[Gluster-devel] Specific volume name causing read-only?
Amar Tumballi
amarts at redhat.com
Mon Apr 2 04:11:25 UTC 2012
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
More information about the Gluster-devel
mailing list