Re: Regression: NFS locking hangs when statd not running.

[Olaf Kirch <okir@suse.de>]

On Fri, Oct 20, 2006 at 08:23:13PM +1000, Neil Brown wrote:
>  The problem is that there is a case where we don't want the retry.
> 
>  In 2.6.18, if statd isn't running, then a lock attempt returns ENOLCK
>  immediately, which I think is good.
>  In 2.6.19-rc, in the same situation, a lock attempt waits for a major
>  timeout (30 seconds for TCP mounts) and is not interruptible for this
>  whole time (even with '-o intr' mounts).
> 
>  So: what to do?  Should we retry requests when portmap says "no such
>  service".

When lockd tries to do an upcall to statd? Definitely no, I'd say.
Essentially, statd upcalls should be a one-shot affair with minimal
timeout.

>  I think that for requests to a remote service - lockd or nfsd - we do
>  want to retry.  The server might be rebooting and so "no such
>  service" should be treated much like "no reply".

I believe this should depend on the semantics of the parent mount.
Basically, we should copy intr,hard from the NFS mount to the lockd
client we use, and from there to the portmap client. Otherwise
in a HA setup where you have hard mounts, you will suddenly start
seeing IO errors during failover.

The patch looks good, except maybe I'd use a different name, like
RPC_CLNT_BIND_NORETRY or some such.

Olaf
-- 
Olaf Kirch   |  --- o --- Nous sommes du soleil we love when we play
okir@suse.de |    / | \   sol.dhoop.naytheet.ah kin.ir.samse.qurax

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs