From: "George Spelvin" <linux@horizon.com>
To: linux-nfs@vger.kernel.org
Cc: bfields@fieldses.org, linux@horizon.com, nix@esperi.org.uk
Subject: Re: persistent, quasi-random -ESTALE at mount time
Date: 1 Feb 2011 22:56:36 -0500 [thread overview]
Message-ID: <20110202035636.32013.qmail@science.horizon.com> (raw)
For what it's worth, I'm seeing the same problem.
The server was just rebooted with 2.6.38-rc3, and the client reported
"STALE NFS file handle". I wish I understood why; I thought the point
of a stateless protocol was that it could survive server reboots.
Anyway, I found all the affected processes, killed them, unmounted,
tried to remount, and lo and behold:
mount("server:/path/dir", "/client/dir", "nfs", MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC, "addr=ww.xx.yy.zz,vers=3,proto=tcp,mountvers=3,mountproto=tcp,mountport=2050") = -1 ESTALE (Stale NFS file handle)
The server is just logging
send(10, "<29>Feb 1 22:39:49 mountd[4167]: authenticated mount request from $CLIENT:912 for /path/dir (/path/dir)", 125, MSG_NOSIGNAL) = 125
/proc/fs/nfs/exports is reporting:
/path/dir *.dom.ain,client.dom.ain(ro,root_squash,async,wdelay,no_subtree_check,uuid=3210ba59:586b43f2:8780109f:d915f4ab)
Debian packaged nfs utilities 1.2.2-4 on both server and client. 32 bits in both cases. (Server is
running a 64-bit kernel, but 32-bit userland.)
It worked immediately before the reboot (when the server was runnign 2.6.26-rcX).
"exportfs -a" several times did NOT fix it, but restarting mountd and nfsd
("/etc/init.d/nfs-kernel-server restart") fixed it.
Anyway, quite annoying. Unfortunately, that's a server I don't like to reboot.
(But I can restart the NFS server safely if that would help testing.)
next reply other threads:[~2011-02-02 3:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 3:56 George Spelvin [this message]
2011-02-03 3:48 ` persistent, quasi-random -ESTALE at mount time J. Bruce Fields
2011-02-03 4:28 ` George Spelvin
2011-02-03 4:37 ` J. Bruce Fields
2011-02-03 4:40 ` J. Bruce Fields
2011-02-03 8:30 ` Nix
2011-02-03 13:40 ` J. Bruce Fields
2011-02-06 18:54 ` Nix
[not found] ` <87sjw156yx.fsf-AdTWujXS48Mg67Zj9sPl2A@public.gmane.org>
2011-02-06 19:23 ` J. Bruce Fields
[not found] ` <AANLkTinUMeTowsWtxFm+Ga_ChVztWuUNe6na_Tq+F2==@mail.gmail.com>
2011-02-06 19:31 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 20:28 Nix
2010-09-22 15:52 ` J. Bruce Fields
2010-09-23 21:03 ` Nix
2010-10-01 22:00 ` J. Bruce Fields
2010-10-01 22:41 ` Nix
2010-10-01 23:11 ` J. Bruce Fields
2010-12-17 20:45 ` Nix
2010-12-24 18:27 ` J. Bruce Fields
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=20110202035636.32013.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).