Yes, I am aware that nobootwait is a different issue. My point is about bad boot ordering, where nfs is tried before up'ing the network interfaces.
Note that it's just a plain wired dhcp setup without any auth, so it should just work. Regards, Alex On Apr 8, 2011 12:46 AM, "Clint Byrum" <cl...@fewbar.com> wrote: > bwalex: Are you saying that the boot is actually waiting for these > mounts to timeout with nobootwait? That would be a pretty serious > problem, and not related to this bug. > > The error message is a result of the fact that mountall just tries to > mount *all* filesystems in fstab, similarly to 'mount -a'. If one fails > its just noted and will be tried again. > > The error message from mount.nfs is a bit misleading, as its saying DNS > failed but its really that contacting the host failed. > > dblade, net-device-up is emitted every time a network device is > configured properly. This means either it was static and configured by > ifupdown, or its dynamic and dhclient configured it. So, the theory here > is that every time we get a new network device, we should try again in > case all filesystems haven't been mounted yet. > > start on started networking only means that all static devices have been > configured, and all dhclients have been started. Any NetworkManager > based connections will be missed entirely. > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/586022 > > Title: > nfs mounts happen before network is up > > Status in NULL Project: > Invalid > Status in “upstart” package in Ubuntu: > Incomplete > > Bug description: > Binary package hint: upstart > > My server tries to make three NFS mounts, as specified in /etc/fstab. > I use a host name in the fstab entry and that host name is in my > /etc/hosts. However on boot, I get these error messages: > > > mount.nfs: DNS resolution failed for nfshost: Name or service not known > mountall: mount /home/foo/Maildir [622] terminated with status 32 > > After the boot completes though, the mounts are working. The > /etc/fstab entry looks like this: > > nfshost:/c/backup/foomail /home/foo/Maildir nfs > defaults,hard,intr,nolock 0 0 > > Changing 'nfshost' to the IP address does not help. I'm guessing its > an upstart boot order problem where the mounts are attempted before > networking is up. Then, once networking comes up, the mount is > retried and succeeds. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/null/+bug/586022/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/586022 Title: nfs mounts happen before network is up -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
