Version: 1:1.3.4-2.1

nfs-common version 1:1.3.4-2.1
kernel linux-image-4.9.0-8-amd64                 4.9.130-2 

It takes a little longer than the advertised 60s.
It tries 10 times and gives up.

% /usr/bin/time -p sudo mount -vvvv -t nfs -o vers=3,retry=1 192.168.30.1:/blah 
/mnt
mount.nfs: timeout set for Sat Dec 15 21:04:10 2018
mount.nfs: trying text-based options 'vers=3,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
imount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: Connection timed out
Command exited with non-zero status 32
real 65.87
user 0.02
sys 0.04

Same for vers=2
% /usr/bin/time -p sudo mount -vvvv -t nfs -o vers=2,retry=1 192.168.30.1:/blah 
/mnt
mount.nfs: timeout set for Sat Dec 15 21:05:58 2018
mount.nfs: trying text-based options 'vers=2,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=2,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=2,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=2,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=2,retry=1,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: Connection timed out
Command exited with non-zero status 32
real 65.77
user 0.02
sys 0.04


Setting retry=2 does indeed double the time to timeout.

% /usr/bin/time -p sudo mount -vvvv -t nfs -o vers=3,retry=2 192.168.30.1:/blah 
/mnt
mount.nfs: timeout set for Sat Dec 15 21:09:13 2018
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: trying text-based options 'vers=3,retry=2,addr=192.168.30.1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: Connection timed out
Command exited with non-zero status 32
real 131.67
user 0.04
sys 0.05


NFSv4 behaves differently.

% /usr/bin/time -p sudo mount -vvvv -t nfs4 -o retry=1 192.168.30.1:/blah /mnt 
mount.nfs4: timeout set for Sat Dec 15 21:11:06 2018
mount.nfs4: trying text-based options 
'retry=1,vers=4.2,addr=192.168.30.1,clientaddr=192.168.1.12'
mount.nfs4: mount(2): Connection timed out
mount.nfs4: Connection timed out
Command exited with non-zero status 32
real 262.87
user 0.00
sys 0.00

Try retry=2 - times out at the same time.
The timeout is calculated correctly, but something makes it take longer

% date
Sat 15 Dec 21:29:02 AEDT 2018
% /usr/bin/time -p sudo mount -vvvv -t nfs4 -o retry=1 192.168.30.1:/blah /mnt
mount.nfs4: timeout set for Sat Dec 15 21:31:06 2018                 
mount.nfs4: trying text-based options 'retry=1,vers=4.2,addr=192.168.30.1,      
clientaddr=192.168.1.12'
mount.nfs4: mount(2): Connection timed out
mount.nfs4: Connection timed out
Command exited with non-zero status 32
real 269.12
user 0.00
sys 0.00


Despite the different v4 behaviour I think this bug can be closed.
At the time it was reported v3 would have been default and that
definitely works as advertised.

There is an issue with v4 but that should probably be a new bug.

Kind regards
Vince

Reply via email to