I believe the following events have happened in the cluster resulting into this situation: 1. GlusterD & brick process on node 2 was brought down 2. Node 1 was rebooted. In the above case the mount will definitely fail since the brick process was not started as in a 2 node set up glusterd waits its peers to come up before it starts the bricks. Could you check whether the brick process is running or not? Thanks, Atin On 08/31/2015 04:17 PM, Yiping Peng wrote: > I've tried both: assuming server1 is already in pool, server2 is undergoing > peer-probing > > server2:~$ mount server1:/vol1 mountpoint, fail; > server2:~$ mount server2:/vol1 mountpoint, fail. > > Strange enough. I *should* be able to mount server1:/vol1 on server2. But > this is not the case :( > Maybe something is broken in the server pool, as I'm seeing disconnected > nodes? > > > 2015-08-31 18:02 GMT+08:00 Ravishankar N <ravishankar@xxxxxxxxxx>: > >> >> >> On 08/31/2015 12:53 PM, Merlin Morgenstern wrote: >> >> Trying to mount the brick on the same physical server with deamon running >> on this server but not on the other server: >> >> @node2:~$ sudo mount -t glusterfs gs2:/volume1 /data/nfs >> Mount failed. Please check the log file for more details. >> >> For mount to succeed the glusterd must be up on the node that you specify >> as the volfile-server; gs2 in this case. You can use -o >> backupvolfile-server=gs1 as a fallback. >> -Ravi >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users@xxxxxxxxxxx >> http://www.gluster.org/mailman/listinfo/gluster-users >> > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
