e4fsck segfaults whilst repairing a large (4TB+) file system
Issue
e4fsck
ended up with segfault after few minutes:
Illegal block #0 (2823111748) in inode 39493090. CLEARED.
Illegal block #1 (1368098952) in inode 39493090. CLEARED.
Illegal block #4 (1145361442) in inode 39493090. CLEARED.
Illegal block #5 (1514423364) in inode 39493090. CLEARED.
Illegal block #6 (3084775052) in inode 39493090. CLEARED.
Illegal block #9 (2303265804) in inode 39493090. CLEARED.
Illegal block #10 (3995346481) in inode 39493090. CLEARED.
Illegal indirect block (1128743972) in inode 39493090. CLEARED.
Illegal double indirect block (3784160119) in inode 39493090. CLEARED.
Inode 39493090 is too big. Truncate? yes
Block #149948470 (520976742) causes directory to be too big. CLEARED.
Segmentation fault
Environment
- Red Hat Enterprise Linux 5.5
- e4fsprogs-1.41.12-4.el5_10
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.