> Well, I now get, after rebooting: > > /dev/md3: UNEXPECTED INCONSISTENCY; run fsck manually > > So I did > > fsck -y /dev/md3 > > and after running for about a minute or so, it gets into this > > Too many illegal blocks in inode 8 > > and > > Illegal block #6828 (39485860) in inode 8. CLEARED > > Several lines of these, and then again > > Too many illegal blocks in inode 8 > > The block number (#6828) changes but this loop never seems to end. I > aborted this, for now. When I tried > > mount /dev/md3 /home > > I got: wrong fs type, bad option, bad superblock on md3 > I ran fsck on /dev/md0 again, answered 'n' to the question if I wanted to clear inode 8, and it gets into the following infinite loop Directory inode 83161, block 0, offset 0: directory corrupted. Salvage<y>? If I answer 'y' then it asks the very same thing about inode 83161, and if I answer n, then I get e2fsck aborted. Máté -- Matyi -- 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
