From: Eric Sandeen <sandeen@sandeen.net>
To: Gabriel Barazer <gabriel@oxeva.fr>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem shutting down on linux 2.6.28.9 (xfs_rename)
Date: Wed, 22 Jul 2009 23:11:33 -0500 [thread overview]
Message-ID: <4A67E2F5.2030400@sandeen.net> (raw)
In-Reply-To: <000c01ca0ae0$e85420a0$b8fc61e0$@fr>
Gabriel Barazer wrote:
> Hi,
>
> I recently put a NFS file server into production, with mostly XFS volumes on LVM. The server was quite low on traffic until this morning and one of the filesystems crashed twice since this morning with the following backtrace:
>
> Filesystem "dm-24": XFS internal error xfs_trans_cancel at line 1164 of file fs/xfs/xfs_trans.c. Caller 0xffffffff811b09a7
> Pid: 2053, comm: nfsd Not tainted 2.6.28.9-filer #1
> Call Trace:
> [<ffffffff811b09a7>] xfs_rename+0x4a1/0x4f6
> [<ffffffff811b1806>] xfs_trans_cancel+0x56/0xed
> [<ffffffff811b09a7>] xfs_rename+0x4a1/0x4f6
...
> xfs_force_shutdown(dm-24,0x8) called from line 1165 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff811b181f
> Filesystem "dm-24": Corruption of in-memory data detected. Shutting down filesystem: dm-24
>
> The two crashed are related to the same function: xfs_rename.
Can you do objdump -d xfs.ko | grep "xfs_rename\|xfs_trans_cancel" and
maybe we can see which call to xfs_trans_cancel in xfs_rename this was.
The problem relates to canceling a dirty transaction on an error path.
-Eric
> I _really_ cannot upgrade to 2.6.29 or later because of the "reconnect_path: npd != pd" bug and the maybe related radix-tree bug ( http://bugzilla.kernel.org/show_bug.cgi?id=13375 ) affecting all kernel version afeter 2.6.28.
>
> Unmounting then remounting the filesystem allow to access the mountpoint again without any error message or apparent file corruption.
> This filesystem is used by ~30 NFS clients and contains about 5M files (100GB).
>
> Before using the volume over NFS, there was only local activity (rsync syncing) and we didn't get any error.
>
> I expect to see this crash again in a few hours except if the volume is really corrupted. Does a full filesystem copy to a newly created volume would have a chance to solve the problem?
>
> Thanks,
>
> Gabriel
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-23 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 15:27 XFS filesystem shutting down on linux 2.6.28.9 (xfs_rename) Gabriel Barazer
2009-07-23 4:11 ` Eric Sandeen [this message]
2009-07-27 11:40 ` Gabriel Barazer
2009-07-27 17:40 ` Eric Sandeen
2009-07-28 0:31 ` Gabriel Barazer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A67E2F5.2030400@sandeen.net \
--to=sandeen@sandeen.net \
--cc=gabriel@oxeva.fr \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox