Hi Dirk, Yes, Ganesha creates an expanded handle from your FSAL private handle and its own steering data. See the logic in support/nfs_filehandle_mgmt_c.
Matt ----- "Dirk Jagdmann" <d...@cubic.org> wrote: > > The exportid is not meaningful to the client, however, since it is > part of > > the handle, and the clients expect handles to be unchanging for a > specific > > file, changing the exportid for a given client's VM file would > definitely > > cause problems. > > But when I write my own FSAL, I do construct my own wire handle. If I > don't > include the Export ID in my own wire handle (my file has a unique ID, > unique > even across different file systems), will be client still see the > Export ID? > Does the server software add something to the wire handle, what the > FSAL doesn't > put in there? > > -- > ---> Dirk Jagdmann > ----> http://cubic.org/~doj > -----> http://llg.cubic.org > > ------------------------------------------------------------------------------ > _______________________________________________ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Matt Benjamin CohortFS, LLC. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://cohortfs.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 ------------------------------------------------------------------------------ _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
