On 4 Oct, Mikhail Teterin wrote: > вівторок 04 жовтень 2005 13:08, Don Lewis Ви написали: >> Hung trying to lock a vnode ... >> >> What other processes are in the D state, and what is their wchan info? > 0 45773 45771 0 -4 0 1740 1208 ufs D p1 0:00,32 dmake > 0 45806 45788 350 -4 0 1548 632 ufs D p1 0:00,00 /bin/tcsh -fc zipdep.pl -u -j ../../../ > 0 65072 64985 271 -4 0 1248 480 ufs D p1 0:00,00 /bin/tcsh -fc if ( -e ../../../unxfbsd.p > 0 65327 8694 0 -4 0 1432 908 ufs D+ p2 0:02,05 find work/ -name provider.o Looks like some sort of vnode locking bug. All the other processes are system processes in their usual idle state. > The two tcsh and the dmake process are remnants of the interrupted OOo build. > What's a "wchan"? wchan is the column labeled MWCHAN in the ps lax output. The wchan info for the processes above is "ufs". >> Are you using filesystem snapshots? > > Not "on purpose". This is the /var partition, BTW, nothing fancy: > > /dev/da0s2e on /var (ufs, local, soft-updates) > > The only suspect thing about it, that I can say, is that "a few reboots ago" > I used growfs to extend it. Thanks for your help, I'm hoping that something will show up on my HEAD box because it has vnode lock debugging enabled. If not, it will require some time in the kernel debugger.Received on Tue Oct 04 2005 - 15:43:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:44 UTC