From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Feature suggestion: immediate repair attempt on failed read?
Date: Fri, 14 Nov 2008 12:29:25 +0000 [thread overview]
Message-ID: <491D6F25.8030301@anonymous.org.uk> (raw)
On 13/11/2008 23:04, Mikael Abrahamsson wrote (in the "OT: Tips for good
hard drives for a home server" thread):
> Looking at the md code in linux, would it be possible to do some work
> around here in that if a drive read operationstalls, let's try to read
> from the other drives and then re-write the block on the drive that
> stalled?
I'd like to second this suggestion; my coding skills are WAY too rusty
to attempt it myself, but it sounds like an excellent idea.
We could also have a timeout setting so that if a read stalls, at least
the application can get its data (by reading the other discs) and the md
subsystem can carry on waiting for the read and/or just doing the
rewrite in the background.
What happens at the moment - could one slow read cause the array to be
switched into degraded mode immediately?
Cheers,
John.
reply other threads:[~2008-11-14 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=491D6F25.8030301@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.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).