Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rice!sun-spots-request
From: del@thrush.mlb.semi.harris.com (Don Lewis)
Newsgroups: comp.sys.sun
Subject: Re: Has anyone tried the quota system?
Keywords: Miscellaneous
Message-ID: <9871@brazos.Rice.edu>
Date: 12 Jul 90 01:27:15 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 34
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n227, Replies: v9n230 v9n236 v9n244
X-Sun-Spots-Digest: Volume 9, Issue 253, message 17

In article <9538@brazos.Rice.edu> pcg@compsci.aberystwyth.ac.uk (Piercarlo Grandi) writes:
|Having too many mount points is really an exaggeration. I think that one
|mount point per server is all that is needed. Each server should have a
|directory with its name under which it mounts all filesystems that it must
|export. The resulting tree is like:
|
|		/server1/fs0/...
|		/server1/fs1/...
|		/server2/fsA/...
|		/server3/fsX/...
|		/server3/fsY/...
|		/server3/fsZ/...
|
|Where if you are on server1 you just mount your devices onto fs0 and fs1,
|whereas you NFS mount the entire /server2 and /server3 from the other
|servers.

Nope, sorry, this won't work, at least not on most machines (i.e. Suns).
Nfs mounts on the clients don't follow mounts on the server.  In your
example, on server1, the directories /server3/{fsX,fsY,fsZ} would all be
empty.  I do remember seeing a SunOS source patch at one time that makes
NFS server behave the way you describe.

|This organization reduces dramatically the number of mounted filesystems,
|which is *good* for many reasons (and helps prevent getcwd() lockups on
|pre-4.1 systems,

Not true in this case.  If /server2 and /server3 are mount points, then it
is real easy for something to hang because of stat()'ing these directories
when one of these servers is down.

Don "Truck" Lewis                      Harris Semiconductor
Internet:  del@mlb.semi.harris.com     PO Box 883   MS 62A-028
Phone:     (407) 729-5205              Melbourne, FL  32901