Hi Tom. This is a bug. This feature was introduced to prevent setting some options when old clients are connected to a gluster volume. This was needed because the old clients wouldn't be able to understand the newer options, which could lead to unintended behaviour. But auth.allow has been available from the beginning and is moreover a server side option, so it shouldn't have failed. Could you please open a bug regarding this at [1]. Please add information on your setup/environment, including glusterfs version, volume information, the glusterd log files, version of glusterfs clients. For now, to workaround this bug, unmount all the connected clients and set the option again. [1] https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS On Tue, Apr 29, 2014 at 5:33 PM, Tom Young <tom.young@xxxxxxxxxxxxx> wrote: > Hi, > > I have 2 servers with a distributed volume “home” and I’d like to set volume > options like auth.allow, and am getting an error when I go through the > procedure in the admin guide. > > > > gluster volume set home auth.allow <IPADDR> > > “volume set: failed: One or more connected clients cannot support the > feature being set. These clients need to be upgraded or disconnected before > running this command again” > > > > > > Tom Young > > Corvid Technologies > > 145 Overhill Drive, Mooresville, NC 28117 > > (704)799-6944 x156 > > www.corvidtec.com > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
