Summary: unreplayable log after crash
Product: Linux XFS
Component: XFS kernel code
I have a ~700G filesystem that experienced a hard crash (controller failure),
but the subsequent mount fails when the log would be replayed. xfs_check tells
me that the filesystem is funky:
bad magic # 0x421cd4bf in inode 11281887 bmbt block 66/1011263
expected level 0 got 6369 in inode 11281887 bmbt block 66/1011263
bad btree nrecs (13911, min=127, max=254) in inode 11281887 bmap block 70217279
extent count for ino 11281887 data fork too low (0) for file format
bad nblocks 7169 for inode 11281887, counted 1
bad nextents 28 for inode 11281887, counted 0
bad nblocks 67585 for inode 11317715, counted 67073
bad nextents 155 for inode 11317715, counted 154
bad nblocks 98817 for inode 11343754, counted 99329
bad nextents 242 for inode 11343754, counted 244
bad nblocks 52737 for inode 11343803, counted 53761
bad nextents 185 for inode 11343803, counted 189
bad nblocks 24577 for inode 11358383, counted 24065
bad nextents 71 for inode 11358383, counted 68
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
...and returns with exit code 32.
xfs_repair instructs me to zero the log before attempting a repair.
Device is software striped array across two 3ware hardware RAID-5s.
Filesystem geometry (info from xfs_db, superblock 0):
blocksize = 4096
dblocks = 175829568
agblocks = 1048512
agcount = 168
logblocks = 32768
versionnum = 0x3584
sectsize = 512
inodesize = 512
logsunit = 262144
Compressed xfs_logprint output is available at
[1.7 MiB, 57 MiB uncompressed]
I'm currently dumping the md0 device to another machine for further analysis.
Kernel is 2.4.20-31.7.2.cernsmp which is basically RedHat plus some local
patches to the SCSI tape layer.
Hardware is dual Xeon 2.4GHz 1G RAM 3ware 7850-8/7500-4, WD 120G disks.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.