Hi Forum
I have an issue trying to kill a long running process:
My FreeBSD is FreeBSD 7.2-RELEASE-p6 an old FreeNAS system.
Top shows two ls processes:
Which are all in the "R" State.
The issue appeared when tried to acess my geom 5 RAID device which in in the "rebuilding" state.
Is there maybe an other way? like unmounting the raid, or a different kill command?
My SCP tool was unable to list the director and aborted. The remainders where these two ls commands that currently use 50% CPU (i.e. two cores)
I have tried all tricks in the book (I know of) with kill -9, kill 11, kill -15
But the processes are still there.
A reboot would do the trick but as the raid is rebuilding I do not necessarily want to spoil this. After two days it is at 16% and a reboot will likely reduce this to 0%
I have an issue trying to kill a long running process:
My FreeBSD is FreeBSD 7.2-RELEASE-p6 an old FreeNAS system.
Top shows two ls processes:
Code:
last pid: 8735; load averages: 2.00, 2.00, 2.00 up 2+12:44:51 09:20:39
28 processes: 3 running, 25 sleeping
CPU: 0.0% user, 0.0% nice, 50.2% system, 0.2% interrupt, 49.6% idle
Mem: 13M Active, 265M Inact, 123M Wired, 48K Cache, 100M Buf, 486M Free
Swap:
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
3824 root 1 -8 0 3436K 1256K CPU1 1 23.9H 100.00% ls
3801 root 1 -8 0 3436K 1264K CPU3 3 23.4H 100.00% ls
Which are all in the "R" State.
Code:
ps -U root |grep ls
3801 ?? R 1404:20.20 ls -la /mnt/raid/...
3807 ?? D 0:00.01 ls -la /mnt/raid/...
3824 ?? R 1432:47.22 ls -la /mnt/raid/..
The issue appeared when tried to acess my geom 5 RAID device which in in the "rebuilding" state.
Is there maybe an other way? like unmounting the raid, or a different kill command?
My SCP tool was unable to list the director and aborted. The remainders where these two ls commands that currently use 50% CPU (i.e. two cores)
I have tried all tricks in the book (I know of) with kill -9, kill 11, kill -15
But the processes are still there.
A reboot would do the trick but as the raid is rebuilding I do not necessarily want to spoil this. After two days it is at 16% and a reboot will likely reduce this to 0%