Re: [PATCH] NFS: have string-based mount options default to intr mounts

Re: [PATCH] NFS: have string-based mount options default to intr mounts

[Rick Macklem]

> Chuck Lever <chuck.lever@oracle.com> wrote:
> 
> > I thought "nointr" was the default because it is safest.
> > 

I was actually impressed that "intr" mounts work for NFSv4. I would have
thought interrupting an RPC that has state related (Open, Lock,...) op(s)
in it would cause grief later. (NFSERR_BADSEQID or similar)

Do you spin off kernel threads to babysit those outstanding RPCs? rick

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: [NFS] [PATCH] NFS: have string-based mount options default to intr mounts

[Trond Myklebust]

On Wed, 2007-07-25 at 16:05 -0400, Rick Macklem wrote:
> > Chuck Lever <chuck.lever@oracle.com> wrote:
> > 
> > > I thought "nointr" was the default because it is safest.
> > > 
> 
> I was actually impressed that "intr" mounts work for NFSv4. I would have
> thought interrupting an RPC that has state related (Open, Lock,...) op(s)
> in it would cause grief later. (NFSERR_BADSEQID or similar)
> 
> Do you spin off kernel threads to babysit those outstanding RPCs? rick

Sort of. We run them as independent asynchronous RPC tasks. If the user
interrupts the request, then it is allowed to complete but once it does
then a new RPC call may be sent in order to undo the effects.

Cheers
  Trond