Nicolas Williams wrote: > On Fri, Aug 21, 2009 at 09:09:58PM +0200, Roland Mainz wrote: > > AFAIK this means the "fuse" kernel module needs to implement support for > > |VOP_FID()| and (optionally) allow FUSE userland drivers to implement > > this functionality... right ? > > Yes. At the very least it has to for NFSv2 and NFSv3.
IMO it would be a good idea if the userland driver can (optionally) provide it's own fid information... > The NFSv4 protocol allows servers to issue something called "volatile > filehandles" to workaround the lack of open-by-inode (or even lack of > inode numbers altogether -- FAT was, IIUC, the motivation for volatile > FHs). Another reason would be a SMBFB<--->NFS bridge. For example in my university we had for a long time a NovelFS<--->NFS bridge to connect old Unix machines with old Novel machines using a Linux machine which ex-exported a mounted Novel filesystem... BTW: Does the Solaris NFSv4 client support volatile filehandles ? > The Solaris NFSv4 server does not support volatile filehandles. Is there a bugid for this ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)
