The "remote 0/0" speaks of issues and I see later changes in mountall.c that could address reliability of startups.
"415 Even if the mounting/mounted event failed (due perhaps to a failure of a job depending on it), we still want to proceed with the mount and not just error out." "411 Make sure we reset the pending_call to NULL when handling the event, so that we correctly rehandle after a failed mount attempt." http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/raring/mountall/raring/changes I neglected to save output of mountall --verbose and I neglected to try connecting to the system over ssh in lucid where I saw no further upstart activity on the console after about 3 failed NFS mount attempts. ** Changed in: mountall (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836533 Title: Still problems with nfs-mounts in /etc/fstab on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/836533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
