Kill destroy process that still hang

[RobertusIT]

Hi

I have this issue, I can't kill or stop this destroy process.

I tried with kill -9, no success.
In webgui, stop button, doesn't works.

qm destroy 114 --purge

ps aux | grep qm
kill 2214241

ps aux | grep qmdestroy
kill -9 2214241

Is absurd that I must to reboot the host.

Please you know a solution ?

 

[dietmar]

Most likely you have an unstable storage system. What is the output of

# pvesm status

 

[RobertusIT]

Most likely you have an unstable storage system. What is the output of

# pvesm status

root@AEROFARA:~# pvesm status
Name Type Status Total Used Available %
ROBNAS nfs active 5802865920 5770014080 32733056 99.43%
SSD1TB dir active 960302824 263580660 647867704 27.45%
USB1TB dir active 960301072 29364172 882082528 3.06%
USB500GB dir active 479596200 366657496 88503044 76.45%
local dir active 15375304 4480320 10092168 29.14%
local-lvm lvmthin active 448999424 150953606 298045817 33.62%

 

[RobertusIT]

is unstable ? where?

 

[VictorSTS]

Post the output of ps aux | grep qmdestroy. To be more specific, the STAT column. If the process is in "D" state, uninterruptible sleep, you will not be able to kill it. This usually happens when some disk I/O operation could not be completed due to the storage not being available/not working correctly (i.e. a NFS storage when the network goes down and can't be reached reliabily or when it gets too full).

 

[RobertusIT]

Post the output of ps aux | grep qmdestroy. To be more specific, the STAT column. If the process is in "D" state, uninterruptible sleep, you will not be able to kill it. This usually happens when some disk I/O operation could not be completed due to the storage not being available/not working correctly (i.e. a NFS storage when the network goes down and can't be reached reliabily or when it gets too full).

root@AEROFARA:~# ps aux | grep qmdestroy
root     1714300  0.0  0.0   6332  2176 pts/0    S+   16:15   0:00 grep qmdestroy
root     2214241  0.0  0.0 251084 14120 ?        Ds   Sep12   0:00 task UPID:AEROFARA:0021C961:11710F59:66E2B90A:qmdestroy:114:root@pam:
root     2215833  0.0  0.0 251164 13940 ?        Ds   Sep12   0:00 task UPID:AEROFARA:0021CF99:11715924:66E2B9C7:qmdestroy:114:root@pam:
root     2880668  0.0  0.1 251328 38148 ?        Ds   Sep13   0:00 task UPID:AEROFARA:002BF49C:11EBF857:66E3F3B0:qmdestroy:114:root@pam:
root     2881896  0.0  0.1 251008 39636 ?        Ds   Sep13   0:00 task UPID:AEROFARA:002BF968:11EC34C0:66E3F44B:qmdestroy:114:root@pam:

I use internal storage. But happend a lot of times some issue like that.