<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Oct 30, 2015 4:35 PM, "Remi Serrano" <<a href="mailto:rserrano@pros.com">rserrano@pros.com</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> <br>
><br>
> I setup a gluster file cluster with 2 nodes. It works fine.<br>
><br>
> But, when I shut down the 2 nodes, and startup only one node, I cannot mount the share :<br>
><br>
> <br>
><br>
> [root@xxx ~]# mount -t glusterfs 10.32.0.11:/gv0 /glusterLocalShare<br>
><br>
> Mount failed. Please check the log file for more details.<br>
><br>
> <br>
><br>
> Log says :<br>
><br>
> [2015-10-30 10:33:26.147003] I [MSGID: 100030] [glusterfsd.c:2318:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.7.5 (args: /usr/sbin/glusterfs -127.0.0.1 --volfile-id=/gv0 /glusterLocalShare)<br>
><br>
> [2015-10-30 10:33:26.171964] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1<br>
><br>
> [2015-10-30 10:33:26.185685] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2<br>
><br>
> [2015-10-30 10:33:26.186972] I [MSGID: 114020] [client.c:2118:notify] 0-gv0-client-0: parent translators are ready, attempting connect on transport<br>
><br>
> [2015-10-30 10:33:26.191823] I [MSGID: 114020] [client.c:2118:notify] 0-gv0-client-1: parent translators are ready, attempting connect on transport<br>
><br>
> [2015-10-30 10:33:26.192209] E [MSGID: 114058] [client-handshake.c:1524:client_query_portmap_cbk] 0-gv0-client-0: failed to get the port number for remote subvolume. Please ume status' on server to see if brick process is running.<br>
><br>
> [2015-10-30 10:33:26.192339] I [MSGID: 114018] [client.c:2042:client_rpc_notify] 0-gv0-client-0: disconnected from gv0-client-0. Client process will keep trying to connect t brick's port is available<br>
><br>
> <br>
><br>
> And when I check the volumes I get:<br>
><br>
> [root@xxx ~]# gluster volume status<br>
><br>
> Status of volume: gv0<br>
><br>
> Gluster process TCP Port RDMA Port Online Pid<br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
> Brick 10.32.0.11:/glusterBrick1/gv0 N/A N/A N N/A<br>
><br>
> NFS Server on localhost N/A N/A N N/A<br>
><br>
> NFS Server on localhost N/A N/A N N/A<br>
><br>
> <br>
><br>
> Task Status of Volume gv0<br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
> There are no active volume tasks<br>
><br>
> <br>
><br>
> If I start th second node, all is OK.<br>
><br>
> <br>
><br>
> Is this normal ?<br>
This behaviour is by design. In a multi node cluster when GlusterD comes up it doesn't start the bricks until it receives the configuration from its one of the friends to ensure that stale information is not been referred. In your case since the other node is down bricks are not started and hence mount fails.<br>
As a workaround, we recommend to add a dummy node to the cluster to avoid this issue.<br>
><br>
> <br>
><br>
> Regards,<br>
><br>
> <br>
><br>
> Rémi<br>
><br>
> <br>
><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
><a href="mailto:Gluster-users@gluster.org"> Gluster-users@gluster.org</a><br>
><a href="http://www.gluster.org/mailman/listinfo/gluster-users"> http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</p>