On Mon, Feb 05, 2007 at 05:06:25PM +0100, Chuck Silvers wrote:
> On Mon, Feb 05, 2007 at 09:39:23AM +0100, Kurt Schreiner wrote:
> > Hi,
> > 
> > On Sun, Feb 04, 2007 at 08:34:31PM -0800, Chuck Silvers wrote:
> > > On Mon, Feb 05, 2007 at 12:54:26AM +0000, Geoff Wing wrote:
> > > > : Log Message:
> > > > : more fixes for the new vnode locking scheme:
> > > > 
> > > > This gives me vnode locking problems symptomatically similar to the one
> > > > you fixed with sys/kern/vfs_lookup.c:1.77
> > > 
> > > ok, could you send me a dump for the new problem?
> > Just another datapoint: mounting procfs and doing "df /proc" hangs df in
> > state "vnlock". Not using procfs gives me a usable system...
> > 
> > mount | grep procfs
> > procfs on /proc type procfs (local)
> > 
> > ps axl | grep df
> >    77  499  161     0  -2  0    48   532 vnlock   D+   ttyp1  0:00.00 df -k 
> > 
> > This is on i386, sources cvs-updated ~21:00 MET
> 
> 
> please update again and let me know if that fixes it or not.
> it was the combination of mountd + procfs (or any non-exportable fs)
> that caused the problem.
Yep! Works for me again! Tried procfs, kernfs & unionfs - all working fine!

Thanks for the quick fix

Kurt