mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
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 15:47:09 -0500	[thread overview]
Message-ID: <1165265229.5698.21.camel@lade.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0612042100570.29300@yvahk01.tjqt.qr>

On Mon, 2006-12-04 at 21:03 +0100, Jan Engelhardt 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.
> 
> Way 1:
> 
> mount -nt tmpfs none /var/lib/nfs;
> mount -nt nfs fserve:/tftpboot/linux /mnt;
> mount -n --move /var/lib/nfs /mnt/var/lib/nfs/;

Nope. As Janne implied, the /var/lib/nfs partition _must_ be persistent,
since it is used to store information about the servers on which the
client holds locks and therefore needs to notify in case it reboots.
Using tmpfs defeats the whole purpose of having an rpc.statd in the
first place.

> ./run_init -c /mnt /sbin/init; # or similar
> 
> And you can also start locking after pivot_rooting to /mnt, that would 
> not even require (/mnt)/var/lib/nfs to be a separate mount.

Much better idea. You can delay starting rpc.statd until you have set up
your filesystem provided that you are not running any programs that
require NLM locking. If you do need to run such a program before you
start rpc.statd, then you will have to use the '-onolock' mount option.

Cheers,
  Trond


  parent reply	other threads:[~2006-12-04 20:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 19:03 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
2006-12-04 20:03       ` Jan Engelhardt
2006-12-04 20:27         ` Janne Karhunen
2006-12-04 20:47         ` Trond Myklebust [this message]
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=1165265229.5698.21.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=Janne.Karhunen@gmail.com \
    --cc=MrUmunhum@popdial.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    /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®