I''m using Btrfs v0.20-rc1-253-g7854c8b on kernel 3.10.10-1-ARCH. I''ve been using this btrfs filesystem on an SSD for a little under a year with no problems until now. I noticed it was getting a bit full (~79%) and tried to do some cleanup by removing old snapshots. Immediately after, the filesystem went into read only mode. I then followed Hugo Mill''s advice (that was posted here: https://bbs.archlinux.org/viewtopic.php?id=169429 ) but was not able to fully recover the filesystem (there were tons of error messages along the entire process). Luckily, mounting the filesystem read-only, I was able to copy all my data and rebuild the filesystem. Anyway, I''m not sure if I ran btrfs-zero-log before or after taking this image. But I have a btrfs-image available for a dev who wants it. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sep 14, 2013, at 11:05 AM, Mathew Kamkar <matkam@gmail.com> wrote:> Luckily, mounting the filesystem read-only, > I was able to copy all my data and rebuild the filesystem.Did you create a new btrfs volume? Or were you somehow able to repair the old one? Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Chris Murphy <lists <at> colorremedies.com> writes:> Did you create a new btrfs volume? Or were you somehow able to repair theold one? No I wasn''t able to repair the old one. I used rsync to copy the data, created a new volume, then rsync copied it back. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html