[Gluster-devel] Specific volume name causing read-only?
leafyoung at yahoo.com
Mon Mar 26 16:54:18 UTC 2012
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.103:/k /home/korolev glusterfs
Posted to Bugzilla.
On Mon, Mar 26, 2012 at 11:15 PM, Vijay Bellur <vbellur at redhat.com> wrote:
> On 03/26/2012 08:03 PM, Yang Ye wrote:
>> 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
>> 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'.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel