From: Thomas Backlund <tmb@mandriva.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New btrfsck status
Date: Tue, 29 Mar 2011 15:13:00 +0300 [thread overview]
Message-ID: <4D91CCCC.10305@mandriva.org> (raw)
In-Reply-To: <1297340143-sup-3602@think>
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
next prev parent reply other threads:[~2011-03-29 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 2:52 New btrfsck status Ben Gamari
2011-02-10 3:04 ` cwillu
2011-02-10 12:17 ` Chris Mason
2011-02-10 12:26 ` Ben Gamari
2011-03-29 12:13 ` Thomas Backlund [this message]
2011-04-13 14:00 ` Ernst Sjöstrand
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 14:41 Christian Hesse
2011-06-07 16:52 ` Jeff Putney
2011-06-13 18:56 ` Daniel Witzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D91CCCC.10305@mandriva.org \
--to=tmb@mandriva.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.