Re: Specific volume name causing read-only?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux