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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
