> none /var/www/dav/Public aufs
br:/mnt/local/archiv/Public_dav:/mnt/local/archiv/Public 0 0
Yes, the problem here is that the information about the preconditions
for mounting this filesystem entry are encoded in the options field
using a filesystem-specific syntax. mountall doesn't (and shouldn't)
know anything about this, so doesn't have enough information to mount
this at the correct time.
Does aufs support a value other than 'none' for the first field? even
if it ignored it, if this pointed to a file path we could then use the
same handling for aufs as for bind mounts. (Bind mounts are currently
*also* broken - bug #524972 - but then we could at least kill two birds
with one stone.)
As far as this breaking the boot and giving you no option to insert your
own local script: you can mark the filesystem 'noauto' in /etc/fstab,
and add an upstart job like this:
start on mounted MOUNTPOINT=/mnt/local/archiv
exec mount /var/www/dav/Public
(or whatever the correct value for MOUNTPOINT is on your system)
** Changed in: mountall (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: mountall (Ubuntu)
Status: New => Triaged
** Summary changed:
- mountall hangs when fstab contains aufs entries
+ mountall hangs when fstab contains aufs entries because device='none', paths
specified in options
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806884
Title:
mountall hangs when fstab contains aufs entries because device='none',
paths specified in options
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/806884/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
