Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Nov 1999 09:44:56 -0800 (PST)
From:      Jamie Bowden <ragnar@sysabend.org>
To:        "Ronald G. Minnich" <rminnich@lanl.gov>
Cc:        "David E. Cross" <crossd@cs.rpi.edu>, freebsd-hackers@FreeBSD.ORG
Subject:   Re: wacky rpc.lockd idea...
Message-ID:  <Pine.BSF.4.10.9911230942250.37564-100000@moo.sysabend.org>
In-Reply-To: <Pine.LNX.4.20.9911230840400.4538-100000@mini.acl.lanl.gov>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Nov 1999, Ronald G. Minnich wrote:

:On Mon, 22 Nov 1999, David E. Cross wrote:
:> I've noticed about 99% of the panics on our machines are the result of NFS, 
:> more often than not it is the result of a backing store file being blown
:> away underneath the client.  ie.  person editing a file on one machine, 
:> compiling and running on a second, then removing the binary on the first
:> machine.  If we had a working lock manager could we not have the kernel open
:> a shared lock on anything it had in backing store, would that not assure that
:> files didn't go poof in the night?
:
:I think you're really proposing to add state to NFS, but add it via a
:'back door', the lockd. I think this is not as good an idea as getting
:coda or intermezzo working -- for the latter, www.inter-mezzo.org
:
:nfs is just plain broken for this sort of thing, and has been forever. I'm
:not sure you want to start grafting on fixes of this sort.

How would this be different that what Sun has done?  They designed NFS
stateless (do to stupid utopian visions of 0 latency infinite bandwidth
networks), and then added state via rpc.lockd to try and fix their silly
design flaw.  Sure, locking still has problems due to race conditions and
deadlocks, but it beats what you have without it.

Jamie Bowden

-- 

If we've got to fight over grep, sign me up.  But boggle can go.
	-Ted Faber (on Hasbro's request for removal of /usr/games/boggle)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911230942250.37564-100000>