[Gluster-users] replace-brick failing - transport.address-family not specified

[Vijay Bellur]

On 12/08/2013 07:06 PM, Nguyen Viet Cuong wrote:
> Thanks for sharing.
>
> Btw, I do believe that GlusterFS 3.2.x is much more stable than 3.4.x in
> production.
>

This is quite contrary to what we have seen in the community. From a 
development perspective too, we feel much better about 3.4.1. Are there 
specific instances that worked well with 3.2.x which does not work fine 
for you in 3.4.x?

Cheers,
Vijay