From: Mi Jinlong <mijinlong@cn.fujitsu.com>
To: "Trond.Myklebust" <trond.myklebust@fys.uio.no>,
"J. Bruce Fields" <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>,
NFSv3 list <linux-nfs@vger.kernel.org>
Subject: [RFC] After nfs restart, locks can't be recovered which record by lockd before
Date: Wed, 13 Jan 2010 17:51:25 +0800 [thread overview]
Message-ID: <4B4D979D.6090307@cn.fujitsu.com> (raw)
Hi,
When testing the nfs's lock at NFSv3, I get a problem.
So I want someone help me, thanks!
Test Process:
Step1, ClientA get an exclusive lock success.
Step2, Using command "service nfs restart" to restart server's nfs se=
rvice.
Step3. ClientB get lock should fail, but success.
I think after step2 (nfs service restart), clientA's lock should be rec=
overed.
But like above, clientA's lock doesn=E2=80=99t be recovered.
When tracing the kernel, I find nfsd will cause lockd stop when it stop=
=2E
When lockd stop, all locks will be release which is record before at lo=
ckd.
When nfsd start, the lockd will start also, but the statd don't know wh=
at happened
at kernel, so after that, locks will be lost.
Is it right when nfs stop, the lockd will stop too?=20
If it's right, should locks be recovered after lockd start?
thanks,
Mi Jinlong
next reply other threads:[~2010-01-13 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:51 Mi Jinlong [this message]
2010-01-13 12:51 ` [RFC] After nfs restart, locks can't be recovered which record by lockd before Jeff Layton
[not found] ` <20100113075155.5c409567-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2010-01-13 18:53 ` Chuck Lever
2010-01-14 10:06 ` Mi Jinlong
2010-01-14 16:13 ` Chuck Lever
2010-01-15 9:35 ` Mi Jinlong
2010-01-15 16:12 ` Chuck Lever
2010-01-18 10:51 ` Mi Jinlong
2010-01-18 16:17 ` Chuck Lever
2010-01-19 10:36 ` Mi Jinlong
2010-01-14 9:41 ` Mi Jinlong
2010-01-14 12:10 ` Jeff Layton
[not found] ` <20100114071036.09583f4a-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-01-15 9:28 ` Mi Jinlong
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=4B4D979D.6090307@cn.fujitsu.com \
--to=mijinlong@cn.fujitsu.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--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