Re: Better handling of readerrors with raid5.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>i recovered my raid by using dd_rescue the last failed disk to a spare 
>disk (with 4 read errors)
>(and doing a mdadm -A -force)

>(so I should have a corrupted file somewhere?)

Or a corrupted filesystem, which e2fsck will find & fix.

Did you write down the bad sectors?  If so, you can use debugfs to find out
where they are on the filesystem. Computing the filesystem block number from
the device sector number will be an exercise...

-
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux