[Bug 501678] Re: karmic indefinitely waits for nfs4-mount
I had the same phenomena. I followed Hark's instruction then it booted well. Option nobootwait is invalid, not solve the issue. Besides, I tested like this. I let it mount from non-existing server, means invalid mount point, then mount.nfs4 report that "No such device" then halted forever. I dont know whether it is behaviour of nfs4 or Ubuntu 10.04. On CentOS, even invalid nfs mount point, booting process is well, then I can ssh to it to modify the entry in fstab. I think this behavior of NFS on CentOS is good. This helps admin avoid going to datacenter from home, just remove nfs entry in fstab. I dont know whether it is a bug or not, but the behavior is not acceptable. Hope that Ubuntu developers consider this. -- karmic indefinitely waits for nfs4-mount https://bugs.launchpad.net/bugs/501678 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501678] Re: karmic indefinitely waits for nfs4-mount
Why is this bug marked as invalid? I also have this bug in Lucid. Servers with nfs4 mounts in fstab hang forever while booting, unless I put 'nfs' in /etc/modules. I think this is an important bug! -- karmic indefinitely waits for nfs4-mount https://bugs.launchpad.net/bugs/501678 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501678] Re: karmic indefinitely waits for nfs4-mount
If you do not want it to wait for /home, add "nobootwait" to the options for that mountpoint in fstab ** Changed in: mountall (Ubuntu) Status: New => Invalid -- karmic indefinitely waits for nfs4-mount https://bugs.launchpad.net/bugs/501678 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501678] Re: karmic indefinitely waits for nfs4-mount
Hi Mr. Remnant Setting fstab to "nobootwait" is not a solution. /home has to be there before any user gets a login If there is no home directory for the user and gdm and login will fail. And my users complain heavily and start to press the reset button or c-a-del every time they get "waiting for /home". Can you give me a hint on how to modify upstart and mountall to check for the nfs server before trying to mount the volume? Or is it possible to add an upstart job just before login and gdm to check for the volume and maybe try to mount again? I'm willing to do some hacking if you can flatten my learning curve a bit ... -- karmic indefinitely waits for nfs4-mount https://bugs.launchpad.net/bugs/501678 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501678] Re: karmic indefinitely waits for nfs4-mount
Update for whoever gets here: I triet with "bobootwait" but it failed like I anticipated it. After some digging and source-reading I found out the following: mountall tries to mount the network volume and if it does not work, it will wait for the device by waiting for a SIGUSR. upstart sends SIGUSER as soon as the network device is availible. But this is too early. network-manager and dhcp have not completed to set up a working connection so the network mount will fail again. mountall will wait for SIGUSR again but nobody will send it until you remove and reinstall the plug to trigger upstart. So I added a "sleep 5s" in mountall-net and the problem was hacked away for me. -- karmic indefinitely waits for nfs4-mount https://bugs.launchpad.net/bugs/501678 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
