linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan March <nathan@gt.net>
To: linux-nfs@vger.kernel.org
Subject: Stale file not being refreshed automatically?
Date: Tue, 25 Jan 2011 14:11:22 -0800	[thread overview]
Message-ID: <4D3F4A8A.7040003@gt.net> (raw)

Hi All,

Having a strange issue, I've reproduced this both on nfs 3 and 4. 
Currently using v4 with:

exports:
/var/home/voyage 
10.2.1.0/24(rw,fsid=0,async,wdelay,secure,no_subtree_check,anonuid=1000,anongid=1006)

fstab:
10.2.1.1:/ /mnt/voyage nfs4 
rsize=32768,wsize=32768,noatime,nosuid,rw,bg,hard,intr 0 0

Can be produced using these two commands on 2 machines:

perl -le '$| = 1 ; while (1) { sleep 1; $res = -e "/home/voyage/test"; 
if ($res) { print "-e : $res"; } else { print "-e : $res ($!)"; } }'
-e : 1

perl -le '$| = 1 ; while (1) { sleep 5; open(F, ">", 
"/home/voyage/test.foo"); close F; my $res = 
rename("/home/voyage/test.foo", "/home/voyage/test"); print "rename 
($res)"; }'

The first command will occasionally print out: -e :  (Stale NFS file handle)

Now according to http://nfs.sourceforge.net/#faq_a10 as of 2.6.12 the 
vfs should automatically retry when it gets a estale during path 
resolution. This doesn't appear to be happening though based on the 
errors I'm seeing.

Anyone have any thoughts on what might be happening here? Or am I 
misinterpreting that faq entry? (This is on ext3 if it matters)

- Nathan

             reply	other threads:[~2011-01-25 22:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 22:11 Nathan March [this message]
2011-01-25 22:25 ` Stale file not being refreshed automatically? Nathan March
2011-01-25 22:28 ` Trond Myklebust
2011-01-25 22:38   ` Nathan March
2011-01-25 22:48     ` Trond Myklebust
2011-01-25 22:52       ` Nathan March
2011-01-25 23:24   ` Nathan March
     [not found]   ` <1295994532.6867.12.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2011-01-25 23:29     ` Nathan March
2011-01-25 23:35       ` Trond Myklebust

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=4D3F4A8A.7040003@gt.net \
    --to=nathan@gt.net \
    --cc=linux-nfs@vger.kernel.org \
    /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).