From: Justin Kanoa Withington <kanoa@cfht.hawaii.edu>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: bad block remapping
Date: Thu, 23 May 2002 15:18:32 -1000 [thread overview]
Message-ID: <3CED94E8.9040303@cfht.hawaii.edu> (raw)
In-Reply-To: 15597.36010.276397.345833@notabene.cse.unsw.edu.au
Thanks Neil,
No I'm not offering; I don't have the skill to do something like that
though I would offer emotional support and pizza to anyone who could.
-Kanoa
Neil Brown wrote:
>On Thursday May 23, kanoa@cfht.hawaii.edu wrote:
>
>>I have philosophical question about the RAID software.
>>
>
>I think you are right.
>After a read error, the raid system would do well to:
> read a few other random blocks on the drive
> (first/last/middle/superblock) to see if the whole drive is dead
> or not
> Updates a failed-read-count in the superblock - abort if this fails
> regnerate the data from redundant info
> attempt a re-write
> On success assume the device has coped.
>
>All we need now is code .... are you offering?
>
>NeilBrown
>
>
prev parent reply other threads:[~2002-05-24 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 0:02 bad block remapping Justin Kanoa Withington
2002-05-24 0:43 ` Neil Brown
2002-05-24 1:18 ` Justin Kanoa Withington [this message]
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=3CED94E8.9040303@cfht.hawaii.edu \
--to=kanoa@cfht.hawaii.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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