On Sun, 22 Apr 2012, Tim Connors wrote:
And then just moments ago, I got this in my kernel logs: Internal error xfs_btree_check_sblock at line 119 of file /home/blank/debian/kernel/release/linux-2.6/linux-2.6-3.2.4/debian/build/source_amd64_none/fs/xfs/xfs_btree.c
Awesome! I hadn't yet gotten around to syncing the FS to my new ZFS installation on the NAS that also lost power but would probably cope with it better.
Awesome shit. So xfs_repair wanted it mounted first to replay the log. But mounting it caused an internal error, so it suggested blowing away the log and running xfs_repair on the unmounted filesystem. Did that, a few minor things in lost+found. 24 hours later, Apr 23 03:48:22 dirac kernel: [29301.792677] XFS: Internal error XFS_WANT_CORRUPTED_RETURN at line 341 of file /home/blank/debian/kernel/release/linux-2.6/linux-2.6-3.2.4/debian/build/source_amd64_none/fs/xfs/xfs_alloc.c. Caller 0xffffffffa0a6b072 What a fragile filesystem! Do people actually trust their data to it? I've been running xfs for 2 months now. I had been running ext2/ext3/4 trouble free since they bloody well came out. Ext4 before ext4 was marked stable! -- Tim Connors