From: Arne Jansen <sensille@gmx.net>
To: Mike Fleetwood <mike.fleetwood@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS and power loss ~= corruption?
Date: Fri, 26 Aug 2011 11:30:53 +0200 [thread overview]
Message-ID: <4E5767CD.3010407@gmx.net> (raw)
In-Reply-To: <CAMU1PDgk-uKU9SuQz1YxGPNVy3HVObwtYALgcDL_Jb0MWcss5w@mail.gmail.com>
On 26.08.2011 09:48, Mike Fleetwood wrote:
>> On 26.08.2011 01:01, Gregory Maxwell wrote:
>
> This article describes evaluating ext3, reiserfs and jfs using fault
> injection using a custom Linux block device driver.
> "Model-Based Failure Analysis of Journaling File Systems"
> http://www.cs.wisc.edu/adsl/Publications/sfa-dsn05.pdf
> --
While the article is interesting, it describes a quite different
failure mode. I/O-error handling is not very sophisticated in
btrfs yet. The tests Gregory were taking about are on completely
well-behaving hardware. Failure injection would be the second step.
next prev parent reply other threads:[~2011-08-26 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 13:11 BTRFS and power loss ~= corruption? Berend Dekens
2011-08-24 13:31 ` Arne Jansen
2011-08-24 15:01 ` Berend Dekens
2011-08-24 15:04 ` *** GMX Spamverdacht *** " Arne Jansen
2011-08-24 15:13 ` Berend Dekens
2011-08-24 17:06 ` Mitch Harder
2011-08-24 21:00 ` Ahmed Kamal
2011-08-25 3:31 ` Anand Jain
2011-08-25 17:55 ` Martin Steigerwald
2011-08-25 22:16 ` Maciej Marcin Piechotka
2011-11-09 20:15 ` Martin Steigerwald
2011-08-25 23:01 ` Gregory Maxwell
2011-08-26 6:37 ` Arne Jansen
2011-08-26 7:48 ` Mike Fleetwood
2011-08-26 9:30 ` Arne Jansen [this message]
2011-11-09 17:33 ` Stefan Behrens
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=4E5767CD.3010407@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mike.fleetwood@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.