On Wed, Oct 3, 2018 at 2:45 PM Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > > On Wed, 2018-10-03 at 14:31 -0400, Olga Kornievskaia wrote: > > Hi folks, > > > > Is it true that NFS mount option "timeo" has nothing to do with the > > socket's setting of the user-specified timeout TCP_USER_TIMEOUT. > > Instead, when creating a TCP socket NFS uses either default/hard > > coded > > value of 60s for v3 or for v4.x it's lease based. Is there no value > > is > > having an adjustable TCP timeout value? > > > > It is adjusted. Please see the calculation in > xs_tcp_set_socket_timeouts(). but it's not user configurable, is it? I don't see a way to modify v3's default 60s TCP timeout. and also in v4, the timeouts are set from xs_tcp_set_connect_timeout() for the lease period but again not user configurable, as far as i can tell. > > -- > Trond Myklebust > Linux NFS client maintainer, Hammerspace > trond.myklebust@xxxxxxxxxxxxxxx > >
