From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net
Subject: Re: lockd recovery not working on RH with 2.6 kernel
Date: Fri, 19 Nov 2004 12:50:10 -0500 [thread overview]
Message-ID: <419E3252.3040602@RedHat.com> (raw)
In-Reply-To: <1100882099.11209.8.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>to den 18.11.2004 Klokka 11:52 (-0500) skreiv Steve Dickson:
>
>
>>Well it appears things are a bit broken. Here is a client side patch that
>>enables the client to reclaim locks on a rebooted server.
>>
>>The two main issues were nlm4svc_decode_reboot() not setting
>>the protocol which cause the nlm_host structure not to be found
>>and two, making nlmclnt_reclaim() retry when the portmapper was up
>>but lockd had not made it yet.... I also fixed a debugging
>>statement and well as added a couple... that I found useful....
>>
>>
>
>Yep. Good work!
>
>
cool... can I assuming the patch will be headed to one of the upstream
kernels soon?
>>Unfortunately this reclaim code freaks out the linux server, causing it
>>to send two back-to-back messages (both using the same xid) that
>>fails and then grant the lock.... It seems the dentry_open() call
>>(in nfsd_open()) is returning 30000 error value. Its not clear why or
>>what a 30000 value means.... I'm still looking in to that, but this code
>>was tested with both a Neapps filer and Solaris 10 server which seem
>>to work fine..
>>
>>
>
>30000 ???? All kernel errors should be < 1000. Is this the perhaps the
>bug with the unintialized variable in the mountd upcall code? I believe
>the attached patch has already been committed to the nfs-utils CVS tree.
>
>
Well after further review.... dentry_open() is not the one failing with
an error
code of 30000, its fh_verify() that's failing with 30000 which means
nfserr_dropit.
Basically what this means is exp_find() is returning EAGAIN because the
there
is an upcall is already in process (or the cache is not yet fully
primed)....
Unfortunately the NLM protocol does not support a EAGAIN notion and the way
the NLM rpc routines are setup, is does not seem possible to simply
svc_drop
NLM messages....
So I've pinged Neil on how he would like to hand this....
SteveD.
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-11-19 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 19:12 lockd recovery not working on RH with 2.6 kernel Marc Eshel
2004-11-17 19:58 ` Steve Dickson
2004-11-18 16:52 ` Steve Dickson
2004-11-19 16:34 ` Trond Myklebust
2004-11-19 17:50 ` Steve Dickson [this message]
2004-11-19 20:24 ` Trond Myklebust
2004-11-19 20:27 ` Trond Myklebust
2004-11-19 21:40 ` Steve Dickson
2004-11-19 20:38 ` Steve Dickson
2004-11-23 0:45 ` unlock during lockd recovery Marc Eshel
2004-11-23 8:10 ` Olaf Kirch
2004-11-23 17:44 ` Marc Eshel
2004-11-24 8:59 ` Olaf Kirch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=419E3252.3040602@RedHat.com \
--to=steved@redhat.com \
--cc=NFS@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox