On Tue, Sep 11, 2012 at 09:47:49AM +0200, Jacek Luczak wrote:
> Hi All,
> got this during heavy IO (parallel checkout of few large projects from SVN):
> XFS (dm-8): Corruption detected. Unmount and run xfs_repair
> XFS (dm-8): Internal error xfs_trans_cancel at line 1467 of file
> fs/xfs/xfs_trans.c. Caller 0xffffffffa03c9974
> Pid: 11930, comm: svn Not tainted 3.4.10-1 #1
> Call Trace:
> [<ffffffffa03f758b>] ? xfs_trans_cancel+0x56/0xd7 [xfs]
> [<ffffffffa03c9974>] ? xfs_create+0x467/0x4cf [xfs]
> [<ffffffffa03c1777>] ? xfs_vn_mknod+0xcb/0x160 [xfs]
> [<ffffffff81101a30>] ? vfs_create+0x6e/0xc7
> [<ffffffff81102487>] ? do_last+0x3a5/0x745
> [<ffffffff811028f5>] ? path_openat+0xce/0x35f
> [<ffffffff81102c53>] ? do_filp_open+0x2c/0x72
> [<ffffffffa03ca5d7>] ? xfs_release+0x1ac/0x1cc [xfs]
> [<ffffffff8110c169>] ? alloc_fd+0x69/0xf2
> [<ffffffff810f588e>] ? do_sys_open+0x107/0x18e
> [<ffffffff813cb3f9>] ? system_call_fastpath+0x16/0x1b
That won't tell us what caused the problem. FWIW:
i.e. mount options, filesystem size, geometry, space usage on the
filesystem, etc are all relevant.
Indeed, this issue is often caused by fragmented free space andnot
being able to allocate inodes, though that usually just results in
ENOSPC. Use the xfs_db "freespace" command to dump the freespace
histogram when the error occurs and you've unmounted the filesystem.
> Is it a known issue? I have not - yet - enabled this host in CI thus
> can't tell if this can be reproduced.
> I've done repair but did not saved output.
Were there any errors that were fixed?