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 ----- Original Message ----- > From: "Alun James" <ajames@xxxxxxxxx> > To: gluster-users@xxxxxxxxxxx > Sent: Wednesday, March 25, 2015 6:33:05 AM > Subject: Gluster/NFS mount issues > > Hi folks, > > I am having some issues getting NFS to mount the glusterfs volume on boot-up, > I have tried all the usual mount options in fstab, but thus far none have > helped I am using NFS as it seems to give better performance for my workload > compared with glusterfs client. > > [Node Setup] > > 3 x Nodes mounting vol locally. > Ubuntu 14.04 3.13.0-45-generic > GlusterFS: 3.6.2-ubuntu1~trusty3 > nfs-common 1:1.2.8-6ubuntu1.1 > > Type: Replicate > Status: Started > Number of Bricks: 1 x 3 = 3 > Transport-type: tcp > Bricks: > Brick1: node01:/export/brick0 > Brick2: node 02:/export/brick0 > Brick3: node 03:/export/brick0 > > /etc/fstab: > > /dev/mapper/gluster--vg-brick0 /export/brick0 xfs defaults 0 0 > > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock,mountproto=tcp,vers=3 0 0 > > > [Issue] > > On boot, the /data partition is not mounted, however, I can jump on each node > and simply run "mount /data" without any problems, so I assume my fstab > options are OK. I have noticed the following log: > > /var/log/upstart/mountall.log: > > mount.nfs: requested NFS version or transport protocol is not supported > mountall: mount /data [1178] terminated with status 32 > > I have attempted the following fstab options without success and similar log > message: > > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock 0 0 > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock,mountproto=tcp,vers=3 0 0 > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock,vers=3 0 0 > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock,nfsvers=3 0 0 > localhost:/my_filestore_vol /data nfs > defaults,nobootwait,noatime,_netdev,nolock,mountproto=tcp,nfsvers=3 0 0 > > Anything else I can try? > > Regards, > > ALUN JAMES > Senior Systems Engineer > Tibus > > T: +44 (0)28 9033 1122 > E: ajames@xxxxxxxxx > W: www.tibus.com > > Follow us on Twitter @tibus > > Tibus is a trading name of The Internet Business Ltd, a company limited by > share capital and registered in Northern Ireland, NI31235. It is part of UTV > Media Plc. > > This email and any attachment may contain confidential information for the > sole use of the intended recipient. Any review, use, distribution or > disclosure by others is strictly prohibited. If you are not the intended > recipient (or authorised to receive for the recipient), please contact the > sender by reply email and delete all copies of this message. > > _______________________________________________ > 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
