From: Joe Peterson <lavajoe@gentoo.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>, linux-btrfs@vger.kernel.org
Subject: Re: Raid1 with failing drive
Date: Wed, 29 Oct 2008 14:02:04 -0600 [thread overview]
Message-ID: <4908C13C.7070607@gentoo.org> (raw)
In-Reply-To: <1225307907.6448.284.camel@think.oraclecorp.com>
Chris Mason wrote:
> On Tue, 2008-10-28 at 16:48 -0700, Stephen Hemminger wrote:
>> I have a system with a pair of small/fast but unreliable scsi drives.
>> I tried setting up a raid1 configuration and using it for builds.
>> Using 2.6.26.7 and btrfs 0.16. When using ext3 (no raid) on same partition,
>> the driver would recalibrate and log something an keep going. But with
>> btrfs it doesn't recover and takes drive offline.
>>
>
> Btrfs doesn't really take drives offline. In the future we'll notice
> that a drive is returning all errors, but for now we'll probably just
> keep beating on it.
It can also detect when a bad checksum is returned or the drive returns an i/o
error, right? Would the "all-zero" test be a heuristic in case neither of those
happened (but I cannot imagine why the zeros would get by the checksum check)?
> The IO error handling code in btrfs currently expects it'll be able to
> find at least one good mirror. You're probably hitting some bad
> conditions as it fails to clean up.
What happens (or rather, will happen) on a regular/non-mirrored btrfs? Would it
then return an i/o error to the user and/or mark a block as bad? In ZFS, the
state of the volume changes, noting an issue (also happens on a scrub), and the
user can check this. What I don't like about ZFS is that the user can clear the
condition, and then it appears OK again until another scrub.
-Joe
next prev parent reply other threads:[~2008-10-29 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 23:48 Raid1 with failing drive Stephen Hemminger
2008-10-29 19:18 ` Chris Mason
2008-10-29 20:02 ` Joe Peterson [this message]
2008-10-29 20:06 ` Stephen Hemminger
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=4908C13C.7070607@gentoo.org \
--to=lavajoe@gentoo.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shemminger@vyatta.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