All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Nix <nix@esperi.org.uk>
Cc: George Spelvin <linux@horizon.com>, linux-nfs@vger.kernel.org
Subject: Re: persistent, quasi-random -ESTALE at mount time
Date: Sun, 6 Feb 2011 14:23:07 -0500	[thread overview]
Message-ID: <20110206192307.GA14850@fieldses.org> (raw)
In-Reply-To: <87sjw156yx.fsf-AdTWujXS48Mg67Zj9sPl2A@public.gmane.org>

On Sun, Feb 06, 2011 at 06:54:46PM +0000, Nix wrote:
> On 3 Feb 2011, J. Bruce Fields uttered the following:
> > On Thu, Feb 03, 2011 at 08:30:48AM +0000, Nix wrote:
> >> I can give you a packet dump from my (completely reproducible) failure
> >> with the same symptoms, if you like. (Again, it is fixed by running
> >> exportfs repeatedly, each time fixing another few mounts: currently,
> >> I have to run it six times.)
> >
> > That would be great, thanks.  And could you collect the contents of
> > /proc/net/rpc/{nfsd.fh,nfsd.export}/content at the same time?  (I think
> > you already sent some; but I'd be curious to match them up with the
> > packet trace.)  Also, the output of "blkid" might help diagnose any
> > problems with uuid's.
> 
> I jinxed it. I just recompiled and the problem went away. The only
> differences between the old and new kernel are a so-far-entirely-
> unconfigured IPv6 setup (so nothing but link-local private addresses, no
> routing, nothing) and a new compiler (4.5.x rather than 4.4.x).
> 
> Which of these caused the change in behaviour I do not yet know, but
> will try to figure out (by turning IPv6 off again and seeing if
> the problem recurs).

OK, thanks.

--b.

  parent reply	other threads:[~2011-02-06 19:23 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
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 [this message]
     [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=20110206192307.GA14850@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux@horizon.com \
    --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.