Comment 41 for bug 19196

just to straighten it out:

if my above patch fixes the "Mysterious NFS mount timeouts" the bug would be either in klibc's nfsmount or it's a package install problem. which version of the klibc package you are using, oliver?
the current version klibc-1.1.16-1ubuntu1 has the nolock option (NFS_MOUNT_NONLM=no NetworkLockManager) as default in usr/kinit/nfsmount/main.c:

static struct nfs_mount_data mount_data = {
        ...
        .flags = NFS_MOUNT_NONLM | NFS_MOUNT_VER3 | NFS_MOUNT_TCP,
        ...
}

in my dapper environment nfsmount is mounting the nfs-root with the option nolock set and works as expected.
what happens if you change back from busybox-mount to klibc's nfsmount with nolock option forced:

- mount -o nolock ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}
+ nfsmount -o nolock ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}

(you could set NFSOPTS="-o retrans=10,nolock" in "/etc/mkinitramfs/initramfs.conf" as well instead)

martin