From: Janne Karhunen <Janne.Karhunen@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: MrUmunhum@popdial.com, linux-kernel@vger.kernel.org
Subject: Re: Mounting NFS root FS
Date: Mon, 4 Dec 2006 19:12:29 +0200 [thread overview]
Message-ID: <200612041912.30527.Janne.Karhunen@gmail.com> (raw)
In-Reply-To: <1165246177.711.179.camel@lade.trondhjem.org>
On Monday 04 December 2006 17:29, Trond Myklebust wrote:
> > > I have been trying to make FC5's kernel do a boot
> > > with an NFS root file system. I see the support is in the
> > > kernel(?).
> >
> > Is this really properly possible (with read/write access and
> > locking in place)? AFAIK NFS client lock state data seems
> > to require persistent storage .. ?
>
> 1) Yes, but not on the root partition (unless you use an initrd to start
> rpc.statd before mounting the NFS partition).
Ok.
> 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.
Anyhoo, I tried this at some stage and failed as random
clients seemed to occasionally get stuck in insmod¹ at
boot (infinite wait on lock that never gets released).
At that stage guess was that server could not properly
recognize client reboot given stale client lock data.
But if it's supposed to work I guess I have to give it
another shot and do better analysis on it.
What about NLM/NSM protocol issues - do they properly
deal with packet loss and clients that stay down (client
holding a lock crashing and staying down; will the lock
ever be released)?
¹ And why does insmod require a lock on module at load??
--
// Janne
next prev parent reply other threads:[~2006-12-04 17:12 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 [this message]
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
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=200612041912.30527.Janne.Karhunen@gmail.com \
--to=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 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®