On Wed, May 2, 2012 at 10:58 AM, Kaushal M <address@hidden>
Took a look at your patch for fixing this problem. It solves the it for the brick glusterfsd processes. But glusterd also spawns and communicates with nfs server & self-heal daemon processes. The proper xlator-option is not set for these. This might be the cause. These processes are started in glusterd_nodesvc_start() in glusterd-utils, which is where you could look into.
On Fri, Apr 27, 2012 at 10:31 PM, Emmanuel Dreyfus <address@hidden>
I am still trying on 3.3.0qa39, and now I have an address family issue:
gluserfs defaults to inet6 transport while the machine is not configured
I added option transport.address-family inet in glusterfs/glusterd.vol
and now glusterd starts with an IPv4 address, but unfortunately,
communication with spawned glusterfsd do not stick to the same address
family: I can see packets going from ::1.1023 to ::1.24007 and they are
rejected since I used transport.address-family inet.
I need to tell glusterfs to use the same address family. I already did a
patch for exactly the same problem some time ago, this is not very
difficult, but it would save me some time if someone could tell me where
should I look at in the code.
Gluster-devel mailing list