I've been having problems with this filesystem for a while now.
I upgraded to 2.6.23 to see if it's improved (no).
Once every 2 or 3 cold boots I get this in dmesg as the user logs in and
accesses the /scratch filesystem. If the error doesn't occur as the user logs in
then it won't happen at all.
Filesystem "dm-0": XFS internal error xfs_btree_check_sblock at line 334 of file
fs/xfs/xfs_btree.c. Caller 0xc01b7bc1
xfs_force_shutdown(dm-0,0x8) called from line 4274 of file fs/xfs/xfs_bmap.c.
Return address = 0xc0214dae
Filesystem "dm-0": Corruption of in-memory data detected. Shutting down
Please umount the filesystem, and rectify the problem(s)
I ssh in as root, umount, mount, umount and run xfs_repair.
This is what I got this time:
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
ir_freecount/free mismatch, inode chunk 59/5027968, freecount 27 nfree 26
- found root inode chunk
All the rest was clean.
It is possible this fs suffered in the 2.6.17 timeframe
It is also possible something got broken whilst I was having lots of issues with
hibernate (which is still unreliable).
I wonder if the fs is borked and xfs_repair isn't fixing it?
PS Please cc on replies.