Oh but a much bigger problem is this... Mounting NFS from localhost is a BAD IDEA. There's a well known deadlock condition when under heavy load. It WILL fail on you!
I can't find a link to more info but if anyone can fill in the details please do. This is not unique to the gluster nfs server, it applies to any nfs server and client mount of it on the same machine. Beware. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/1012768 Title: Mounting volumes from localhost using NFS clients and the Gluster-NFS server fails at boot time Status in “glusterfs” package in Ubuntu: Confirmed Bug description: GlusterFS provides it's own NFS server which exports glusterfs volumes. If an NFS client is used to mount a localhost glusterfs volume at boot time it's likely that the mount will be executed in fstab before the gluster-nfs server is ready. There was a similar issue when using the glusterfs FUSE client (mount type "glusterfs") which I fixed by adding a wait-for-state task to upstart. Something similar is needed for NFS mount types as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1012768/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
