On Fri, Apr 25, 2008 at 12:20:19PM -0400, Chuck Lever wrote: >> It seems retry= is now additive with the text-based mount interface. In >> particular, "mount -o retry=0" still gives a two-minute timeout. Is this >> intentional? > No, it's broken. Can you test the attached patch? It seems it creates rather odd behavior: fugl:~# mount -t nfs -v -o retry=0 10.0.0.11:/foo /mnt mount.nfs: timeout set for Thu Jan 1 14:40:25 1970 mount.nfs: text-based options: 'retry=0,addr=10.0.0.11' fugl:~# mount -t nfs -v -o retry=0 10.0.0.11:/foo /mnt mount.nfs: timeout set for Sat Jan 10 17:07:36 1970 mount.nfs: text-based options: 'retry=0,addr=10.0.0.11' /* Steinar */ -- Homepage: http://www.sesse.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
