Backup failed, high IO delay

spearox

Member
Jun 6, 2013
81
1
8
Hi all,

I got a problem.
I have an NFS mount on the server where backup goes.
Once the backup failed and the vzdump lock file not deleted and the vzdump still alive.
I tryed to stop the task but not success, then I killed the vzdump process, now its not running but the task still show its running and the IO delay on server fix 25% after the process failed.

How can I kill, stop without server restart? The NFS mount is live, I think the problem of process fail is the nfs mount gone once.
 

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
376
38
28
Hi,
as a first step you might want to check out what instances of vzdump are running with `ps aux | grep vzdump`.
 

spearox

Member
Jun 6, 2013
81
1
8
Hi,
as a first step you might want to check out what instances of vzdump are running with `ps aux | grep vzdump`.
I killed the processes already as i mentioned above.
The output:
Code:
root@node1:~# ps aux | grep vzdump
root      6069  0.0  0.1 522688 86812 ?        Ds   Feb07   0:14 task UPID:node1:000017B5:1D2B434D:5C5B66F1:vzdump::root@pam:
root     21004  0.0  0.0  12788   936 pts/0    S+   08:23   0:00 grep vzdump
 

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
376
38
28
root 6069 0.0 0.1 522688 86812 ? Ds Feb07 0:14 task UPID:node1:000017B5:1D2B434D:5C5B66F1:vzdump::root@pam:
The status of the task is "Ds" so it is waiting for IO, causing your high IO delays. You can try to stop the task in the WebUI, this should send a SIGTERM to the task and clean up afterwards. If this does not work, you might want to try to send a SIGTERM to the task directly.
 

spearox

Member
Jun 6, 2013
81
1
8
Its not work. :/
Code:
root@node1:~# ps -ef|grep vz
root      6069     1  0 Feb07 ?        00:00:14 task UPID:node1:000017B5:1D2B434D:5C5B66F1:vzdump::root@pam:
root     23083 19501  0 07:18 pts/0    00:00:00 grep vz
root@node1:~# kill -15 6069
root@node1:~# ps -ef|grep vz
root      6069     1  0 Feb07 ?        00:00:14 task UPID:node1:000017B5:1D2B434D:5C5B66F1:vzdump::root@pam:
root     23532 19501  0 07:18 pts/0    00:00:00 grep vz
root@node1:~#
 

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
376
38
28
Then you might be more drastic and send a SIGKILL
 

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
376
38
28
Then unfortunately you will have to reboot the machine to get rid of the process as it is in a uninterruptible sleep.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!