From: Chris Ball <cjb@laptop.org>
To: "Morten P.D. Stevens" <mstevens@imt-systems.com>
Cc: Chris Mason <chris.mason@oracle.com>,
"linux-btrfs\@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: 2.6.36-rc1 btrfs still unstable
Date: Mon, 16 Aug 2010 11:45:29 -0400 [thread overview]
Message-ID: <m3iq3a4l46.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <7222A6B8ACA37D4AA1AC37810C43E8A80F5FC5BC@mail.corp.imt-systems.com> (Morten P. D. Stevens's message of "Mon, 16 Aug 2010 16:17:54 +0200")
Hi,
> the other big question is:
>
> Is btrfs with 2.6.36 really rockstable and ready to use in
> productive environments?
No, certainly not until there's a working fsck tool -- at the moment
it's rather easy to kill a btrfs by just losing power.
I just added a paragraph to the main page of the wiki about this,
since we've had a few people on IRC express surprise that their
filesystem aren't fixable after power loss. Feel free to reword:
Note that Btrfs does not yet have a fsck tool that can fix errors.
While Btrfs is stable on a stable machine, it is currently possible
to corrupt a filesystem irrecoverably if your machine crashes or
loses power. This will be fixed when the fsck tool is ready.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2010-08-16 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 8:46 2.6.36-rc1 btrfs still unstable Ameya Palande
2010-08-16 12:16 ` Chris Mason
2010-08-16 14:17 ` Morten P.D. Stevens
2010-08-16 15:45 ` Chris Ball [this message]
[not found] ` <AANLkTin-q4N9g3=ymsiJy051xts3b2vioNdqku6DMEzQ@mail.gmail.com>
2010-08-16 16:11 ` Fwd: " Evert Vorster
2010-08-16 16:32 ` Chris Ball
2010-08-16 22:25 ` Diego Calleja
2010-08-26 22:45 ` Roy Sigurd Karlsbakk
2010-08-26 23:17 ` Diego Calleja
2010-08-17 11:57 ` Carlos R. Mafra
2010-08-17 16:25 ` Rodrigo E. De León Plicet
2010-08-25 16:57 ` Johannes Hirte
2010-08-26 8:58 ` Xavier Nicollet
2010-08-26 22:48 ` Roy Sigurd Karlsbakk
2010-08-17 0:14 ` Chris Samuel
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=m3iq3a4l46.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mstevens@imt-systems.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).