From: Cedric - Equinoxe Media <cedric@e-m.fr>
To: xfs@oss.sgi.com
Subject: xfs crash
Date: Mon, 5 Nov 2007 22:51:35 +0100 [thread overview]
Message-ID: <20071105215135.GA12238@e-m.fr> (raw)
Hi,
I got a crash with xfs serving nfs :
Hardware is Dell Poweredge 2950 with RAID5 SAS
Linux fng2 2.6.22-3-amd64 #1 SMP Wed Oct 31 13:43:07 UTC 2007 x86_64 GNU/Linux
Here is the dmesg :
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff88113b35
Call Trace:
[<ffffffff88111fcb>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
[<ffffffff88113b35>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff8811cf77>] :xfs:xfs_bmap_finish+0xee/0x167
[<ffffffff8813c843>] :xfs:xfs_itruncate_finish+0x19b/0x2e0
[<ffffffff881543c1>] :xfs:xfs_setattr+0x841/0xe57
[<ffffffff8023a29e>] __mod_timer+0xc3/0xd3
[<ffffffff80229db3>] task_rq_lock+0x3d/0x6f
[<ffffffff80229976>] __activate_task+0x26/0x38
[<ffffffff8815eae8>] :xfs:xfs_vn_setattr+0x121/0x144
[<ffffffff80296791>] notify_change+0x156/0x2f1
[<ffffffff88309aba>] :nfsd:nfsd_setattr+0x334/0x4b1
[<ffffffff883102e2>] :nfsd:nfsd3_proc_setattr+0xa2/0xae
[<ffffffff8830524d>] :nfsd:nfsd_dispatch+0xdd/0x19e
[<ffffffff88283180>] :sunrpc:svc_process+0x3df/0x6ef
[<ffffffff803f4cc2>] __down_read+0x12/0x9a
[<ffffffff88305815>] :nfsd:nfsd+0x191/0x2ac
[<ffffffff8020aba8>] child_rip+0xa/0x12
[<ffffffff88305684>] :nfsd:nfsd+0x0/0x2ac
[<ffffffff8020ab9e>] child_rip+0x0/0x12
xfs_force_shutdown(sda4,0x8) called from line 4258 of file
fs/xfs/xfs_bmap.c. Return address = 0xffffffff8811cfb4
Filesystem "sda4": Corruption of in-memory data detected. Shutting down
filesystem: sda4
Please umount the filesystem, and rectify the problem(s)
nfsd: non-standard errno: -117
----------------
Here I stopped nfs, umount -f /dev/sda4, mount /dev/sda4 then start nfs
again.
----------------
nfsd: last server has exited
nfsd: unexporting all filesystems
xfs_force_shutdown(sda4,0x1) called from line 423 of file
fs/xfs/xfs_rw.c. Return address = 0xffffffff88158289
xfs_force_shutdown(sda4,0x1) called from line 423 of file
fs/xfs/xfs_rw.c. Return address = 0xffffffff88158289
XFS mounting filesystem sda4
Starting XFS recovery on filesystem: sda4 (logdev: internal)
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
fs/xfs/xfs_alloc.c. Caller 0xffffffff88113b35
Call Trace:
[<ffffffff88111fcb>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
[<ffffffff88113b35>] :xfs:xfs_free_extent+0xa9/0xc9
[<ffffffff88145edf>] :xfs:xlog_recover_process_efi+0xf7/0x12a
[<ffffffff88147288>] :xfs:xlog_recover_process_efis+0x4f/0x81
[<ffffffff881472d3>] :xfs:xlog_recover_finish+0x19/0x9a
[<ffffffff8814bd22>] :xfs:xfs_mountfs+0x83d/0x91b
[<ffffffff802f4b29>] _atomic_dec_and_lock+0x39/0x58
[<ffffffff88151b34>] :xfs:xfs_mount+0x317/0x39d
[<ffffffff88161889>] :xfs:xfs_fs_fill_super+0x0/0x1a7
[<ffffffff88161907>] :xfs:xfs_fs_fill_super+0x7e/0x1a7
[<ffffffff803f4c21>] __down_write_nested+0x12/0x9a
[<ffffffff80297003>] get_filesystem+0x12/0x35
[<ffffffff80284ff5>] sget+0x39d/0x3af
[<ffffffff80284a0c>] set_bdev_super+0x0/0xf
[<ffffffff80284a1b>] test_bdev_super+0x0/0xd
[<ffffffff80285a35>] get_sb_bdev+0x105/0x152
[<ffffffff8028542a>] vfs_kern_mount+0x93/0x11a
[<ffffffff80285500>] do_kern_mount+0x43/0xdd
[<ffffffff80298eda>] do_mount+0x691/0x708
[<ffffffff80297a3c>] mntput_no_expire+0x1c/0x94
[<ffffffff8028cba5>] link_path_walk+0xce/0xe0
[<ffffffff80266af7>] activate_page+0xad/0xd4
[<ffffffff8025ff17>] find_get_page+0x21/0x50
[<ffffffff80262028>] filemap_nopage+0x180/0x2ab
[<ffffffff8026c709>] __handle_mm_fault+0x3e6/0x9d9
[<ffffffff80269c17>] zone_statistics+0x3f/0x60
[<ffffffff802f796f>] __up_read+0x13/0x8a
[<ffffffff802646fe>] __alloc_pages+0x5a/0x2bc
[<ffffffff80298fdb>] sys_mount+0x8a/0xd7
[<ffffffff80209d8e>] system_call+0x7e/0x83
Ending XFS recovery on filesystem: sda4 (logdev: internal)
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: starting 90-second grace period
I have no other message in the dmesg, the server has latest RAID
firmware from dell.
Cédric.
next reply other threads:[~2007-11-05 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:51 Cedric - Equinoxe Media [this message]
[not found] ` <20071106082632.GU995458@sgi.com>
2007-11-06 9:21 ` xfs crash Cedric - Equinoxe Media
2007-11-06 16:07 ` Cedric - Equinoxe Media
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=20071105215135.GA12238@e-m.fr \
--to=cedric@e-m.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.