From: Diego Calleja <diegocg@gmail.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: "Morten P.D. Stevens" <mstevens@imt-systems.com>,
Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: 2.6.36-rc1 btrfs still unstable
Date: Fri, 27 Aug 2010 01:17:06 +0200 [thread overview]
Message-ID: <201008270117.06249.diegocg@gmail.com> (raw)
In-Reply-To: <31081717.109.1282862751167.JavaMail.root@zimbra>
> Even with cheap drives, a filesystem shouldn't die. With stuff like ZFS, you can use all sorts of crap and still live with it. Btrfs should follow that track.
Sadly that's not true, a bit of cooperation of the hardware is needed.
Both Btrfs and ZFS need to be sure that certain operations i.e. writting
a modified superblock need to be physically on the disk. Some disks lie
(or fail) when they are asked to write data to the disk, and both filesystems
have faced filesystem inconsistencies due to this. AFAIK there is nothing
the filesystem can do to avoid that.
next prev parent reply other threads:[~2010-08-26 23:17 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
[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 [this message]
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=201008270117.06249.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mstevens@imt-systems.com \
--cc=roy@karlsbakk.net \
/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).