I think it is worth to implement a lock option. +1
Rafi KC On 11/14/2016 06:12 AM, David Gossage wrote: > On Sun, Nov 13, 2016 at 6:35 PM, Lindsay Mathieson > <[email protected] <mailto:[email protected]>> wrote: > > As discussed recently, it is way to easy to make destructive changes > to a volume,e.g change shard size. This can corrupt the data with no > warnings and its all to easy to make a typo or access the wrong volume > when doing 3am maintenance ... > > So I'd like to suggest something like the following: > > gluster volume lock <volname> > > Setting this would fail all: > - setting changes > - add bricks > - remove bricks > - delete volume > > gluster volume unlock <volname> > > would allow all changes to be made. > > Just a thought, open to alternate suggestions. > > Thanks > > + > sounds handy > > -- > Lindsay > _______________________________________________ > Gluster-users mailing list > [email protected] <mailto:[email protected]> > http://www.gluster.org/mailman/listinfo/gluster-users > <http://www.gluster.org/mailman/listinfo/gluster-users> > > > > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
