Subject: Re: process wedged in vnlock
To: Tom Spindler <email@example.com>
From: Zafer Aydogan <firstname.lastname@example.org>
Date: 03/12/2007 18:25:44
I've upgraded to 4.99.14 yesterday and my system starts to slowly lock
up after find is hanging in vnlock state.
"find" is executed for example by running daily cronjobs at 3 o'clock.
Although I could trigger it by running "locate.update".
The odd thing is that running find and locate update immediately after
a reboot works just fine.
I've had no problems until 4.99.12.
I'm running LFS as a root file system without any problems since
3.99.21 but i doubt it's an LFS problem.
2007/2/27, Tom Spindler <email@example.com>:
> > Are you folks on uni-processor or multi-processor machines?
> > I've been trying to cause a dual-core box to fall over, and have been
> > unable to so far...
> > cvs rdiff -r1.4 -r1.5 src/sys/kern/kern_turnstile.c
> > If the trace includes ufs_ihash* it would be good to see the output of
> > "ps/l", and note if anything is sleeping on "tstile" if this happens again..
> > The output of "show lock ufs_hashlock" would be useful here. If it shows
> > that the lock is currently held, you can get a backtrace from the owner
> > using "t/a <address of lwp>".
> I'll try that when I get home.
> As it happens, I can immediately cause it to happen within about
> ten seconds by doing "find . -type d -print >/dev/null".