hi again...
after purposely trying to corrupt one drive in my raid1 array (for testing
purposes of course), i discovered something that i find odd. heres how i got
there:
i setup raid1 array w/ 2 identical 9gig scsi drives, and made an ext2fs on the
array. then i stopped the array, and used dd(1) to zero the first 2 blocks on
the first disk (/dev/sdb1, raid-disk 0 in /etc/raidtab). when i then run
raidstart, the mirror starts up fine, but refuses to mount claiming a valid
ext2fs doesnt exist on the device (in the same way trying to mount the
'corrupt' sdb1 would). if i perform the same test using /dev/sdc1 (raid-disk
1), the drives are resync'd successfully during execution of the mount command.
so...why doesnt sdb1 get resync'd? i remember from raidtools version 0.50,
there was at least one option to chkraid that would allow selection of the
'trusted' (ie not corrupt) partition. now that everything lives in the kernel,
i dont see how that would be possible. i tried using raidhot<remove|add> but
since the corrupted disks are still listed as active, removing fails.
perhaps this is a feature, but im just wondering what the logic behind it is...
any insight/help appreciated,
james blanding
