Hey all, Over the last several months there have been many claims regarding the release of the rewritten btrfsck. Unfortunately, despite numerous claims that it will be released Real Soon Now(c), I have yet to see even a repository with preliminary code. Did I miss an announcement? There is something to be said for "release early, release often." Is there a timeline for getting btrfsck into some sort of usable form? Cheers, - Ben -- 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 Wed, Feb 9, 2011 at 8:52 PM, Ben Gamari <bgamari@gmail.com> wrote:> Hey all, > > Over the last several months there have been many claims regarding the > release of the rewritten btrfsck. Unfortunately, despite numerous > claims that it will be released Real Soon Now(c), I have yet to see > even a repository with preliminary code. Did I miss an announcement? > There is something to be said for "release early, release often." Is > there a timeline for getting btrfsck into some sort of usable form?I can''t speak for the devs, but that''s never stopped me before :p Speculative code to directly muck with known-to-be-corrupted data structures is not something that benefits from early releases. It''s too easy to cause damage that _can''t_ be fixed later, and no amount of warnings will prevent people from trying that code in desperation. Or would you have taken a full image of your 8 drives before trying it the first time? -- 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
Excerpts from Ben Gamari''s message of 2011-02-09 21:52:20 -0500:> Hey all, > > Over the last several months there have been many claims regarding the > release of the rewritten btrfsck. Unfortunately, despite numerous > claims that it will be released Real Soon Now(c), I have yet to see > even a repository with preliminary code. Did I miss an announcement? > There is something to be said for "release early, release often." Is > there a timeline for getting btrfsck into some sort of usable form?Yes, but its still real soon now. I''ve been at about 90% done since Christmas. It would have been out last week but I''ve been chasing a debugging a very difficult corruption under load. I finally found a race in btrfs causing the corruption and now I''m back on fsck full time again. -chris -- 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 Thu, 10 Feb 2011 07:17:10 -0500, Chris Mason <chris.mason@oracle.com> wrote:> Excerpts from Ben Gamari''s message of 2011-02-09 21:52:20 -0500: > > Is there a timeline for getting btrfsck into some sort of usable form? > > Yes, but its still real soon now. I''ve been at about 90% done since > Christmas. It would have been out last week but I''ve been chasing a > debugging a very difficult corruption under load. > > I finally found a race in btrfs causing the corruption and now I''m back > on fsck full time again. >Glad to hear this. Thank you very much for your update. With respect to the other thread (re: loose eSATA cable). I can keep the array around in its current form if it would provide a good test case for btrfsck. That being said, I''m really looking to recover some of the data from this array if at all possible. Cheers, - Ben -- 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 Mason skrev 10.2.2011 14:17:> Excerpts from Ben Gamari''s message of 2011-02-09 21:52:20 -0500: >> Hey all, >> >> Over the last several months there have been many claims regarding the >> release of the rewritten btrfsck. Unfortunately, despite numerous >> claims that it will be released Real Soon Now(c), I have yet to see >> even a repository with preliminary code. Did I miss an announcement? >> There is something to be said for "release early, release often." Is >> there a timeline for getting btrfsck into some sort of usable form? > > Yes, but its still real soon now. I''ve been at about 90% done since > Christmas. It would have been out last week but I''ve been chasing a > debugging a very difficult corruption under load. > > I finally found a race in btrfs causing the corruption and now I''m back > on fsck full time again. >Any status updates on this ? Checking: http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs-unstable.git;a=shortlog;h=refs/heads/next I see last commit is 3+ months ago -- Thomas -- 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
A very good question indeed! ;-) Regards //Ernst Sjöstrand On Tue, Mar 29, 2011 at 14:13, Thomas Backlund <tmb@mandriva.org> wrote:> Chris Mason skrev 10.2.2011 14:17: >> >> Excerpts from Ben Gamari''s message of 2011-02-09 21:52:20 -0500: >>> >>> Hey all, >>> >>> Over the last several months there have been many claims regarding the >>> release of the rewritten btrfsck. Unfortunately, despite numerous >>> claims that it will be released Real Soon Now(c), I have yet to see >>> even a repository with preliminary code. Did I miss an announcement? >>> There is something to be said for "release early, release often." Is >>> there a timeline for getting btrfsck into some sort of usable form? >> >> Yes, but its still real soon now. I''ve been at about 90% done since >> Christmas. It would have been out last week but I''ve been chasing a >> debugging a very difficult corruption under load. >> >> I finally found a race in btrfs causing the corruption and now I''m back >> on fsck full time again. >> > > Any status updates on this ? > > Checking: > http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs-unstable.git;a=shortlog;h=refs/heads/next > > I see last commit is 3+ months ago > > -- > Thomas > -- > 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 >-- 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