From: Trond Myklebust Subject: Re: Stale file handle Date: 04 Feb 2003 09:49:00 +0100 Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <200302031903.53937.chris-nfs@drspirograph.com> <200302041218.31527.chris-nfs@drspirograph.com> <15935.5764.263002.800295@charged.uio.no> <200302041239.22301.chris-nfs@drspirograph.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net Return-path: Received: from mons.uio.no ([129.240.130.14] ident=7411) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18fylT-0001Mz-00 for ; Tue, 04 Feb 2003 00:49:12 -0800 To: Chris Jensen In-Reply-To: <200302041239.22301.chris-nfs@drspirograph.com> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == Chris Jensen writes: > So is it just a coincidence that this has worked for over a > year? I wouldn't have thought so, because there have often been You ought to have the source available to you so feel free to take a look. However unless you have been using some specially patched version of the kernel, then VFAT support will be poor, as described. I believe that a lot could be done to fix this particular issue. Although it is clear that some compromises will need to be made w.r.t. the NFSv3 specs, the stale filehandle thing could perhaps be fixed by (for instance) encoding the beginning of the FAT chain of the file + the parent directory in the filehandle. Such an encoding is admittedly not safe under renames of the file, but it would already be a huge improvement. Cheers, Trond ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs