Date:   Tue, 18 Dec 2018 09:27:30 +1100
From:   Vincent McIntyre <vincent.mcintyre@csiro.au>
To:     Chuck Lever <chuck.lever@oracle.com>
CC:     Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: mount option timeo - in deciseconds, or seconds?
Message-ID: <20181217222730.fysi2krs7siblihi@mayhem.atnf.CSIRO.AU>
References: <20181215025034.j5zyfytvxqt35woz@mayhem.atnf.CSIRO.AU>
 <8EE078EE-CE10-4316-B447-F005B2034D69@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8EE078EE-CE10-4316-B447-F005B2034D69@oracle.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Mon, Dec 17, 2018 at 10:11:34AM -0500, Chuck Lever wrote:
> Hi Vincent-
> 
> 
> > On Dec 14, 2018, at 9:50 PM, Vincent McIntyre <vincent.mcintyre@csiro.au> wrote:
> > 
> > Hi,
> > 
> > I've been trying to figure out why the nfs.man manpage states
> > 
> >  .BI timeo= n
> >  The time in deciseconds (tenths of a second) the NFS client waits for a
> >  response before it retries an NFS request.
> > 
> > Can someone who actually understands NFS enlighten me?
> > Here's where I'm up to.
> > 
> > I looked in the upstream git.
> > The 'deciseconds' has been in there since the start of git history
> > (2007, commit id 16db99b56a532bf56fa27618a6ef30763cd9006f).
> > But is it (still) correct?
> > 
> > Unfortunately I can't see a direct use of the 'timeo' field
> > of the NFS data structure so the answer is not easily found.
> 
> The "timeo" mount option is not used by the mount.nfs command.
> It is passed to the kernel, which treats it just as the man
> page says.

Thanks Chuck.
I did eventually figure this out but forgot to follow up here.

> The code you excerpt below implements the "retry" mount option.
> 

doh. Thanks for pointing that out.

Kind regards
Vince