From: Asdo <asdo@shiftmail.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Michael Evans <mjevans1983@gmail.com>,
Ryan Wagoner <rswagoner@gmail.com>,
Tim Bock <jtbock@daylight.com>,
linux-raid@vger.kernel.org
Subject: Re: Question about raid robustness when disk fails
Date: Wed, 27 Jan 2010 10:22:36 +0100 [thread overview]
Message-ID: <4B6005DC.7070701@shiftmail.org> (raw)
In-Reply-To: <87vden2a2a.fsf@frosties.localdomain>
Goswin von Brederlow wrote:
> Michael Evans <mjevans1983@gmail.com> writes:
>
>> Why doesn't the kernel issue a pessimistic alternate 'read' path (on
>> the other drives needed to obtain the data) if the ideal method is
>> late. It would be more useful for time-sensitive/worst case buffering
>> to be able to customize when to 'give up' dynamically.
>>
>
> That is a verry good question. I look forward to seeing patches for this
> from you. :) I think it isn't done because nobody has bothered to write
> the code yet but maybe I'm wrong and it would make the code too
> complicated.
>
This is probably more complicated than allowing a timeout to be set at
the MD layer or block-device layer, isn't it?
Which would be just as good I think.
Is it possible to cancel a SATA/SCSI command that is being executed by
the drive?
(it's probably feasible only with NCQ disabled anyway, but it's easy to
disable NCQ)
It's a pity we have to rely on TLER, this narrows the choice of drives a
lot...
next prev parent reply other threads:[~2010-01-27 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 17:39 Question about raid robustness when disk fails Tim Bock
2010-01-22 16:32 ` Goswin von Brederlow
2010-01-25 16:22 ` Tim Bock
2010-01-25 17:51 ` Goswin von Brederlow
2010-01-25 18:12 ` Michał Sawicz
2010-01-26 7:29 ` Goswin von Brederlow
2010-01-27 0:19 ` Ryan Wagoner
2010-01-27 4:22 ` Michael Evans
2010-01-27 9:04 ` Goswin von Brederlow
2010-01-27 9:22 ` Asdo [this message]
2010-01-27 10:25 ` Goswin von Brederlow
2010-01-27 10:43 ` Asdo
2010-01-27 15:34 ` Goswin von Brederlow
2010-01-28 11:52 ` Michael Evans
2010-01-27 15:15 ` Tim Bock
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=4B6005DC.7070701@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=goswin-v-b@web.de \
--cc=jtbock@daylight.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
--cc=rswagoner@gmail.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).