On Tue, Jul 15, 2008 at 12:58:16AM +0200, Matthias Urlichs wrote: > Hi, > > However, even if they do in fact continue to deteriorate, the ability to > re-map the offending areas and continue gives me an order of magnitude > more time to deal with the problem. > > In fact, as I said, there may be problems lurking on other disks which I > just haven't found yet (how often do you read all 5TB of your data?), > which means that a feature like this is the difference between being > able to recover and certain data loss, RAID-6 nonwithstanding. One idea about this - One could read and write the disks perodically, say once a month. In this way single bit errors that could have evolved on the disks coule be repaired, as the CRC saves the one bit error, and gets it corrected when writing. For a raid - if an error occurs, then the sound data could be used, and if the error persists after a rewrite on the bad disk, that data should then be remapped to a sound area on the drive. Maybe people already have implemented this. SMART data could also be consulted. I thought of badblocks -n to do this, but also raid check could be a place to do it. When writing ons should of cause take care that nobody else is writing the same data. best regards keld -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
