On testing this in a Natty VM, I was able to reproduce with this fstab:
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/vda1 during installation
UUID=9d2fb77a-7e3f-42f5-94ec-d8d37c46c56d / ext3 errors=remount-ro 0 1
# swap was on /dev/vda5 during installation
UUID=f35bf0c3-5263-4225-9a33-f8ffdf0fc0ce none swap sw 0 0
clint-MacBookPro:/home/clint /mnt/test/clint nfs defaults,rw,exec,user,nobootwait 0 0
/test.fs /mnt/test ext4 defaults,user_xattr,loop 0 2
The issue seems to be in the name resolution. If I replace 'clint-MacBookPro' (the name of my vm host) with an IP, or something in /etc/hosts, I get no waiting at the S or M prompt.
Marking Confirmed, setting importance to High since this interrupts remote server rebooting.
On testing this in a Natty VM, I was able to reproduce with this fstab:
proc /proc proc nodev,noexec,nosuid 0 0 7e3f-42f5- 94ec-d8d37c46c5 6d / ext3 errors=remount-ro 0 1 5263-4225- 9a33-f8ffdf0fc0 ce none swap sw 0 0 o:/home/ clint /mnt/test/clint nfs defaults, rw,exec, user,nobootwait 0 0 user_xattr, loop 0 2
# / was on /dev/vda1 during installation
UUID=9d2fb77a-
# swap was on /dev/vda5 during installation
UUID=f35bf0c3-
clint-MacBookPr
/test.fs /mnt/test ext4 defaults,
The issue seems to be in the name resolution. If I replace 'clint-MacBookPro' (the name of my vm host) with an IP, or something in /etc/hosts, I get no waiting at the S or M prompt.
Marking Confirmed, setting importance to High since this interrupts remote server rebooting.