From: Erik Logtenberg <erik@logtenberg.eu>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS fsck ?
Date: Fri, 23 Dec 2011 17:55:35 +0100 [thread overview]
Message-ID: <4EF4B287.3090900@logtenberg.eu> (raw)
In-Reply-To: <20111122223140.GT28259@shiny>
Hi Chris,
Any updates on the results of another month of full time work on btrfsck?
Thanks,
Erik.
> I've set myself up for disappointment with release dates in the past.
>
> We've found put some really important corruption fixes into the 3.2
> merge window, and the current for-linus branch of the btrfs kernel repo
> has a fix for write cache flushing bugs that are probably responsible
> for most of the corruptions people have seen with power failures.
>
> With this settled down, I'm back on fsck full time.
>
> -chris
next prev parent reply other threads:[~2011-12-23 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 11:41 BTRFS fsck ? Hervé CHIBOIS
2011-11-22 11:45 ` Roman Mamedov
2011-11-22 22:31 ` Chris Mason
2011-12-23 16:55 ` Erik Logtenberg [this message]
2011-12-29 10:32 ` Gour
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=4EF4B287.3090900@logtenberg.eu \
--to=erik@logtenberg.eu \
--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 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).