[Gluster-users] read only feature only works after the volume is restarted?

[fanghuang.data at yahoo.com]

Hi Atin,
Thank you for your work on it. What is blocking the patch? Could you ping it for the reviewers? Best Regards,
Fang Huang 

     On Monday, 16 February 2015, 12:28, Atin Mukherjee <amukherj at redhat.com> wrote:
   
 

 

On 02/13/2015 02:05 PM, Feng Wang wrote:
> Hi all,
> If we set the read-only feature using the following command in the cli to a volume in service, it will not work until the volume is restarted.
That's the correct functionality. http://review.gluster.org/#/c/8571/
should address it, however it hasn't been taken yet.

> gluster volume set vol-name features.readonly on
> It means that the service must be stopped temporarily. Does this make sense?
> An alternative method is re-mounting the glusterfs using the "-o ro" option. So both of them need the service to be interrupted . Could we have the method to make the volume read-only after flushing the requests on the fly without stopping the service? 
>  Best Regards,
> Fang Huang
> 
> 
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
> 

-- 
~Atin


 
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150302/1d8c8ddd/attachment.html>