From: Andy Mastbaum <mastbaum-q5nx0x9Hqjyyum0STUha2w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: "NFS: Buggy server - nlink == 0!" & segfault
Date: Sun, 27 Sep 2009 16:04:00 -0400 [thread overview]
Message-ID: <4ABFC530.4060504@hep.upenn.edu> (raw)
Hello. I have a bunch of Linux (2.6.18-128.1.1.el5, RHEL 5.3) boxen that
mount NFS shares from Solaris, and one died recently in a conflagration
of kernel segfaults following an NFS error:
Sep 11 19:37:12 nubar6 kernel: NFS: Buggy server - nlink == 0!
Sep 11 19:47:57 nubar6 kernel: gdb[28311]: segfault at 00002b4888e73c0b
rip 0000000000508f20 rsp 00007fff4112c988 error 4
Sep 11 19:55:42 nubar6 kernel: NFS: Buggy server - nlink == 0!
Sep 11 19:55:42 nubar6 kernel: NFS: Buggy server - nlink == 0!
Sep 11 20:10:27 nubar6 kernel: NFS: giant filename in readdir (len 201)!
Sep 11 20:10:42 nubar6 kernel: NFS: giant filename in readdir (len 201)!
...
Sep 11 20:36:12 nubar6 kernel: gdb[21443]: segfault at 00002aec9e92d90c
rip 000000000050be3e rsp 00007fff6fa92250 error 4
Sep 11 22:09:42 nubar6 kernel: gdb[6258]: segfault at 000000010b7023b5
rip 0000000000508ea0 rsp 00007fff8d39da88 error 4
...
Perhaps the Solaris NFS server is indeed buggy, but shouldn't this be
caught/handled by the Linux NFS client? Any thoughts/suggestions?
Thanks!
Andy Mastbaum
mastbaum-q5nx0x9Hqjyyum0STUha2w@public.gmane.org
next reply other threads:[~2009-09-27 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 20:04 Andy Mastbaum [this message]
[not found] ` <4ABFC530.4060504-q5nx0x9Hqjyyum0STUha2w@public.gmane.org>
2009-09-28 18:29 ` "NFS: Buggy server - nlink == 0!" & segfault Jeff Layton
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=4ABFC530.4060504@hep.upenn.edu \
--to=mastbaum-q5nx0x9hqjyyum0stuha2w@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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