Comment 4 for bug 1205075

On Thu, Sep 26, 2013 at 06:35:14PM -0000, Paul Boven wrote:
> Running into the same issue here, I can't get glusterfs to mount at
> boot.

> System: Ubuntu 13.04

> Output from mountall --verbose:

> mount /export/brick0 [2508] exited normally
> Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
> or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
> Try `glusterfs --help' or `glusterfs --usage' for more information.
> mount /gluster [2509] exited normally

> The 'exited normally' seems wrong, too.

These are all bugs in the glusterfs mount helper, not in mountall. It does
not implement the expected interfaces required for mount.$fstype helpers.

> Output from mountall --verbose --debug:
> run_mount: mtab /gluster
> spawn: mount -f -t fuse.glusterfs -o defaults localhost:/gv0 /gluster
> spawn: mount /gluster [2599]
> Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
> or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
> Try `glusterfs --help' or `glusterfs --usage' for more information.
> mount /gluster [2599] exited normally

> My fstab entry:
> localhost:/gv0 /gluster glusterfs defaults,nobootwait 0 0

> It seems that mountall tries to emit "mount -f -t fuse.glusterfs", which fails.

No, that command almost certainly succeeds, because all it's doing is
updating the /etc/mtab to match the list of filesystems that are already
mounted. Something else has mounted /gluster for you, according to
/proc/mounts, and mountall is making sure /etc/mtab is kept up to date.

The failing call is the *second* one, where again, mountall is trying to
mount /gluster according to the fstab.

You can reproduce this failure by running the following from the
commandline:

  mount -t glusterfs -o defaults localhost:/gv0 /gluster