Re: raid and sleeping bad sectors

["Jure Peèar" <pegasus@nerv.eu.org>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1663 bytes --]

On Wed, 30 Jun 2004 18:44:16 -0400
"Guy" <bugzilla@watkins-home.com> wrote:

> I want plan "a".  I want the system to correct the bad block by re-writing
> it!  I want the system to count the number of times blocks have been
> re-located by the drive.  I want the system to send an alert when a limit
> has been reached.  This limit should be before the disk runs out of spare
> blocks.  I want the system to periodically verify all parity data and
> mirrors.  I want the system to periodically do a surface scan (would be a
> side effect of verify parity).

And where do you propose the system would store all the info about
badblocks?

I have an old hw raid controller for my alpha box maintains a badblock table
in its nvram. I guess it's a common feature in hw raid cards, since i had a
whole box of disks with firmwares that reported each internal badblock
relocation as scsi hardware error. Needless to say, linux sw raid freaked
out on each such event. Things were very interesting untill we got firmware
upgrade for those disks ... 
Also, at least 3ware cards do a 'nightly maintenance' of disks which i guess
is something like dd if=/dev/hdX of=/dev/null ... What is holding you back
to do this with a simple shell script and a cron entry?
Now for cheching the parity in the raid5/6 setups, some kind of tool would
be needed ... maybe some extension to mdadm? For the really paranoid people
out there ... :)


-- 

Jure Peèar
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html