From: "George Spelvin" <linux@horizon.com>
To: bfields@fieldses.org, linux@horizon.com
Cc: linux-nfs@vger.kernel.org, nix@esperi.org.uk
Subject: Re: persistent, quasi-random -ESTALE at mount time
Date: 2 Feb 2011 23:28:14 -0500 [thread overview]
Message-ID: <20110203042814.6364.qmail@science.horizon.com> (raw)
In-Reply-To: <20110203034844.GA30641@fieldses.org>
> So the reboot was for an upgrade from 2.6.26-rcX to 2.6.38-rc3? I
> wonder if a reboot (or just a server restart) without changing kernels
> would see the same problem?
Whoops, typo. It was from 2.6.36-rcX (I think -rc5, but it's scrolled
off the logs), not .26.
> We work quite hard to ensure that filehandles returned from older nfsd's
> will still be accepted by newer ones. But that doesn't mean there
> couldn't failed at that somehow in some case....
I understand that sometimes there's an incompatible server change, but
I don't ever remember a Linux-linux nfs mount surviving a server
reboot.
However, the problem I'm complaining about here is more alarming. With
a clean client, attempting to *mount* is failing with -ESTALE.
> If you manage to reproduce the problem, /proc/fs/nfs/exports before and
> after the reboot would be interesting, and ideally also a network trace
> showing traffic before and after the reboot (including the operation
> that returned the STALE error).
Can do. How much detail do you want in the packet trace? Is -vvv
enough, or do you want -X as well?
Thank you very much for the response; I'll try to reproduce and
capture the problem.
--
-Colib
next prev parent reply other threads:[~2011-02-03 4:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 3:56 persistent, quasi-random -ESTALE at mount time George Spelvin
2011-02-03 3:48 ` J. Bruce Fields
2011-02-03 4:28 ` George Spelvin [this message]
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=20110203042814.6364.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).