On 4 Oct, Mikhail Teterin wrote: >> Is this problem repeatable? > > Yes, as per my original e-mail, it has happened twice already. > > The first time the last command in the build log was very similar, but > involved a different object file. The perl-process was stuck as "running" > and I was able to kill it, but the subsequent `rm -rf work' became > unkillable in "ufs", just like `find' is now. > >> What does "ps lax" say about the hung processes? > > 0 65327 8694 0 -4 0 1432 908 ufs D+ p2 0:02,05 find work/ -name provider.o Hung trying to lock a vnode ... What other processes are in the D state, and what is their wchan info? Are you using filesystem snapshots?Received on Tue Oct 04 2005 - 15:08:36 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:44 UTC