From: "J. Bruce Fields" <bfields@fieldses.org>
To: Nix <nix@esperi.org.uk>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: persistent, quasi-random -ESTALE at mount time
Date: Fri, 1 Oct 2010 18:00:18 -0400 [thread overview]
Message-ID: <20101001220018.GE1472@fieldses.org> (raw)
In-Reply-To: <8762xwqijb.fsf@spindle.srvr.nix>
On Thu, Sep 23, 2010 at 10:03:36PM +0100, Nix wrote:
> On 22 Sep 2010, J. Bruce Fields verbalised:
>
> > On Tue, Sep 21, 2010 at 09:28:13PM +0100, Nix wrote:
> >> Sep 21 20:51:39 spindle info: auth_unix_ip: inbuf 'nfsd 192.168.16.20'
> >> Sep 21 20:51:39 spindle info: auth_unix_ip: client 0x1f3dde0 'mutilate.wkstn.nix'
> >> Sep 21 20:51:39 spindle info: nfsd_fh: inbuf 'mutilate.wkstn.nix 7 \x014000000000000095bd22c2253c456f8e36b6cfb9ecd4ef'
> >
> > 7 is FSID_UUID16_INUM.
> >
> >> Sep 21 20:51:39 spindle info: nfsd_fh: found (nil) path (null)
> >
> > And mountd didn't find any filesystem matching the given uuid. That's
> > strange.
>
> I'll say.
Sorry for the slow response; have you figured out anything more?
Looking through your data quickly:
...
> Now I rebooted the server, leaving the client running (actually two are
> connected right now: 'fold' is my firewall. I think you can probably
> ignore it.) Post-reboot, it looked like this:
>
> ,----
> | #uid cnt: gids...
> | # expiry=1285274048 refcnt=1 flags=3
> | # 1000 0:
> | #class IP domain
> | # expiry=1285275728 refcnt=2 flags=1
> | nfsd 192.168.16.20 mutilate.wkstn.nix
> | #path domain(flags)
> | #domain fsidtype fsid [path]
> | # expiry=2147483647 refcnt=1 flags=3
> | # mutilate.wkstn.nix 7 0x0000400100000000c222bd956f453c25cfb6368eefd4ecb9
> `----
>
> I flipped RPC debug on and rebooted the client next. The server said:
>
> Sep 23 21:33:15 spindle warning: [ 127.385537] RPC: Want update, refage=120, age=0
> Sep 23 21:33:15 spindle warning: [ 127.536779] RPC: Want update, refage=120, age=0
> [repeated 40 times]
>
> When it connected, the server said
>
> Sep 23 21:34:23 spindle warning: [ 195.696257] RPC: Want update, refage=120, age=68
...
> Sep 23 21:34:38 spindle warning: [ 210.766205] RPC: Want update, refage=120, age=83
>
> Now, the rpc/*/content files had grown again, and even the -ESTALEd
> filesystems, like /home/.spindle.srvr.nix, are represented once more:
I'm a little confused. Are you saying that in this case the client did
get ESTALE's?
> I restarted rpc.mountd and the client, so it mounted correctly. Here's a
And then here the problems was cleared and you didn't see any more of
them?
--b.
next prev parent reply other threads:[~2010-10-01 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 20:28 persistent, quasi-random -ESTALE at mount time Nix
2010-09-22 15:52 ` J. Bruce Fields
2010-09-23 21:03 ` Nix
2010-10-01 22:00 ` J. Bruce Fields [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-02-02 3:56 George Spelvin
2011-02-03 3:48 ` 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
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=20101001220018.GE1472@fieldses.org \
--to=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 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.