Hi, 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 defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log 0 0 The mounted volume is a read-only volume. The log file includes following lines. [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 [2012-03-24 00:46:02.981545] W [read-only.c:259:init] 0-readonly-autoload: dangling volume. check volfile [2012-03-24 00:46:02.981634] W [write-behind.c:3023:init] 0-korolev-write-behind: disabling write-behind for first 0 bytes [2012-03-24 00:46:02.984363] I [client.c:1935:notify] 0-korolev-client-0: parent translators are ready, attempting connect on transport [2012-03-24 00:46:02.984791] I [client.c:1935:notify] 0-korolev-client-1: parent translators are ready, attempting connect on transport Regards, Yang Ye
_______________________________________________ Gluster-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gluster-devel
