From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gossamer.nmsrv.com ([208.70.244.21]:44771 "EHLO gossamer.nmsrv.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751625Ab1AYWZs (ORCPT ); Tue, 25 Jan 2011 17:25:48 -0500 Message-ID: <4D3F4DE5.7020905@gt.net> Date: Tue, 25 Jan 2011 14:25:41 -0800 From: Nathan March To: linux-nfs@vger.kernel.org Subject: Re: Stale file not being refreshed automatically? References: <4D3F4A8A.7040003@gt.net> In-Reply-To: <4D3F4A8A.7040003@gt.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 Just to add, this is 2.6.32.27 w/ grsecurity. - Nathan On 1/25/2011 2:11 PM, Nathan March wrote: > 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 > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html