Hi I'm having trouble with checking a corrupt ext3 file system resulting from a 3-disk failure on a 12 disk software raid6 array. The disk failure was due to an issue with the (3ware) controller and 11 disks appear to be fine. However, I had to --assemble --force the array because two of the 11 disks were not up to date after the crash. e2fsck from today's git master branch aborts after a while with ./e2fsck -f -y -C 0 /dev/euclidean/snap_abt1_kristall_RockMakerStorage e2fsck 1.41.12 (17-May-2010) Backing up journal inode block information. Pass 1: Checking inodes, blocks, and sizes Error storing inode count information (inode=245859898, count=2): Memory allocation failed e2fsck: aborted This is an old 32 bit system with only 1G of ram and a 2.6.24 distro kernel. I added _lots_ of swap but this did not help. Any hints on how to proceed? Since the file system is corrupt anyway, it is maybe easiest to delete inode 245859898 with debugfs, but maybe there is a better option. Moreover, since this might be some kind of e2fsck-trusts-corrupt-data issue, you might be interested in looking at this. Further info: The ext3 file system lives on a lv within a vg whose single pv is the 12 disk raid6 array. The file system stores hard link based backups, so it contains _lots_ of hard links. Thanks Andre -- The only person who always got his work done by Friday was Robinson Crusoe
Attachment:
signature.asc
Description: Digital signature
