From: Chris Samuel <chris@csamuel.org>
To: Riccardo Berto <riccardobrt@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RESEND] btrfs corruption / cannot mount
Date: Sun, 02 Dec 2012 23:44:42 +1100 [thread overview]
Message-ID: <50BB4D3A.2050309@csamuel.org> (raw)
In-Reply-To: <CAHt5hBH6drsjdzudgwgd8hdyRFOXsZqptu3J5y32z=MGxTmhCg@mail.gmail.com>
Hiya Riccardo,
On 02/12/12 19:49, Riccardo Berto wrote:
> I'm a btrfs user since I encountered the ext4 3.6.2 bug and then I
> decided to switch.
You are aware that the ext4 issue you mention only affects people who
turned on journal checksums, and is not turned on by default?
This LWN article has a good summary:
http://lwn.net/Articles/521803/
As Michael wrote btrfs is still considered an experimental filesystem.
All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
prev parent reply other threads:[~2012-12-02 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 8:49 [RESEND] btrfs corruption / cannot mount Riccardo Berto
2012-12-02 12:21 ` Michael Kjörling
2012-12-02 12:44 ` Chris Samuel [this message]
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=50BB4D3A.2050309@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=riccardobrt@gmail.com \
/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).