DragonFly bugs List (threaded) for 2008-09
DragonFly BSD
DragonFly bugs List (threaded) for 2008-09
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Process stuck with an empty STATE


From: YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>
Date: Wed, 10 Sep 2008 11:49:16 +0900

Hello.
I very occasionally (only twice as far as I recall) see this on 2.0-RELEASE
or -DEVELOPMENT in `top' output(the following is on my mail server running
2.0-RELEASE):

load averages:  0.00,  0.00,  0.00                     up 13+15:09:03  11:26:24
79 processes:  79 running
CPU states:     % user,     % nice,     % system,     % interrupt,     % idle
Mem: 83M Active, 241M Inact, 130M Wired, 26M Cache, 59M Buf, 1116K Free
Swap: 2048M Total, 340K Used, 2048M Free

  PID USERNAME  PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
44758 qhwt      230   0     0K     4K          0:06 182.89% 77.44% git

`kill' or other tools can't locate this process, and I can't find it under
/proc filesystem either.  Unfortunately I forgot plugging in the keyboard
when it booted, so probably I can't drop into DDB.  There's no `cache_lock'
diagnostic messages on the console.
The `git' command was probably running on HAMMER filesystem, but it's been
regularly pruned and reblocked, and I think it has enough room:

Filesystem       Size   Used  Avail Capacity  Mounted on
/dev/ad0s1a      496M   364M    93M    80%    /
/dev/ad0s1e      7.9G   5.0G   2.3G    69%    /var
/dev/ad0s1f      7.9G   1.2G   6.0G    17%    /u
HAMMER           100G    23G    77G    23%    /HAMMER
/dev/ad0s1h       22G    11G   9.5G    53%    /backup
procfs           4.0K   4.0K     0B   100%    /proc
/HAMMER/@@-1:1   100G    23G    77G    23%    /home
/HAMMER/@@-1:2   100G    23G    77G    23%    /home/source
/HAMMER/@@-1:4   100G    23G    77G    23%    /usr/obj

It's not limited to `git' command; I've seen a similar stuck process
(cc1) during buildworld loops on another machine running -DEVELOPMENT.
The kernel and the world has been built on August 24, so it's not the
lastest.  Does anyone know if it's already been resolved?

Thanks.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]