On 07/23/2013 03:55 PM, Nicholas Majeran wrote: > FWIW, I tried to disable the parameter on a stopped volume, which was > successful. I then started the volume and I could get/set the ACLs > normally. > > I'm going to try the same procedure on the gv0 volume that threw the > error previously. > Thanks. The inconsistent version possibility worries me. What does glusterfs -V and glusterfsd -V report? [root at crunch glusterfs-3.4.0]# glusterfs -V glusterfs 3.4.0 built on Jul 23 2013 16:02:16 ... [root at crunch glusterfs-3.4.0]# glusterfsd -V glusterfs 3.4.0 built on Jul 23 2013 16:02:16 ... for each machine that is a brick (glusterfsd) and each client (glusterfs)? We've had problems in the past with incomplete updates between major version revisions, to the point that we had to completely scrub any old libraries and config files off some units during updates (3.2.x and 3.3.x time periods). -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: landman at scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/siflash phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615
