Thanks Ben Turner, The LINKDELAY=time fixed my fstab problem, thank very much.
BTW, my issue message in log: [socket.c:2267:socket_connect_finish] 0-glusterfs: connection to 192.168.0.61:24007 failed (No route to host) [glusterfsd-mgmt.c:1811:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: gwgfs01 (Transport endpoint is not connected) ________________________________ From: "Ben Turner" <[email protected]<mailto:[email protected]>> To: "Alun James" <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Sent: Wednesday, 25 March, 2015 9:21:14 PM Subject: Re: [Gluster-users] Gluster/NFS mount issues Normally when I see this the NICs are not fully initialized. I have done a couple different things to work around this: -Try adding the linkdelay parameter to the ifcfg script: LINKDELAY=time where time is the number of seconds to wait for link negotiation before configuring the device. -Try turning on portfast on your switch to speed up negotiation. -Try putting a sleep in your init scripts just before it goes to mount your fstab items -Try putting the mount command in rc.local or whatever is the last thing your system does before it boots. Last time I looked at the _netdev code it only looked for an active link, it didn't ensure that the NIC was up and able to send traffic. I would start with the linkdelay and go from there. LMK how this works out for ya, I am not very well versed on the Ubuntu boot process :/ -b
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
