Thanks, Harshavardhana, Anand for the tips!
I checked out parts of the linux-2.6.34 (the one we are using down here)
knfsd/fuse code. I understood (hopefully, rightly) that when we export a fuse
directory over NFS and specify an fsid, the handle is constructed somewhat like
this:
fh_size (4 by
On Tue, Dec 24, 2013 at 8:21 AM, Anirban Ghoshal
wrote:
> Hi, and Thanks a lot, Anand!
>
> I was initially searching for a good answer to why the glusterfs site lists
> knfsd as NOT compatible with the glusterfs. So, now I know. :)
>
> Funnily enough, we didn't have a problem with the failover du
Hi, and Thanks a lot, Anand!
I was initially searching for a good answer to why the glusterfs site lists
knfsd as NOT compatible with the glusterfs. So, now I know. :)
Funnily enough, we didn't have a problem with the failover during our testing.
We passed constant fsid's (fsid=xxx) while expo
RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.2qa5/
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.2qa5.tar.gz
This release is made off jenkins-release-54
-- Gluster Build System
___
Gluster-users mailing list
Gluster-us
Hi,
Allowing noforget option to FUSE will not help for your cause. Gluster
persents the address of the inode_t as the nodeid to FUSE. In turn FUSE
creates a filehandle using this nodeid for knfsd to export to nfs client.
When knfsd fails over to another server, FUSE will decode the handle
encoded b
