[Gluster-devel] Specific volume name causing read-only?

Vijay Bellur vbellur at redhat.com
Mon Mar 26 15:15:50 UTC 2012

On 03/26/2012 08:03 PM, Yang Ye wrote:
> Hi,
> Will the volume name causing read-only volume?
> When I create a volume named as korolev with following
> gluster> volume create korolev replica 2 transport tcp ...
> and mount with
>       /home/korolev    glusterfs 
> defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log   
>    0 0
> The mounted volume is a read-only volume.

This is a bug. The 'ro' in the log-file name should be causing this. Can 
you please open a bug report? A workaround for now would be to use a 
log-file name that doesn't contain 'ro'.


More information about the Gluster-devel mailing list