On 02/20/2011 12:03 PM, Simon Mcnair wrote: > Hi Phil, > > Is this fsck (fsck.ext4 -n -b 32768 /dev/mapper/lvm--raid-RAID >> fsck.txt) as bad as it looks ? :-( It's bad. Either the original sdd has a lot more corruption than I expected, or the 3ware spread corruption over all the drives. If the former, failing it out of the array might help. If the latter, your data is likely toast. Some identifiable data is being found, based on the used vs. free block/inode/directory counts in that report. That's good. I suggest you do "mdadm /dev/md0 --fail /dev/sdi1" and repeat the "fsck -n" as above. (It'll be noticably slower, as it'll be using parity to reconstruct 1 out every 9 chunks.) If it the fsck results improve, or stay the same, proceed to "fsck -y", and we'll see. Wouldn't hurt to run "iostat -xm 5" in another terminal during the fsck to see what kind of performance that array is getting. Phil -- 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
