From: Frank Steiner <fsteiner-mail1-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
To: nfs@lists.sourceforge.net
Subject: [NFS] locking failure with rpcbind and nfsroot (SLES 11, 2.6.27)
Date: Wed, 22 Jul 2009 15:57:50 +0200 [thread overview]
Message-ID: <4A671ADE.5060109@bio.ifi.lmu.de> (raw)
Hi,
the question in short: How can I boot a diskless client with nfsroot and
let it mount its /var directory via NFS, with locking enabled?
We did this with SLES 10 so far:
- boot the client and let it mount / read-only from the server
- start portmap on the client
- execute sth. like "mount -o rw,lock server:/<clientip>/var /var"
Then we had file locking in /var on the client, and on every NFS directory
we mounted on the client afterwards.
With SLES 11 (kernel 2.6.27) we switched from portmap to rpcbind and things fail,
because rpcbind creates a lock file and a socket in /var/run, so we need a
writeable /var before we can mount /var.
So we first create a tmpfs for /var, start rpcbind, then mount the clients
/var directory via NFS from the server over the tmpfs.
Then we try to restart rpcbind so that it can recreate the socket in /var/run,
but it fails. It doesn't create the socket file, and after about 60 seconds says:
rpcbind: server localhost not responding, timed out
lockd: cannot monitor our_server
lockd: failed to monitor our_server
So it seems we cannot mount a nfs directory on a tmpfs /var when this /var
is already used by rpcbind and its socket.
What can we do? Is /var as nfs directory with locking no longer possible
with nfsroot and rpcbind?
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
------------------------------------------------------------------------------
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next reply other threads:[~2009-07-22 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 13:57 Frank Steiner [this message]
[not found] ` <4A671ADE.5060109-G0GEQqhI7DhYiKXMg8wJIg@public.gmane.org>
2009-07-28 10:31 ` [NFS] locking failure with rpcbind and nfsroot (SLES 11, 2.6.27) Frank Steiner
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=4A671ADE.5060109@bio.ifi.lmu.de \
--to=fsteiner-mail1-g0geqqhi7dhyikxmg8wjig@public.gmane.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