From: Jeff Putney <jeffrey.putney@gmail.com>
To: Christian Hesse <list@eworm.de>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New btrfsck status
Date: Tue, 7 Jun 2011 11:52:21 -0500 [thread overview]
Message-ID: <BANLkTimzVU6_dqYOWVJ1sdio2akOKT3ghQ@mail.gmail.com> (raw)
In-Reply-To: <20110606164109.7b032c17@io.vpn.lugor.de>
Me too. I've got a 9TB filesystem that I can't mount since rebooting
during a rebalance. I want to get the fs as repaired as possible, but
I am not in a hurry, and I have enough space at present to make a
duplicate and play with test versions of the repair.
--jeff
On Mon, Jun 6, 2011 at 9:41 AM, Christian Hesse <list@eworm.de> wrote:
> Chris Mason on 10 Feb 13:17:
>> Excerpts from Ben Gamari's message of 2011-02-09 21:52:20 -0500:
>> > 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. =A0I've been at about 90% done sin=
ce
>> Christmas. =A0It 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.
>
> This mail was about four month ago...
> Any news on this topic?
>
> I really would like to test btrfs on my desktop systems, but I still
> hesitate because of the missing fsck.
> --
> Schoene Gruesse
> 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 =A0http://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
next prev parent reply other threads:[~2011-06-07 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 14:41 New btrfsck status Christian Hesse
2011-06-07 16:52 ` Jeff Putney [this message]
2011-06-13 18:56 ` Daniel Witzel
-- strict thread matches above, loose matches on Subject: below --
2011-02-10 2:52 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
2011-04-13 14:00 ` Ernst Sjöstrand
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=BANLkTimzVU6_dqYOWVJ1sdio2akOKT3ghQ@mail.gmail.com \
--to=jeffrey.putney@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@eworm.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).