Aha! Good job that. Makes sense, too. Indeed, it must take some cleverness to figure out that the parent of the bind is a remote mount.
Scott James Remnant wrote: > I was able to reproduce this on lucid, and mountall 2.1 fixes this > problem > > It's caused by the bind mounts being considered "failed" because the NFS > server wasn't ready, and it hadn't correctly remote-tagged them because > they were device parents not mount parents. > -- upstart/mountall doesn't handle bind mounts reliably https://bugs.launchpad.net/bugs/459642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
