Yes, it is SLES10 SP3 and I'm a customer. I'm not sure that Novell can help me, I expect the same proposal from them - "just make sure that /var/lib/nfs is available on startup". I'm not satisfied with this because I have some kind of high availability system built with two Linux hosts. Hosts share DRBD partition and one acting as primary exports, for instance /some/path. As soon as primary host fails, another one becomes primary and exports /some/path. There are more hosts on the network, they mount: server:/some/path where "server" is resolved to the IP of current primary host which currently exports path. So, in order to keep and overtake data about clients, /var/lib/nfs is replaced with link and points to /some/path/var/lib/nfs. If You don't familiar with DRBD then the most important thing You should know is that it is available for R/W on primary host only. So, on primary host DRBD is R/W, /var/lib/nfs is available and kstatd starts. On another host DRBD is NOT R/W, /var/lib/nfs is empry and kstatd doesn't start. This is why I'm looking for how do I re-init it at any time. I was looking for guidelines of using NFS in clusters but didn't found anything useful. Best regards Vladimir Vlasov -----Original Message----- From: NeilBrown [mailto:neilb@xxxxxxx] Sent: Thursday, January 26, 2012 3:41 PM To: Vlasov, Vladimir Cc: linux-nfs@xxxxxxxxxxxxxxx Subject: Re: Re-init lockd and kstatd in runtime. On Thu, 26 Jan 2012 11:15:02 +0000 "Vlasov, Vladimir" <vvlasov@xxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
