Your message dated Sat, 7 Feb 2009 15:37:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#429381: Info received (XFS internal error)
has caused the Debian Bug report #429381,
regarding XFS internal error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
429381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429381
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-12etch2
Severity: important
Hi,
Recently, I meet many times on many servers, large (>1TB) XFS filesystem throw
kernel internal error:
Filesystem "cciss/c0d2": XFS internal error xfs_trans_cancel at line 1138 of
file fs/xfs/xfs_trans.c. Caller 0xffffffff881df006
Call Trace:
[<ffffffff881d6d18>] :xfs:xfs_trans_cancel+0x5b/0xfe
[<ffffffff881df006>] :xfs:xfs_create+0x58b/0x5dd
[<ffffffff881e7496>] :xfs:xfs_vn_mknod+0x1bd/0x3c8
[<ffffffff8027d27d>] default_wake_function+0x0/0xe
[<ffffffff802200e5>] __up_read+0x13/0x8a
[<ffffffff881c3682>] :xfs:xfs_iunlock+0x57/0x79
[<ffffffff881dc180>] :xfs:xfs_lookup+0x6c/0x7d
[<ffffffff802200e5>] __up_read+0x13/0x8a
[<ffffffff881c3682>] :xfs:xfs_iunlock+0x57/0x79
[<ffffffff881dc1ce>] :xfs:xfs_access+0x3d/0x46
[<ffffffff881e7a4b>] :xfs:xfs_vn_permission+0x14/0x18
[<ffffffff8020cc7d>] permission+0x87/0xce
[<ffffffff80208f26>] __link_path_walk+0x16a/0xf3c
[<ffffffff8022ae52>] mntput_no_expire+0x19/0x8b
[<ffffffff8020dd5f>] link_path_walk+0xd3/0xe5
[<ffffffff802381ed>] vfs_create+0xe7/0x12c
[<ffffffff80218efb>] open_namei+0x18d/0x69c
[<ffffffff802252f1>] do_filp_open+0x1c/0x3d
[<ffffffff80217baa>] do_sys_open+0x44/0xc5
[<ffffffff802584d6>] system_call+0x7e/0x83
xfs_force_shutdown(cciss/c0d2,0x8) called from line 1139 of file
fs/xfs/xfs_trans.c. Return address = 0xffffffff881d6d36
Filesystem "cciss/c0d2": Corruption of in-memory data detected. Shutting down
filesystem: cciss/c0d2
Please umount the filesystem, and rectify the problem(s)
I hope this is a bug, please help to identify it. Thanks very much!
Chun Tian (binghe)
NetEase.com, Inc.
--- End Message ---
--- Begin Message ---
On Wed, Jan 21, 2009 at 06:09:20PM +0800, Chun Tian (binghe) wrote:
> Hi,
>
> Recently I found this issue only happends on our specific hardware (HP
> Proliant DL145), our other DELL storage runs well as the same load
> average and same XFS structure.
>
> So I think DD should just close this bug, I'll try to find the exact
> reason from another view.
Thanks, closing the bug then.
Cheers,
Moritz
--- End Message ---
