From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: NFS locking bug
Date: 01 Aug 2001 11:53:08 +0200 [thread overview]
Message-ID: <shs1ymw14zf.fsf@charged.uio.no> (raw)
In-Reply-To: <20010801040256.H9254@vestdata.no>
In-Reply-To: Ragnar Kjørstad's message of "Wed, 1 Aug 2001 04:02:56 +0200"
>>>>> " " == Ragnar Kjørstad <kernel@ragnark.vestdata.no> writes:
> This is what I do:
> * mount NFS filesystem on client1
> * mount NFS filesystem on client2
> * lock file on client1
> * verify that I can not lock the same file on client2
> * reboot the NFS-server
> * When I start statd on the nfs-server, I see the following
> in the logfiles for the clients:
> Jul 31 18:33:55 client rpc.statd[455]: recv_rply: [127.0.0.1]
> RPC status 3 Jul 31 18:33:55 client kernel: svc: unknown
> procedure (24) Jul 31 18:34:01 client kernel: svc: unknown
> procedure (24) Jul 31 18:34:01 client rpc.statd[455]:
> recv_rply: [127.0.0.1] RPC status 3 Jul 31 18:34:07 client
> kernel: svc: unknown procedure (24) Jul 31 18:34:07 client
> rpc.statd[455]: recv_rply: [127.0.0.1] RPC status 3 Jul 31
> 18:34:13 client kernel: svc: unknown procedure (24) Jul 31
> 18:34:13 client rpc.statd[455]: recv_rply: [127.0.0.1] RPC
> status 3 Jul 31 18:34:19 client rpc.statd[455]: Can't
> callback client (100021,1), giving up.
> * I can no lock the file on client2, even if the client1 still thinks
> the file is locked.
> Is this a bug?
The NLM lock reclaiming code in the stock 2.4.x kernel is
incomplete. Please apply the patch on
http://www.fys.uio.no/~trondmy/src/2.4.7/linux-2.4.7-reclaim.dif
Cheers,
Trond
prev parent reply other threads:[~2001-08-01 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 2:02 NFS locking bug Ragnar Kjørstad
2001-08-01 9:53 ` Trond Myklebust [this message]
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=shs1ymw14zf.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=kernel@ragnark.vestdata.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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