Subject: Re: Mounting NFS root FS
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Janne Karhunen <Janne.Karhunen@gmail.com>
Cc: MrUmunhum@popdial.com, linux-kernel@vger.kernel.org
In-Reply-To: <200612041912.30527.Janne.Karhunen@gmail.com>
References: <4571CE06.4040800@popdial.com>
	 <24c1515f0612040351p6056101frc12db8eb86063213@mail.gmail.com>
	 <1165246177.711.179.camel@lade.trondhjem.org>
	 <200612041912.30527.Janne.Karhunen@gmail.com>
Content-Type: text/plain; charset=utf-8
Date: Mon, 04 Dec 2006 13:21:30 -0500
Message-Id: <1165256490.711.233.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1543
Lines: 40

On Mon, 2006-12-04 at 19:12 +0200, Janne Karhunen 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. Neither rpc.statd nor lockd, nor the nfs client
depend on locking working a priori.

> 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)?

1) Packet loss is dealt with by retrying ad-infinitum.

2) No. The problem of client crashes was fixed in NFSv4 with the
addition of lease-based locks.

> ¹ And why does insmod require a lock on module at load??

Does it? I've no idea why it should need that.

Trond

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