Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Mar 1999 10:19:12 -0500 (EST)
From:      Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        Matthew Dillon <dillon@apollo.backplane.com>, Pierre Beyssac <beyssac@enst.fr>, freebsd-current@FreeBSD.ORG
Subject:   Re: panic: vfs_busy: unexpected lock failure 
Message-ID:  <199903181519.KAA12752@khavrinen.lcs.mit.edu>
In-Reply-To: <199903181449.WAA33699@spinner.netplex.com.au>
References:  <199903180111.RAA34092@apollo.backplane.com> <199903181449.WAA33699@spinner.netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 18 Mar 1999 22:49:10 +0800, Peter Wemm <peter@netplex.com.au> said:

> AMD is easy to upset, and that's bad because it's holding a mountpoint in /
> (ie: /host) which often gets hit by every single getcwd() call when it 
> gets a lstat("/host"...) or whatever.  I think this is the single largest 
> source of load on the amd process.

> IMHO, /host needs to move down a level to get it out of the way of 
> getcwd().  NFS mounts should probably move away from / as well, as they 
> cause traffic on each getcwd().

`/host' is non-standard.  The Standard Configuration is `/net' is the
directory simulated by amd and `/a/${hostname}/root' is where amd
mounts the directory tree.  This is done specifically to avoid getcwd
wedgitude.  The example we ship would sorely puzzle anyone who is
experienced running a Standard Configuration amd.

My machine has, throughout its entire history, had `/home' simulated
by amd.  I have literally *never* had amd hose my configuration (and I
would know it fast since both mail and Web service would break).

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903181519.KAA12752>