This bug might actually be related to nfs-common, but I'm not sure yet.
I'm debugging the situation right now.
A workaround that might be working is setting the MOUNT_WAIT variable in /etc/default/autofs
nfs debugging didn't give me anything usefel yet, I will see what I can pick up with wireshark.
After the failed mount in the syslog, the "mount.nfs" process sits there with ~16%CPU.
This bug might actually be related to nfs-common, but I'm not sure yet.
I'm debugging the situation right now.
A workaround that might be working is setting the MOUNT_WAIT variable in /etc/default/autofs
nfs debugging didn't give me anything usefel yet, I will see what I can pick up with wireshark.
After the failed mount in the syslog, the "mount.nfs" process sits there with ~16%CPU.