linux-kernel - Re: Mounting NFS root FS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 04 Dec 2006 15:47:09 -0500
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Janne Karhunen <Janne.Karhunen@...il.com>, MrUmunhum@...dial.com,
	linux-kernel@...r.kernel.org
Subject: Re: Mounting NFS root FS

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/