forcing a raid recovery

[dsr-mzpnVDyJpH4k7aNtvndDlA at public.gmane.org (Dan Ritter)]

On Tue, Nov 03, 2009 at 02:12:29PM -0500, Stephen Adler wrote:
> Hi all,
> 
> I'm putting together a backup system at my job and in doing so setup the 
> good ol' raid 5 array. While I was putting the disk array together, I 
> read that one could encounter a problem in which you replace a failed 
> drive, the rebuilding processes will trip over another bad sector in on 
> of the drives which was good before starting the rebuilding process and 
> thus you end up with a screwed up raid array. So I was thinking of a way 
> to avoid this problem. One solution is to kick off a job once a week or 
> month in which you force the whole raid array to be read. I was thinking 
> of possibly forcing a check sum of all the files I had stored on the 
> disk. The other idea I had was to force one of the drives into a failed 
> state and then add it back in and thus force the raid to rebuild. The 
> rebuilding processes takes about 3 hours on my system which I could 
> easily execute at 2am every Sunday morning.

That's why I don't use RAID5, and I do use RAID10, and I also
have backups.

The incremental disk and controller cost is paid back in
man-hours and uptime.

-dsr-


-- 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.
You can't defend freedom by getting rid of it.