From: Marc Schmitt <mschmitt@inf.ethz.ch>
To: nfs@lists.sourceforge.net
Subject: nfs_statfs: statfs error = 116
Date: Thu, 18 Sep 2003 11:56:18 +0200 [thread overview]
Message-ID: <3F698142.6070404@inf.ethz.ch> (raw)
Dear all,
Server: RedHat 7.3, kernel 2.4.20-19.7smp, nfs-util 1.0.5
Client: RedHat 7.3, kernel 2.4.18-27.7.x, nfs-utils 0.3.3-6.73
Over 200 entries in /etc/exports, after issuing 'exportfs -r', some
clients keep certain home directories stale.
On the client, the dmesg output says:
nfs: server x not responding, still trying
nfs: server x OK
nfs_statfs: statfs error = 116
nfs_statfs: statfs error = 116
nfs_statfs: statfs error = 116
nfs_statfs: statfs error = 116
bash# ls -ld /home/user
ls: /home/user: Stale NFS file handle
On the server, I'm looking at the traffic from client ('tcpdump -s300 -i
eth2 -Nt host client'):
...
client.4180178520 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4180178520: reply ok 32 (DF)
client.4196955736 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4196955736: reply ok 32 (DF)
client.4213732952 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4213732952: reply ok 32 (DF)
client.4230510168 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4230510168: reply ok 32 (DF)
client.4247287384 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4247287384: reply ok 32 (DF)
client.4264064600 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4264064600: reply ok 32 (DF)
client.4280841816 > fs.nfs: 112 read fh Unknown/1 4096 bytes @
0x000029000 (DF)
x.nfs > client.4280841816: reply ok 32 (DF)
...
I don't know how to interpret this, but the facts are:
- the server x is running NFS, most clients still work w/o problems
- client can not recover from the stale handle and it looks like it is
spamming the server
My questions are:
- Is this a race?
- Is there a way to get the client working again w/o having to reboot
(or kill all the users processes and umount the home if that's
possible)? I tried restarting rpc.statd on the client but that did not help.
- How can I provide more debugging infos if needed?
- Could this be related to the thread "[NFS] nfs errors clutter up logs
after 2.4.20 -> 2.4.22-pre10", we really see a lot of messages like that
on all clients
Thanks for your help.
Regards,
Marc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-09-18 9:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 9:56 Marc Schmitt [this message]
2003-09-18 13:49 ` nfs_statfs: statfs error = 116 Steve Dickson
2003-09-18 19:24 ` Bernd Schubert
2003-09-18 19:31 ` Marc Schmitt
2003-09-18 19:49 ` Bernd Schubert
2003-11-14 14:57 ` Marc Schmitt
2003-09-18 19:26 ` Marc Schmitt
2003-09-19 0:22 ` Neil Brown
2003-09-19 9:27 ` Marc Schmitt
2003-09-21 13:38 ` Marc Schmitt
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 14:15 martin.knoblauch
2003-11-13 14:39 ` Richard B. Johnson
2003-11-13 14:52 ` Martin.Knoblauch
2003-11-13 20:26 ` Jesse Pollard
2003-11-13 20:34 ` Trond Myklebust
2003-11-14 8:43 ` Martin.Knoblauch
2003-11-14 13:49 ` Trond Myklebust
2003-11-14 14:22 ` Martin.Knoblauch
2003-11-13 15:27 ` Trond Myklebust
2003-11-13 16:00 ` Richard B. Johnson
2003-11-13 17:03 ` Trond Myklebust
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=3F698142.6070404@inf.ethz.ch \
--to=mschmitt@inf.ethz.ch \
--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 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.