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

Yang Ye leafyoung at yahoo.com
Mon Apr 2 04:27:08 UTC 2012


thanks. 806978.
On Apr 2, 2012 12:11 PM, "Amar Tumballi" <amarts at redhat.com> wrote:

> On 03/26/2012 10:24 PM, Yang Ye wrote:
>
>> 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.
>>
>>
> Can let me know the bug number? I was not able to find it while submitting
> a patch for fixing this behavior
> (ref: http://review.gluster.com/3058**).
>
> Regards,
> Amar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20120402/33058788/attachment-0003.html>


More information about the Gluster-devel mailing list