From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: nfs@lists.sourceforge.net
Subject: Hang when shutting down - seems umount and NFS related - kernel version 2.6.18.1
Date: Tue, 27 Feb 2007 00:04:19 +0100 [thread overview]
Message-ID: <9a8748490702261504n147aa444y779153c03a2d44a2@mail.gmail.com> (raw)
I have a server that has the sole job of serving up a bunch of NFS
filesystems to webservers. The server is running kernel 2.6.18.1
A few days ago when attempting to reboot the server, the shutdown
process hung with a backtrace on the console. A photo was taken and is
available here:
http://www.kernel.org/pub/linux/kernel/people/juhl/images/DSC00504.jpg
A quick (incomplete) text transcript of the photo is here:
EIP: [<c01a51a0>] nfs_clear_inode+0x61/0x6b SS:ESP 0068:eb476ee4
BUG: warning at kernel/exit.c:855/do_exit()
do_exit do_trap
do_trap do_invalid_op
do_invalid_op nfs_clear_inode
scheduler_tick radix_tree_gang_lookup_tag
nfs_wait_on_reques_locked error_code
nfs3_forget_cached_acls nfs_clear_inode
clear_inode dispose_list
invalidate_inodes generic_shutdown_super
kill_anon_super nfs_kill_super
deactivate_super sys_umount
sys_readlink syscall_call
BUG: umount/20593, lock held at task exit time!
{alloc_super}
.. held by: umount:20593
... acquired at: generic_shutdown_super
/etc/rc6.d/S01reboot: line4: 20593 Segmentation fault $*
[FAILED]
Unmounting filesystems (retry):
The problem has only manifested itself this once, so unfortunately not
reproducible on demand, but I hope that maybe someone more
knowledgable of NFS internals than me can figure out what went wrong
and a way to fix it in the future (if it's not already fixed) :-)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next reply other threads:[~2007-02-26 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 23:04 Jesper Juhl [this message]
2007-02-26 23:19 ` Chuck Ebbert
2007-02-27 11:27 ` Jesper Juhl
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=9a8748490702261504n147aa444y779153c03a2d44a2@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®