On Fri, Jan 23, 2009 at 05:48:45PM +0100, Bastian Scholz wrote:
> Package: linux-image-2.6.26-1-amd64
> Version: 2.6.26-12
> Severity: important
>
>
> In the last three month I had around five crashes with my XFS filesystem
>
> # dmesg
> <snip>
> [7688274.093948] Filesystem "dm-2": XFS internal error xfs_trans_cancel at
> line
> 1163 of file fs/xfs/xfs_trans.c. Caller 0xffffffffa01b59bb
> [7688274.093976] Pid: 32049, comm: rsnapshot Not tainted 2.6.26-1-amd64 #1
> [7688274.093987]
> [7688274.093988] Call Trace:
> [7688274.094051] [<ffffffffa01b59bb>] :xfs:xfs_link+0x2c1/0x2d2
> [7688274.094092] [<ffffffffa01af9be>] :xfs:xfs_trans_cancel+0x55/0xed
> [7688274.094130] [<ffffffffa01b59bb>] :xfs:xfs_link+0x2c1/0x2d2
> [7688274.094166] [<ffffffffa01b0151>] :xfs:xfs_trans_unlocked_item+0x24/0x3d
> [7688274.094189] [<ffffffff802ab124>] d_instantiate+0x52/0x67
> [7688274.094227] [<ffffffffa01bea66>] :xfs:xfs_vn_link+0x41/0x97
> [7688274.094246] [<ffffffff802a201a>] vfs_link+0x128/0x1c1
> [7688274.094261] [<ffffffff802a4d9e>] sys_linkat+0xe1/0x143
> [7688274.094304] [<ffffffff8020be9a>] system_call_after_swapgs+0x8a/0x8f
> [7688274.094326]
> [7688274.094334] xfs_force_shutdown(dm-2,0x8) called from line 1164 of file
> fs/x
> fs/xfs_trans.c. Return address = 0xffffffffa01af9d7
> [7688274.108381] Filesystem "dm-2": Corruption of in-memory data detected.
> Shutting down filesystem: dm-2
> [7688274.108407] Please umount the filesystem, and rectify the problem(s)
> [7688278.316256] Filesystem "dm-2": xfs_log_force: error 5 returned.
> </snip>
>
> Filesystem setup is XFS on luks on lvm on mdraid5.
> Filesystem size is 600G, raid5 is around 932G
Did you upgrade to Squeeze in the mean time? Has this been resolved in the
current kernel version?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110429232055.GA5516@pisco.westfalen.local
