--- Comment #15 from Christoph Hellwig <hch@xxxxxxx> 2009-02-15 13:08:23 CST
I now have a patch to reject these invalid inode log formats gracefully. That
will still make the log recovery for a fs as badly damaged as yours fail, but
at least it will prevent the kernel from crashing and give some useful error
FYI, I just dumped the whole structures and it's almost completely zeroed:
[ 20.115521] XFS: bad number of regions (0) in inode log item
[ 20.136952] ilf_fields = 0x2, ilf_asize = 0, ilf_dsize = 0
[ 20.148272] ilf_ino = 0, ilf_blkno = 0
[ 20.159309] ilf_len = 0, ilf_boffset = 0
xfs_logprint also finds various invalid zeroes over the log.
Was this filesystem written ontop of luks? In that case I suspect it's doing
something very weird with the write I/Os which causes this log corruption.
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.