From: Bill Davidsen <davidsen@tmr.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: [RFC] Additional info on mdadm 'check'
Date: Thu, 16 Aug 2007 08:21:18 -0400 [thread overview]
Message-ID: <46C4413E.3060302@tmr.com> (raw)
I was wondering if there would be enough value in saving more
information out of 'check' to justify the effort of coding it.
Particularly in the area of faster repair. If the check operation
optionally left a bitmap of stripes which were bad, if the admin decided
that a repair was appropriate, then only the stripes identified by check
would need to be processed. Because of possible additional errors, etc,
that should be optional as well.
This opens the door to more intensive repair operations, such as voting
on more-than-two-way mirrors, and extensive test and try recovery on
RAID-6, where no read error is found but the data doesn't match. By
assuming chunks are bad, one at a time, a correct sector might be
identified and written back.
Note: this is just an idea at the moment, I'm just doing a feasibility
study here. ;-)
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
reply other threads:[~2007-08-16 12:21 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=46C4413E.3060302@tmr.com \
--to=davidsen@tmr.com \
--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).