1. To reproduce the problem: gluster> volume create korolev replica 2 transport tcp 192.168.2.102:/mnt/b/korolev 192.168.2.103:/mnt/a/korolev mount in /etc/fstab 192.168.2.103:/korolev /home/korolev glusterfs defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log 0 0 2. This avoids the problem: gluster> volume create k replica 2 transport tcp 192.168.2.102:/mnt/b/k 192.168.2.103:/mnt/a/k This 192.168.2.103:/k /home/korolev glusterfs defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log 0 0
CHANGE: http://review.gluster.com/3058 (mount.glusterfs: multiple fixes) merged in master by Vijay Bellur (vijay)
Thanks to Jeff Darcy for making sure we fix most of the parsing issues in the mount file
[root@dhcp201-221 ~]# gluster volume create ro dhcp201-214.englab.pnq.redhat.com:/export/shanks/shanks3 Creation of volume ro has been successful. Please start the volume to access data. [root@dhcp201-221 ~]# gluster volume start ro Starting volume ro has been successful [root@dhcp201-221 ~]# [root@dhcp201-214 shanks2]# mount -t glusterfs dhcp201-221.englab.pnq.redhat.com:/ro /export/mount/shanks3 [root@dhcp201-214 shanks2]# cd /export/mount/shanks3 [root@dhcp201-214 shanks3]# touch a [root@dhcp201-214 shanks3]# ls -l total 4 -rw-r--r--. 1 root root 0 May 31 06:05 a [root@dhcp201-214 shanks3]# Verified: glusterfs-3.3.0qa45-1.el6.x86_64