From: NeilBrown <neilb@suse.de>
To: "Vlasov, Vladimir" <vvlasov@mera.ru>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Re-init lockd and kstatd in runtime.
Date: Thu, 26 Jan 2012 22:40:42 +1100 [thread overview]
Message-ID: <20120126224042.63cdd70e@notabene.brown> (raw)
In-Reply-To: <06EFEBD57610DE4FBCA0449DDF4E102B08765D@tecas.te.mera.ru>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Thu, 26 Jan 2012 11:15:02 +0000 "Vlasov, Vladimir" <vvlasov@mera.ru> wrote:
> Hi.
>
> I'm wondering if there is any way to re-init lockd and kstatd after startup?
>
> Look, in svc.c static variable nsm_use_kstatd is set to 1.
> Then, if nsm_kernel_statd_init() returns error, nsm_use_kstatd is set to 0.
> And we end up without kstatd.
>
> Lockd will exit as soon as last NFS mount is unmounted and on next mount attempt lockd() in svc.c will be called again, but nsm_use_kstatd is 0 already and kstatd init will be skipped.
>
> So, looks like if /var/lib/nfs/state is missed on host startup, there is no way to recover and tell kernel init kstatd later on demand. Or?
This would be SLES10 - correct?
I suggest you simply make sure /var/lib/nfs/state is not missing at startup.
The issue sounds vaguely familiar ... maybe it is fixed in SLES10-SP4...
What release are you running? Are you a SLES customer? If you are, you
would be better off logging a support request on the SUSE bugzilla
(bugzilla.novell.com).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-01-26 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 11:15 Re-init lockd and kstatd in runtime Vlasov, Vladimir
2012-01-26 11:40 ` NeilBrown [this message]
2012-01-26 12:14 ` Vlasov, Vladimir
2012-01-27 8:31 ` Vlasov, Vladimir
2012-02-02 4:50 ` Vlasov, Vladimir
2012-02-02 4:58 ` NeilBrown
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=20120126224042.63cdd70e@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=vvlasov@mera.ru \
/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;
as well as URLs for NNTP newsgroup(s).