Hi, I've been able to reproduce this bug. It doesn't happen when using nfs4, it does with nfsvers=2 or nfsvers=3.
I can reproduce it with: ii linux-image-3.2.0-2-amd64 3.2.15-1 ii libmount1 2.20.1-4 ii mount 2.20.1-4 ii nfs-common 1:1.2.5-4 and it's still reproducible with linux-image 3.3.2-1~experimental.1 and also with previous version of mount (2.20.1-1.2) and nfs-commont (1:1.2.5-3) Another information, i'm booting from nfs, for the purpose of this bug report I've booted with init=/bin/sh $ cat /proc/cmdline console=hvc0 ip=10.20.30.14:10.20.30.241::255.255.255.0:log-01:eth0:off nfsroot=10.20.30.241:/vol/nfsroot/log-01 boot=nfs root=/dev/nfs rw init=/bin/sh $ grep nfsroot /proc/mounts 10.20.30.241:/vol/nfsroot/log-01/ / nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,proto=tcp,port=65535,timeo=7,retrans=10,sec=sys,local_lock=all,addr=10.20.30.241 0 0 -- Laurent -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vckqcdvl....@ezri.u-picardie.fr
