From: Cedric - Equinoxe Media <cedric@e-m.fr>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs crash
Date: Tue, 6 Nov 2007 17:07:21 +0100 [thread overview]
Message-ID: <20071106160721.GB25295@e-m.fr> (raw)
In-Reply-To: <20071106092157.GB16694@e-m.fr>
I just had exactly the same crash again today :
/dev/sda4 on /filer type xfs (rw,noexec,nosuid,nodev,noatime)
Nov 6 16:40:24 fng2 kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff88113b35
Nov 6 16:40:24 fng2 kernel:
Nov 6 16:40:24 fng2 kernel: Call Trace:
Nov 6 16:40:24 fng2 kernel: [<ffffffff88111fcb>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
Nov 6 16:40:24 fng2 kernel: [<ffffffff88113b35>] :xfs:xfs_free_extent+0xa9/0xc9
Nov 6 16:40:24 fng2 kernel: [<ffffffff8811cf77>] :xfs:xfs_bmap_finish+0xee/0x167
Nov 6 16:40:24 fng2 kernel: [<ffffffff8813c843>] :xfs:xfs_itruncate_finish+0x19b/0x2e0
Nov 6 16:40:24 fng2 kernel: [<ffffffff881543c1>] :xfs:xfs_setattr+0x841/0xe57
Nov 6 16:40:24 fng2 kernel: [<ffffffff8815c328>] :xfs:xfs_fs_get_dentry+0x38/0x59
Nov 6 16:40:24 fng2 kernel: [<ffffffff80229db3>] task_rq_lock+0x3d/0x6f
Nov 6 16:40:24 fng2 kernel: [<ffffffff80229976>] __activate_task+0x26/0x38
Nov 6 16:40:24 fng2 kernel: [<ffffffff8815eae8>] :xfs:xfs_vn_setattr+0x121/0x144
Nov 6 16:40:24 fng2 kernel: [<ffffffff80296791>] notify_change+0x156/0x2f1
Nov 6 16:40:24 fng2 kernel: [<ffffffff88309aba>] :nfsd:nfsd_setattr+0x334/0x4b1
Nov 6 16:40:24 fng2 kernel: [<ffffffff883102e2>] :nfsd:nfsd3_proc_setattr+0xa2/0xae
Nov 6 16:40:24 fng2 kernel: [<ffffffff8830524d>] :nfsd:nfsd_dispatch+0xdd/0x19e
Nov 6 16:40:24 fng2 kernel: [<ffffffff88283180>] :sunrpc:svc_process+0x3df/0x6ef
Nov 6 16:40:24 fng2 kernel: [<ffffffff803f4cc2>] __down_read+0x12/0x9a
Nov 6 16:40:24 fng2 kernel: [<ffffffff88305815>] :nfsd:nfsd+0x191/0x2ac
Nov 6 16:40:24 fng2 kernel: [<ffffffff8020aba8>] child_rip+0xa/0x12
Nov 6 16:40:24 fng2 kernel: [<ffffffff88305684>] :nfsd:nfsd+0x0/0x2ac
Nov 6 16:40:24 fng2 kernel: [<ffffffff8020ab9e>] child_rip+0x0/0x12
Nov 6 16:40:24 fng2 kernel:
Nov 6 16:40:24 fng2 kernel: xfs_force_shutdown(sda4,0x8) called from line 4258 of file fs/xfs/xfs_bmap.c. Return address = 0xffffffff8811cfb4
Nov 6 16:40:24 fng2 kernel: Filesystem "sda4": Corruption of in-memory data detected. Shutting down filesystem: sda4
Nov 6 16:40:24 fng2 kernel: Please umount the filesystem, and rectify the problem(s)
Seems to be again on a setattr() ?
Regards.
Cédric
next prev parent reply other threads:[~2007-11-06 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:51 xfs crash Cedric - Equinoxe Media
[not found] ` <20071106082632.GU995458@sgi.com>
2007-11-06 9:21 ` Cedric - Equinoxe Media
2007-11-06 16:07 ` Cedric - Equinoxe Media [this message]
2007-11-06 16:44 ` Justin Piszcz
2007-11-06 17:08 ` Cedric - Equinoxe Media
2007-11-06 20:55 ` David Chinner
2007-11-07 10:58 ` Cedric - Equinoxe Media
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 4:45 Jabir M
2010-05-18 6:02 ` Dave Chinner
2010-05-19 11:26 ` Jabir M
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=20071106160721.GB25295@e-m.fr \
--to=cedric@e-m.fr \
--cc=dgc@sgi.com \
--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