From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: NeilBrown <neilb@suse.de>, Tomasz Chmielewski <mangoo@wpkg.org>,
linux-raid@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
Date: Fri, 17 Jul 2009 01:20:03 -0400 [thread overview]
Message-ID: <4A600A03.5040808@garzik.org> (raw)
In-Reply-To: <4A6002AC.9090807@kernel.org>
Tejun Heo wrote:
> NeilBrown wrote:
>> I tried that and easily found cases where it fails way too fast.
>> FAILFAST seems to mean different things on different devices, making
>> it useless in general (it is still useful in some specific cases
>> such as multipath on devices which are expected to be used under
>> multipath and so treat FAILFAST appropriately).
>
> Yeap, FAILFAST flags seem geared pretty much toward multipathing.
Yes :/
I'm glad this area is getting some attention, because we ideally want to
do two things in parallel:
* send upper layer advisory message, when we first notice a failure
* begin EH recovery
Time passes, libata attempts recovery, and completes the command with
success or failure many seconds later.
Right now, failfast handling is inconsistent, and is not (I think...)
always signalled as soon as we begin EH.
Jeff
next prev parent reply other threads:[~2009-07-17 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 23:03 hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal? Tomasz Chmielewski
2009-07-17 4:12 ` Tejun Heo
2009-07-17 4:38 ` NeilBrown
2009-07-17 4:48 ` Tejun Heo
2009-07-17 5:20 ` Jeff Garzik [this message]
2009-07-17 5:24 ` Tejun Heo
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=4A600A03.5040808@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=neilb@suse.de \
--cc=tj@kernel.org \
/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).