[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-nfs
Subject:    RE: [NFS] Stale NFS file handle
From:       "Lever, Charles" <Charles.Lever () netapp ! com>
Date:       2005-03-23 18:59:25
Message-ID: 482A3FA0050D21419C269D13989C6113085398F4 () lavender-fe ! eng ! netapp ! com
[Download RAW message or body]

filipe-

in general the kernel patches i referred to earlier will prevent most
issues when using rsync and serving web pages.  an occassional ESTALE is
unavoidable because no NFS client can recover from an ESTALE during a
read operation.  however, the patches do allow a subsequent open(2)
operation on that pathname to find the new file.


> -----Original Message-----
> From: Filipe Brandenburger [mailto:branden@terra.com.br] 
> Sent: Wednesday, March 23, 2005 12:15 PM
> To: Trond Myklebust
> Cc: Steve Dickson; nfs@lists.sourceforge.net
> Subject: Re: [NFS] Stale NFS file handle
> 
> 
> * Wed, 23 Mar 2005 08:57:15 -0500, Trond Myklebust 
> <trond.myklebust@fys.uio.no>:
> > He was running
> > 
> > while :; do cat test.txt; done >/dev/null
> > 
> > on a client, then deleting the file on the server. Even if 
> the call to
> > open() is successful, you both can and will get ESTALEs on the 
> > subsequent call to read().
> 
> Ok,
> 
> But then, how do you suggest I should change applications to 
> do it? The applications that publish content to the NFS run 
> on one host and are based on rsync, the applications that 
> deliver content are web servers
> (Apache) reading from this same NFS on another pool of hosts 
> (these are the ones that get the ESTALE error).
> 
> Where is the problem? On the applications that publish? 
> Should they open the file and update it in-place instead of 
> creating a new one and renaming? I don't think so! This would 
> lead to content that is a mix of the old and the new, that is corrupt.
> 
> Or is the webserver? Should the application protect itself 
> from ESTALE errors and retry? Somehow that seems wrong to me 
> also. Then I would have to change all applications that read 
> this content to do it. Why doesn't the NFS client recover 
> from this kind of errors?
> 
> If it's really not possible to change it on the NFS client 
> (the kernel), what workaround would you suggest me to use?
> 
> Thanks,
> Filipe
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Microsoft Mobile & Embedded 
> DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more 
> about the latest Windows
> Embedded(r) & Windows Mobile(tm) platforms, applications & 
> content.  Register by 3/29 & save $300 
> http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/nfs
> 


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&opĚk
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

[prev in list] [next in list] [prev in thread] [next in thread]