Interrupted restore file download; remaining qemu-system-x86_64 and (b)locking new attempts

[Mark Schouten]

Hi,

A customer wanted to dowload a file from a PBS backup via the PVE GUI 
and the download started into a too small directory. He interrupted the 
download, but now he cannot restart the download, because the PVE-node 
is still working on the (stopped) restore.

I see this process running, which I believe is the (old) 
restore-process:

root      125794 87.0  0.6 2447456 1774048 ?     Sl   16:25  17:42 
qemu-system-x86_64 -chardev 
file,id=log,path=/dev/null,logfile=/dev/fd/20,logappend=on -serial 
chardev:log -vnc none -enable-kvm -kernel 
/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/bzImage -initrd 
/dev/fd/19 -append quiet panic=1 zfs_arc_min=16777216 
zfs_arc_max=67108864 memhp_default_state=online_kernel -daemonize 
-pidfile /dev/fd/18 -name pbs-restore-vm -m 192M,slots=1,maxmem=704M 
-drive 
file=pbs:repository=XXX at pbs@10.230.249.2:8007:pbs,,snapshot=vm/260/2023-05-01T19:14:47Z,,archive=drive-scsi1.img.fidx,read-only=on,if=none,id=drive0 
-device pci-bridge,id=bridge2,chassis_nr=2 -device 
virtio-blk-pci,drive=drive0,serial=drive-scsi1,bus=bridge2 -drive 
file=pbs:repository=XXX at pbs@10.230.249.2:8007:pbs,,snapshot=vm/260/2023-05-01T19:14:47Z,,archive=drive-scsi0.img.fidx,read-only=on,if=none,id=drive1 
-device virtio-blk-pci,drive=drive1,serial=drive-scsi0,bus=bridge2 
-device vhost-vsock-pci,guest-cid=10,disable-legacy=on -chardev 
socket,id=qmp,path=/run/proxmox-backup/file-restore-qmp-10.sock,server=on,wait=off 
-mon chardev=qmp,mode=control

  Is it safe to kill this process, so the customer can restart his 
restore?

—
Mark Schouten, CTO
Tuxis B.V.
mark at tuxis.nl / +31 318 200208