Carlos E. R. wrote:
On Saturday, 2010-01-23 at 13:20 -0600, David C. Rankin wrote:
On 01/22/2010 11:01 AM, Carlos E. R. wrote:
On Friday, 2010-01-22 at 17:23 +0100, Anders Johansson wrote:
...
As far as I know, fsck never does badblock analysis
As a matter of fact, it does. Kind of. For instance, for ext3 it calls e2fsck, and this one has options for badblock handling.
There in lies an Achilles' of dmraid that I am interested in. If there isn't a specific kernel level workaround to temporarily disable a dmraid array to check and correct any normally easily correctable 'disk' errors such as bad blocks, etc.., then that means a dmraid setup will suppress/prevent the correction of disk errors on each 'disk' in the array allowing simple correctable errors to propagate or grow into multiple compounded errors resulting in disk deterioration to the point of data loss.
Whoa! Hold on.
The posibility of using fsck to mark badblocks is _NOT_ used on contemporary hard disks.
Yep. You have to go pretty far back for that to be a realistic option. Pre-IDE days, I would say. /Per -- Per Jessen, Zürich (-0.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org