All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Janne Karhunen <Janne.Karhunen@gmail.com>,
	MrUmunhum@popdial.com, linux-kernel@vger.kernel.org
Subject: Re: Mounting NFS root FS
Date: Mon, 04 Dec 2006 16:20:51 -0800	[thread overview]
Message-ID: <4574BB63.4020800@zytor.com> (raw)
In-Reply-To: <1165267623.5698.33.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> On Mon, 2006-12-04 at 22:05 +0200, Janne Karhunen wrote:
>> On Monday 04 December 2006 20:21, Trond Myklebust wrote:
>>
>>>>> 2) NFS provides persistent storage.
>>>> To me this sounds like a chicken and an egg problem. It
>>>> both depends and provides this at the same time :/. But
>>>> hey, if it's supposed to work then OK.
>>> ??? Locking depends on persistent storage, but persistent storage never
>>> depended on locking.
>> Except for the fact that to be able to mount anything RW you
>> generally _want_ to have locks. And can't have locks without 
>> the mount. Not that it wouldn't work, it's just that I would
>> not do it [for obvious reasons].
> 
> You just need to be careful to set it up correctly in the initrd: either
> make sure that you mount the root partition as 'nolock' or else make
> sure that you mount /var/lib/nfs, and start rpc.statd before you start
> init and any other applications that might need locking.
> 

The nfsmount which is in the klibc distribution supports running an ad 
hoc portmap daemon, which allows locking to be done by forwarding 
information to the "real" portmap for when the real rpc.statd is run.

	-hpa

  reply	other threads:[~2006-12-05  0:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 19:03 Mounting NFS root FS William Estrada
2006-12-02 19:07 ` Jan Engelhardt
2006-12-02 21:15   ` Willy Tarreau
2006-12-02 21:56     ` Jan Engelhardt
2006-12-02 22:55       ` Willy Tarreau
2006-12-03  2:37         ` Trond Myklebust
2006-12-03  6:02           ` Willy Tarreau
2006-12-03  7:05             ` Trond Myklebust
2006-12-03  8:30               ` Willy Tarreau
2006-12-03 11:04                 ` Jan Engelhardt
2006-12-03 16:59                 ` Trond Myklebust
2006-12-04 11:51 ` Janne Karhunen
2006-12-04 15:29   ` Trond Myklebust
2006-12-04 17:12     ` Janne Karhunen
2006-12-04 18:21       ` Trond Myklebust
2006-12-04 20:05         ` Janne Karhunen
2006-12-04 21:27           ` Trond Myklebust
2006-12-05  0:20             ` H. Peter Anvin [this message]
2006-12-04 20:03       ` Jan Engelhardt
2006-12-04 20:27         ` Janne Karhunen
2006-12-04 20:47         ` Trond Myklebust
2006-12-05 18:43           ` Jan Engelhardt
2006-12-05 19:37             ` Trond Myklebust
2006-12-05 19:59               ` Jan Engelhardt
2006-12-05 20:12                 ` Trond Myklebust
2007-01-27 14:47                   ` Jan Engelhardt
2006-12-07 22:27   ` Hans-Peter Jansen

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=4574BB63.4020800@zytor.com \
    --to=hpa@zytor.com \
    --cc=Janne.Karhunen@gmail.com \
    --cc=MrUmunhum@popdial.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.