On Tue, Jun 11, 2013 at 03:20:12PM +1000, Dave Chinner wrote: > Please test with XFS and CONFIG_XFS_DEBUG=y - xfstests will stress > the dio subsystem a lot more when it is run on XFS. Indeed, xfstests > generic/013 assert fails almost immediately with: Thanks - I haven't used xfstests much before. This one turned out to be an easy fix, but once I turned on CONFIG_XFS_DEBUG I hit something else I hadn't seen before: [ 1343.482366] XFS (sdb2): Corruption detected. Unmount and run xfs_repair [ 1343.482425] XFS (sdb2): bad inode magic/vsn daddr 64 #8 (magic=5858) [ 1343.482482] XFS: Assertion failed: 0, file: /home/kent/linux/fs/xfs/xfs_inode.c, line: 417 [ 1343.482558] ------------[ cut here ]------------ [ 1343.482611] kernel BUG at /home/kent/linux/fs/xfs/xfs_message.c:108! This one looks weirder - any thoughts on what might cause _that_? (Don't spend any time on it, I haven't tried to debug it besides glancing at the relevant xfs code - just curious if you have any pointers) -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
