Re: Specific volume name causing read-only?

[Yang Ye <leafyoung@xxxxxxxxx>]

Maybe not due to log file name.

My current workaround after a few tries is to use the following

gluster> volume create k replica 2 transport tcp 192.168.2.102:/mnt/b/k 192.168.2.103:/mnt/a/k

192.168.2.103:/k          /home/korolev    glusterfs defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log      0 0

Posted to Bugzilla.

Regards,
Yang Ye

On Mon, Mar 26, 2012 at 11:15 PM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:

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
192.168.2.103:/korolev       /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'.

Thanks,
Vijay