<div class="gmail_quote"><div class="gmail_quote"><div><div>Hi,</div><div><br></div><div>Will the volume name causing read-only volume?</div><div><br></div><div>When I create a volume named as korolev with following</div><div>
<br></div><div>gluster> volume create korolev replica 2 transport tcp ...</div>
<div><br></div><div>and mount with</div><div>192.168.2.103:/korolev /home/korolev glusterfs defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log 0 0</div><div><br></div><div>The mounted volume is a read-only volume.</div>
<div><br></div><div>The log file includes following lines.</div><div><br></div><div>[2012-03-24 00:46:02.41055] I [glusterfsd.c:1493:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.2.5</div><div>
[2012-03-24 00:46:02.981545] W [read-only.c:259:init] 0-readonly-autoload: dangling volume. check volfile</div><div>[2012-03-24 00:46:02.981634] W [write-behind.c:3023:init] 0-korolev-write-behind: disabling write-behind for first 0 bytes</div>
<div>[2012-03-24 00:46:02.984363] I [client.c:1935:notify] 0-korolev-client-0: parent translators are ready, attempting connect on transport</div><div>[2012-03-24 00:46:02.984791] I [client.c:1935:notify] 0-korolev-client-1: parent translators are ready, attempting connect on transport</div>
<div><br></div><div>Regards,</div><div>Yang Ye</div>
</div>
</div><br>
</div><br>