>
> [2013-10-08 17:33:36.662549] I [glusterfsd.c:1910:main]
> 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.4.1
> (/usr/sbin/glusterd --debug)
>
...
> [2013-10-08 17:33:36.664191] W [xlator.c:185:xlator_dynload] 0-xlator:
> /usr/lib64/glusterfs/3.4.0/xlator/mgmt/glusterd.so:
I'm on fedora 19 and gluster 3.4.0. which I installed via:
yum install glusterfs glusterfs-server glusterfs-fuse
Running /usr/sbin/glusterd --debug I got this error and glusterd did not
start:
[2013-10-08 17:33:36.662549] I [glusterfsd.c:1910:main] 0-/usr/sbin/glusterd:
Started running /us
> After giving this some more thought, I feel the cleanest way is to make
> inode_t and inode table graph aware. This way for a given GFID there will
> be one and only one inode_t at a given time no matter how many graphs are
> switched. It is also worth noting that relationship between two GFIDs d
