mountall doesn't know that glusterfs is a network filesystem type. This
means that at boot time, there's a race between bringing the network up
and trying to mount /home, and when mountall wins the race, the mount
fails and is never re-tried. The newer version of mountall is faster by
mounting in parallel, which increases the chance of hitting this race
and exposing this problem.
To work around this bug, you should be able to add the '_netdev' option
to the fstab entries, signal to mountall that the mount should be
retried when network interfaces are brought up. Can you please test
that this fixes the issue for you?
** Changed in: mountall (Ubuntu)
Importance: Undecided => Low
** Changed in: mountall (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103047
Title:
mountall causes automatic mounting of gluster shares to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1103047/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
