I posted a raid5 parity calculator implemented in perl a while back (a couple weeks?) that is capable of taking your disk geometry, the RAID LBA you're interested in, and finding the disk sector it belongs to.
I honestly don't remember if it can go the other way, but I'm not sure why it couldn't? Its possible that bad blocks may simply be in the parity chunk of the stripe too. Once you've got the RAID LBA you can use the methods in the BadBlockHowto to find the file
Either way, the math isn't too hard, and the script isn't very complicated, but doing that math is the only way I know of to relate the bits of data you've got to the file.
-Mike
Matthias Julius wrote:
Gordon Henderson <gordon@xxxxxxxxxx> writes:
Try something like:
mdadm --assemble /dev/mdY /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 \ --run --force
--force did the trick. I could have thought of that one myself. Thanks.
As for not hitting the bad blocks again: Is there a way to find out to which file they belong with ext3/xfs on LVM on RAID5? That would be helpfull.
Matthias
- 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
- 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
