Package: e2fsck-static Version: 1.37+1.38-WIP-0620-1 Severity: normal I found e2fsck to reproducible segfault on a certain inode on a big 330G raid5 partition. I tested e2fsck from e2fsprogs and e2fsck-static from both sarge (1.37-2sarge1) and sid which had the same problem with inode <8962588>. After changing some of the inode attributes with debugfs, e2fsck did its job.
The stat command outputs: debugfs: stat <8962588> Inode: 8962588 Type: block special Mode: 0562 Flags: 0xb00b0505 Generation: 1741115502 User: 33807 Group: 34868 Size: 0 File ACL: 1142969774 Directory ACL: 0 Links: 16716 Blockcount: 0 Fragment: Address: 936282759 Number: -103 Size: -95 ctime: 0x05b33a7b -- Thu Jan 11 21:26:35 1973 atime: 0x1a7a7ab1 -- Sun Jan 29 15:26:57 1984 mtime: 0xa48e60d0 -- Sat May 21 09:50:24 1921 Device major/minor number: 198:32 (hex c6:20) Here an excerpt from a e2fsck run: sh-3.00# e2fsck -C 0 /dev/md0 e2fsck 1.38-WIP (20-Jun-2005) /dev/md0 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes /dev/md0: |============================= - 51.5% Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts i_file_acl for inode 8962566 (...) is 19825478, should be zero. Clear<y>? yes .. .. .. i_file_acl for inode 8962581 (...) is 3433848547, should be zero. Clear<y>? yes Inode 8962581 (...) has invalid mode (0135731). Clear<y>? yes i_file_acl for inode 8962584 (...) is 3745337237, should be zero. Clear<y>? yes Inode 8962584 (...) has invalid mode (0152701). Clear<y>? yes i_file_acl for inode 8962585 (...) is 537618018, should be zero. Clear<y>? yes Inode 8962585 (...) has invalid mode (030344). Clear<y>? yes i_file_acl for inode 8962586 (...) is 860179777, should be zero. Clear<y>? yes Inode 8962586 (...) is an illegal character device. Clear<y>? yes i_file_acl for inode 8962588 (...) is 1142969774, should be zero. Clear<y>? yes i_faddr for inode 8962588 (...) is 936282759, should be zero. Clear<y>? yes i_frag for inode 8962588 (...) is 153, should be zero. Clear<y>? yes i_fsize for inode 8962588 (...) is 161, should be zero. Clear<y>? yes Segmentation fault -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
