Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Erez Zadok <ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org>
Cc: nfs@lists.sourceforge.net, linux-nfs@vger.kernel.org,
	Trond.Myklebust@netapp.com
Subject: Re: [NFS] nfs2/3 ESTALE bug on mount point (v2.6.24-rc8)
Date: Mon, 28 Jan 2008 22:48:35 -0500	[thread overview]
Message-ID: <20080129034834.GA1190@fieldses.org> (raw)
In-Reply-To: <200801290303.m0T33miE028199-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>

On Mon, Jan 28, 2008 at 10:03:48PM -0500, Erez Zadok wrote:
> In message <20080129010819.GD16785@fieldses.org>, "J. Bruce Fields" writes:
> > On Sun, Jan 27, 2008 at 11:37:59PM -0500, Erez Zadok wrote:
> 
> > > You can find both an strace and content files in
> > > 
> > > 	http://agora.fsl.cs.sunysb.edu/tmp/nfs/
> 
> Sorry.  I guess tar on /proc files doesn't really save the content of the
> files.

Hm.

> I cat'ed the content files and alo placed an updated strace in the above
> URL.  Here's the content files.  In this run, I got an ESTALE on
> /n/lower/b2:
> 
>   mkdir: cannot create directory `/n/lower/b2': Stale NFS file handle

OK, thanks.  This looks consistent with the strace I looked at.  So
utils/mountd/cache.c:nfsd_fh() is occasionally getting the wrong result
for some reason.

--b.

  parent reply	other threads:[~2008-01-29  3:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 18:19 [NFS] nfs2/3 ESTALE bug on mount point (v2.6.24-rc8) Erez Zadok
     [not found] ` <200801211819.m0LIJU6Y017173-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-21 19:31   ` J. Bruce Fields
2008-01-21 20:28     ` [NFS] " Erez Zadok
     [not found]       ` <200801212028.m0LKSpwA002924-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-21 22:08         ` J. Bruce Fields
2008-01-22 16:41           ` J. Bruce Fields
2008-01-28  4:37             ` [NFS] " Erez Zadok
     [not found]               ` <200801280437.m0S4bxcE001453-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-28 15:35                 ` Kevin Coffman
2008-01-29  1:08                 ` J. Bruce Fields
2008-01-29  3:03                   ` [NFS] " Erez Zadok
     [not found]                     ` <200801290303.m0T33miE028199-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-29  3:48                       ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-21  3:27 Erez Zadok

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=20080129034834.GA1190@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox