On Fri, Aug 07, 2009 at 09:42:18AM +0300, Benny Halevy wrote: > On Aug. 07, 2009, 3:18 +0300, Carlos André <candrecn@xxxxxxxxx> wrote: > > Anyone ? > > > > 2009/7/29 Carlos André <candrecn@xxxxxxxxx>: > >> PPL, I need put a CentOS 5.3 (updated) NFSv4 server to work with Kerberos > >> and AutoFS, but i got a problem: If NFS server goes down i get a LOOOOOOONG > >> mount timeout on CentOS 5.3 (updated) NFSv4 client... > >> > >> Since i need mount some (3 to 6) dirs at user logon process, if mount hangs, > >> user logon hangs. Then i want configure it to timeout (if server down) after > >> 10-15 secs (MAX) on each mount attempt. > >> > >> I already make a lab and tried a LOT of combinations, there my findings > >> (server DOWN IP: 172.16.0.10 / client IP: 172.16.1.10) using basic command > >> (time mount 172.16.0.10:/remotedir /localdir/ -t nfs4 -o > >> sec=krb5,proto=<tcp/udp>) from NFS client: > >> > >> - Once i try access mount point using AutoFS (proto=tcp OR proto=udp) it > >> hangs for 189 secs (3m9s: real 3m9.001s) until show error (mount: mount to > >> NFS server '172.16.0.10' failed: timed out (giving up)) > > Sounds like you're hitting the server's grace period. I thought he was describing a situation where the server the server is completely gone and isn't coming back, and wondering how to make the mount fail faster. But I may be misunderstanding. --b. -- 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
