From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Billy Crook <billycrook@gmail.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Bill Davidsen <davidsen@tmr.com>, Neil Brown <neilb@suse.de>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Distributed spares
Date: Tue, 14 Oct 2008 01:29:21 +0200 [thread overview]
Message-ID: <20081013232921.GB22265@rap.rap.dk> (raw)
In-Reply-To: <a43edf1b0810131530x36a69089la0d5d26a2228b796@mail.gmail.com>
On Mon, Oct 13, 2008 at 05:30:49PM -0500, Billy Crook wrote:
> Just my two cents.... Those daily smart tests or regularly running
> badblocks are fine, but they're not 'real' load. A test can't prove
> everything is right, it can at best only prove it didn't find anything
> wrong. Distributed spare would exert 'real' load on the spare because
> the spare disks ARE the live disks.
>
>
> On a side note, it would be handy to have a daemon that could run in
> the background on large raid1's, or raid6', and once a month, pull
> each disk out of the array sequentially, completely overwrite it,
> check it with badblocks several times, do the smart tests, etc...,
> then rejoin it, reinstall grub, wait an hour and move on. The point
> being, of course, to kill weak drives off early and in a controlled
> manor. It would be even nicer if there were a way to hot-transfer one
> raid component to another without setting anything faulty. I suppose
> you could make all the components of the real array be single disk
> raid1 arrays for that purpose. Then you could have one extra disk set
> aside for this sort of scrubbing, and never even be down one of your
> parities. I guess I should add that onto my todo list....
I have also been thinking a little on this. My idea is that if bit
errors develop on disks, then there is first maybe one bit error, and
the crc check on the disk sectors then finds and corrects these.
If you rewrite such bit errors, then that bit error will be corrected,
and you prevent the one-bit error from developing to a two-bit error
that is not correctable by the CRC.
Is there some merit to this idea?
Furthermore, if bad luck has striken, then in the case of mirrored RAIDs
you could - when crc fails, then see that this is the block in error and
recreate it from the redundant info, Would be good for raid1, raid10,
raid5, raid6. If the block then could not be written without errors,
then it could be added to a bad blocks list and remapped.
I think there is nothing novel in a scheme like this, but I would like
to know if it is implemented somewhere. Articles say that bit errors on
disks are becoming more and more frequent, so schemes like this may help
the scary scenarion somewhat.
best regards
keld
next prev parent reply other threads:[~2008-10-13 23:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 21:50 Distributed spares Bill Davidsen
2008-10-13 22:11 ` Justin Piszcz
2008-10-13 22:30 ` Billy Crook
2008-10-13 23:29 ` Keld Jørn Simonsen [this message]
2008-10-14 10:12 ` Martin K. Petersen
2008-10-14 13:06 ` Keld Jørn Simonsen
2008-10-14 13:20 ` David Lethe
2008-10-14 12:02 ` non-degraded component replacement was " David Greaves
2008-10-14 13:18 ` Billy Crook
2008-10-14 23:20 ` Bill Davidsen
2008-10-14 10:04 ` Neil Brown
2008-10-16 23:50 ` Bill Davidsen
2008-10-17 4:09 ` David Lethe
2008-10-17 13:46 ` Bill Davidsen
2008-10-20 1:11 ` Neil Brown
2008-10-17 13:09 ` Gabor Gombas
-- strict thread matches above, loose matches on Subject: below --
2008-10-14 13:30 David Lethe
2008-10-14 14:37 ` Keld Jørn Simonsen
2008-10-14 15:18 ` David Lethe
2008-10-14 16:29 ` KELEMEN Peter
2008-10-14 17:16 ` David Lethe
2008-10-14 17:20 ` Mattias Wadenstein
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=20081013232921.GB22265@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=billycrook@gmail.com \
--cc=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).