On Sun, Jul 03, 2005 at 02:33:14PM +0200, Christian Egger wrote:
> 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.
What did you change which caused e2fsck to not segfault?
> 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)
I assume this was the stat command before you changed any of the inode
attributes, which caused e2fsck to segfault?
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
