On Wed, 2006-07-12 at 11:03 +0800, Ian Kent wrote: > On Tue, 2006-07-11 at 19:27 -0400, Trond Myklebust wrote: > > Something like > > > > mount -t nfs -ohard,timeo=600,retrans=2,rsize=32768,wsize=32768,tcp foo:/ > > /bar > > I thought that the default timeo had changed to 600 (60 secs) for TCP > mounts in later versions of mount (it should be) and that the retrans > shouldn't matter as 60 secs is the RPC major timeout. I thought the > point of this default was to prevent RPC from retransmitting as the TCP > la > > should be a fairly safe bet. You might want to add the 'intr' flag too, > > depending on how you feel about the behaviour w.r.t. pressing ^C. > > > > > * What is the reference standard behavior? > > I don't think it's a standard in as much as it's common sense. > Certainly if the defaults are set to those that are sensible for UDP you > are much more likely to bogus failures. > > Ian > yer would take care of it. > > Trond what am I missing.
The fact that not everyone may be using a recent version of mount :-) The above line should work fine with all versions. Actually, the "retrans" value is pretty irrelevant for hard mounts. It is more important for soft mounts for which it defines the number of resends before giving up the RPC call and returning an error to the application. Cheers, Trond _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
