"NFS: Buggy server - nlink == 0!" & segfault

Andy Mastbaum
2009-09-27T20:40:23Z

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