From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Reis <kiko@async.com.br>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, NFS@lists.sourceforge.net
Subject: Re: [NFS] Re: NFS client locking hangs for period
Date: 26 Jan 2003 22:49:14 +0100 [thread overview]
Message-ID: <shs8yx7lgyt.fsf@charged.uio.no> (raw)
In-Reply-To: <20030126140200.A25438@blackjesus.async.com.br>
>>>>> " " == Christian Reis <kiko@async.com.br> writes:
> I wonder why you can't do locking on NFS root (if it's a
> current limitation of if it doesn't make sense).
locking supposes that you are already running a statd daemon, which
you clearly cannot be doing on an nfsroot system. If you need locking
on a root partition, then you'll need to set up an initrd from which
to start all the necessary daemons...
BTW: Did I understand you and Neil correctly when you appeared to say
that you were sharing the *same* root partition between several
clients?
If so, then that could easily explain your problem: a directory like
/var/lib/nfs simply cannot be shared among several different
machines. Read the 'statd' manpage, and I'm sure you will understand
why.
Cheers,
Trond
next prev parent reply other threads:[~2003-01-26 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 20:49 Christian Reis
2003-01-25 3:54 ` Neil Brown
2003-01-26 16:02 ` Christian Reis
2003-01-26 21:49 ` Trond Myklebust [this message]
2003-01-26 22:47 ` [NFS] " Christian Reis
2003-01-26 23:02 ` Trond Myklebust
2003-01-26 23:56 ` Christian Reis
2003-01-27 0:06 ` Trond Myklebust
2003-01-27 2:19 ` Dell Latitude CPi keyboard problems since 2.5.42 Tom Sightler
2003-01-28 8:14 ` [NFS] Re: NFS client locking hangs for period Denis Vlasenko
2003-01-28 16:47 ` Christian Reis
2003-01-28 8:00 ` Denis Vlasenko
2003-01-28 16:44 ` Christian Reis
2003-01-29 21:53 ` Daniel Egger
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=shs8yx7lgyt.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®