[SOLVED] Backup abbrechen?!

[Soc]

Hallo zusammen,

ich habe die aktuelle pve auf einen Intel NUC am lsufen und hsbe folgendes Problem festgestellt.
ich wollte ein laufendes Backup abbrechen und habe dies im Statusfenster durch den STOP Button versucht.
leider ist dann die VM nicht mehr ansprechbar und das Backup wird nicht beendet.

weder ein Herunterfahren, noch ein stoppen der VM geht.
Selbst das beenden der pve scheitert und ich musste den NUC am Ein-/Ausschalter hart benden.
jemand einen Tipp?

 

[fabian]

funktioniert hier. bitte genaue 'pveversion -v', storage und VM config posten sowie den backup task log/system log vom versuch..

 

[Soc]

Habe es noch ein wenig eingrenzen können.
Der Abbruch funktioniert wenn das Backup Ziel local ist.
es funktioniert NICHT wenn das Ziel ein USB-Stick (ext4) ist.

Dann sieht es so aus:

INFO: starting new backup job: vzdump 800 --compress lzo --storage usb-sda1 --mode stop --node pve --remove 0
INFO: Starting Backup of VM 800 (qemu)
INFO: Backup started at 2020-05-04 10:22:55
INFO: status = running
INFO: update VM 800: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: D10TEST
INFO: include disk 'scsi0' 'local-lvm:vm-800-disk-0' 16G
INFO: stopping vm
INFO: creating archive '/media/sda1/dump/vzdump-qemu-800-2020_05_04-10_22_55.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '579b15bb-b2cb-4dfa-b56c-3398c5a2af59'
INFO: resuming VM again after 4 seconds
INFO: status: 0% (3866624/17179869184), sparse 0% (995328), duration 5, read/write 0/0 MB/s
INFO: status: 1% (174850048/17179869184), sparse 0% (125689856), duration 93, read/write 1/0 MB/s
ERROR: interrupted by signal
INFO: aborting backup job

Im Status Fenster erscheint Fehler: unexpected status

Danach ist die VM tot.

Ein Herunterfahren bringt Fehler: VM is locked (backup)

 

[Soc]

pve lässt sich auch nicht mehr Herunterfahren. Der NUC muss hart ausgeschaltet werden.

 

[oguz]

hi,

Ein Herunterfahren bringt Fehler: VM is locked (backup)

qm unlock VMID

bitte:

genaue 'pveversion -v', storage und VM config posten sowie den backup task log/system log vom versuch..

 

[Soc]

pversion -v

proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Bin da etwas überfragt wo ich die "storage und VM config" her bekomme, bzw. wie die Files heissen?!

Task-Log:

INFO: starting new backup job: vzdump 800 --storage usb-sda1 --node pve --remove 0 --compress lzo --mode stop
INFO: Starting Backup of VM 800 (qemu)
INFO: Backup started at 2020-05-07 07:19:36
INFO: status = running
INFO: update VM 800: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: D10TEST
INFO: include disk 'scsi0' 'local-lvm:vm-800-disk-0' 16G
INFO: stopping vm
INFO: creating archive '/media/sda1/dump/vzdump-qemu-800-2020_05_07-07_19_36.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '719157c5-745b-475d-988e-572771324616'
INFO: resuming VM again after 4 seconds
INFO: status: 0% (7602176/17179869184), sparse 0% (1056768), duration 3, read/write 2/2 MB/s
INFO: status: 1% (174850048/17179869184), sparse 0% (124780544), duration 28, read/write 6/1 MB/s
ERROR: interrupted by signal
INFO: aborting backup job

System-Log:

May 07 07:19:40 pve kernel: scsi 4:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 6
May 07 07:19:40 pve kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] 15425536 512-byte logical blocks: (7.90 GB/7.36 GiB)
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] Write Protect is off
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 07 07:19:40 pve kernel: sdb: sdb1
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
May 07 07:19:40 pve pve6-usb-automount[479]: UDEV event for action::add and device::sdb device_path::/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.3/2-4.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb
May 07 07:19:40 pve pve6-usb-automount[479]: Add event for sdb
May 07 07:19:40 pve kernel: device tap800i0 entered promiscuous mode
May 07 07:19:40 pve pve6-usb-automount[479]: Blockdevice has no fs-type
May 07 07:19:40 pve systemd-udevd[3708]: Using default interface naming scheme 'v240'.
May 07 07:19:40 pve systemd-udevd[3708]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 07 07:19:40 pve systemd-udevd[3708]: Could not generate persistent MAC address for fwbr800i0: No such file or directory
May 07 07:19:40 pve systemd-udevd[3706]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 07 07:19:40 pve systemd-udevd[3706]: Using default interface naming scheme 'v240'.
May 07 07:19:40 pve systemd-udevd[3699]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 07 07:19:40 pve systemd-udevd[3706]: Could not generate persistent MAC address for fwpr800p0: No such file or directory
May 07 07:19:40 pve systemd-udevd[3699]: Using default interface naming scheme 'v240'.
May 07 07:19:40 pve systemd-udevd[3699]: Could not generate persistent MAC address for fwln800i0: No such file or directory
May 07 07:19:40 pve kernel: fwbr800i0: port 1(fwln800i0) entered blocking state
May 07 07:19:40 pve kernel: fwbr800i0: port 1(fwln800i0) entered disabled state
May 07 07:19:40 pve kernel: device fwln800i0 entered promiscuous mode
May 07 07:19:40 pve kernel: fwbr800i0: port 1(fwln800i0) entered blocking state
May 07 07:19:40 pve kernel: fwbr800i0: port 1(fwln800i0) entered forwarding state
May 07 07:19:40 pve pve6-usb-automount[479]: UDEV event for action::add and device::sdb1 device_path::/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.3/2-4.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
May 07 07:19:40 pve pve6-usb-automount[479]: Add event for sdb1
May 07 07:19:40 pve kernel: vmbr0: port 2(fwpr800p0) entered blocking state
May 07 07:19:40 pve kernel: vmbr0: port 2(fwpr800p0) entered disabled state
May 07 07:19:40 pve kernel: device fwpr800p0 entered promiscuous mode
May 07 07:19:40 pve kernel: vmbr0: port 2(fwpr800p0) entered blocking state
May 07 07:19:40 pve kernel: vmbr0: port 2(fwpr800p0) entered forwarding state
May 07 07:19:40 pve pve6-usb-automount[479]: Create mount dir </media/sdb1>
May 07 07:19:40 pve kernel: fwbr800i0: port 2(tap800i0) entered blocking state
May 07 07:19:40 pve kernel: fwbr800i0: port 2(tap800i0) entered disabled state
May 07 07:19:40 pve kernel: fwbr800i0: port 2(tap800i0) entered blocking state
May 07 07:19:40 pve kernel: fwbr800i0: port 2(tap800i0) entered forwarding state
May 07 07:19:40 pve kernel: EXT4-fs (sdb1): recovery complete
May 07 07:19:40 pve kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
May 07 07:19:40 pve pve6-usb-automount[479]: Device sdb1 was mounted on /media/sdb1
May 07 07:19:40 pve pve6-usb-automount[479]: UDEV event for action::remove and device::sdb1 device_path::/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.3/2-4.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
May 07 07:19:40 pve kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1WRITE) flags 0x800 phys_seg 0 prio class 0
May 07 07:19:40 pve kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
May 07 07:19:40 pve pve6-usb-automount[479]: Remove event for sdb1
May 07 07:19:40 pve systemd[1]: media-sdb1.mount: Succeeded.
May 07 07:19:40 pve systemd[2111]: media-sdb1.mount: Succeeded.
May 07 07:19:40 pve pve6-usb-automount[479]: Device sdb1 was unmounted
May 07 07:19:40 pve pve6-usb-automount[479]: UDEV event for action::remove and device::sdb device_path::/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.3/2-4.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb
May 07 07:19:40 pve pve6-usb-automount[479]: Remove event for sdb
May 07 07:19:40 pve pve6-usb-automount[479]: Mount dir for device sdb was not found
May 07 07:19:41 pve pve6_usb_automount.py[479]: create storage failed: error with cfs lock 'file-storage_cfg': unable to activate storage 'usb-sdb1' - directory is expected to be a mount point but is not mounted: '/media/sdb1'
May 07 07:19:41 pve pve6_usb_automount.py[479]: delete storage failed: error with cfs lock 'file-storage_cfg': storage 'usb-sdb1' does not exist
May 07 07:19:52 pve kernel: usb 2-4.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
May 07 07:20:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:20:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:20:00 pve systemd[1]: Started Proxmox VE replication runner.
May 07 07:21:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:21:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:21:00 pve systemd[1]: Started Proxmox VE replication runner.
May 07 07:21:06 pve pvedaemon[1278]: <root@pam> end task UPIDve:00000E4D:0001095E:5EB39A68:vzdump:800:root@pam: unexpected status
May 07 07:22:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:22:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:22:00 pve systemd[1]: Started Proxmox VE replication runner.
May 07 07:23:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:23:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:23:00 pve systemd[1]: Started Proxmox VE replication runner.
May 07 07:23:32 pve systemd[1]: Starting Cleanup of Temporary Directories...
May 07 07:23:32 pve systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
May 07 07:23:32 pve systemd[1]: Started Cleanup of Temporary Directories.
May 07 07:24:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:24:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:24:00 pve systemd[1]: Started Proxmox VE replication runner.
May 07 07:24:55 pve pvedaemon[1279]: <root@pam> successful auth for user 'root@pam'
May 07 07:25:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 07 07:25:00 pve systemd[1]: pvesr.service: Succeeded.
May 07 07:25:00 pve systemd[1]: Started Proxmox VE replication runner.

 

[fabian]

das USB device verschwindet zwischendurch..

 

[Soc]

Ich habe übrigens den gleichen Test mit gleichen Ergebnis mit einer USB-Disk durchgeführt.
Unterbreche ich den Backup nicht, dann wird er ordnungsgemäß durchgeführt (Restore geht auch).

 

[fabian]

ist die USB platte dauerhaft eingebunden? oder wird das per hook script aktiv rund ums backup gemacht?

 

[Soc]

Die USB wird via automount beim boot an pve gemountet und bleibt ständig dran.

 

[fabian]

ah, das USB device im log ist ein anderes als das auf das gesichert wird? kannst du mal /etc/pve/storage.cfg und den output von 'qm config XXX' für die betreffende VM posten?

 

[Soc]

Das Log ist von den USB-Stick (waren meine ersten Versuche). Anschließend habe ich es noch mit einer USB-Disk (kein Log geposted) versucht.
war aber das gleiche Ergebnis.
Die Daten poste ich heute Nachmittag (habe aktuell keinen Zugriff auf pve).

 

[Soc]

dir: local
path /var/lib/vz
content backup,vztmpl,iso

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

dir: usb-sda1
path /media/sda1
content vztmpl,backup,iso
is_mountpoint 1
maxfiles 24
shared 0

nfs: nfsbackup
export /volume1/PVE2_Backup
path /mnt/pve/nfsbackup
server 192.168.50.15
content backup
maxfiles 100
options vers=3

dir: usb-sdb1
path /media/sdb1
content iso,backup,vztmpl
is_mountpoint 1
maxfiles 3

usb-sdb1 ist der usb stick der für den Backup verwendet werden soll.

agent: 1
bootdisk: scsi0
cores: 4
ide2: local:iso/debian-9.8.0-amd64-netinst.iso,media=cdrom
memory: 4096
name: D98TEST
net0: virtio=96:59:18:49:F9:5E,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
parent: SS20200507
scsi0: local-lvm:vm-801-disk-0,size=16G
scsihw: virtio-scsi-pci
smbios1: uuid=1a3dbe3d-b2c8-40f0-a980-30ef64c1acab
sockets: 1
usb0: host=2-4.4,usb3=1
vmgenid: 2ab6dc8b-0e62-4ae1-acb1-4827a05fdee4

Es ist noch ein anderer usb-stick der vm zugeordnet (also nicht wundern)

 

[fabian]

tritt das problem auch auf wenn der USB stick nicht durchgereicht wird? eventuell resetted das durchreichen den usb hub an dem auch das backup target liegt?

 

[Soc]

Habe ich anfänglich auch vermutet. War leider nicht so.
gerade habe ich den Backup USB Stick mal direkt an den Intel NUC angeschlossen und nicht an den Hub wo die anderen USB-Sticks hängen.
Ergebnis leider das Gleiche.

 

[fabian]

funktioniert ein backup(-abbruch) einer VM, die kein usb gerät durchreicht?

 

[Soc]

Habe ich schon probiert Und alle USB-Sticks (2) komplett weg genommen (Options) und gezogen.
hat auch nichts verändert.
Wie bereits beschrieben. Wenn ich das Backup durchlaufen lasse schließt es sauber ab und auch ein Restore funktioniert.

 

[fabian]

bitte nochmal folgendes posten:

storage.cfg
config einer VM ohne USB pass-through
pvesm status vor backup
backup log dieser VM bei backup auf USB storage OHNE abbruch
pvesm status nach backup
backup log dieser VM bei backup auf USB storage MIT abbruch
pvesm status nach backup
journal output über den gesamten zeitraum dieser schritte (eventuell vorher persistentens journal anmachen, falls der letzte schritt das system zum hängen bringen kann!)

mein bauchgefühl sagt immer noch dass der USB passthrough schuld ist

 

[Soc]

Storage.cfg (vor Test)
dir: local
path /var/lib/vz
content vztmpl,iso,backup

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

dir: usb-sda1
path /media/sda1
content iso,backup,vztmpl
is_mountpoint 1
maxfiles 24
shared 0

nfs: nfsbackup
export /volume1/PVE2_Backup
path /mnt/pve/nfsbackup
server 192.168.50.15
content backup
maxfiles 100
options vers=3

dir: usb-sdb1
path /media/sdb1
content iso,backup,vztmpl
is_mountpoint 1
maxfiles 10
shared 0

Config der VM 900 (vor Test)
root@pve2:~# qm config 900
agent: 1
bootdisk: scsi0
cores: 2
ide2: local:iso/debian-10.3.0-amd64-netinst.iso,media=cdrom
memory: 4096
net0: virtio=9A:74:F9:1D:6B:03,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-900-disk-0,size=8G
scsihw: virtio-scsi-pci
smbios1: uuid=f9ad9e7a-2f34-4ce1-bd51-c1f2bf7e7005
sockets: 1
vmgenid: ad9d9d25-b767-4e24-9b02-527a49bd42fb

pvesm status (vor Test)
Name Type Status Total Used Available %
local dir active 59600812 3669884 52873676 6.16%
local-lvm lvmthin active 154533888 30474082 124059805 19.72%
nfsbackup nfs active 5754154624 2888047488 2865988352 50.19%
usb-sda1 dir active 960349188 326800 911169604 0.03%
usb-sdb1 dir active 15033720 456120 13794212 3.03%

Log Backup (ohne Abbruch):
INFO: starting new backup job: vzdump 900 --storage usb-sdb1 --mode stop --compress lzo --remove 0 --node pve2
INFO: Starting Backup of VM 900 (qemu)
INFO: Backup started at 2020-05-11 12:50:17
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: include disk 'scsi0' 'local-lvm:vm-900-disk-0' 8G
INFO: stopping vm
INFO: creating archive '/media/sdb1/dump/vzdump-qemu-900-2020_05_11-12_50_17.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '9e1b3cd1-3dc4-46c0-90cd-bd231d176e98'
INFO: resuming VM again after 3 seconds
INFO: status: 1% (140640256/8589934592), sparse 1% (123342848), duration 3, read/write 46/5 MB/s
INFO: status: 2% (174850048/8589934592), sparse 1% (126357504), duration 30, read/write 1/1 MB/s
INFO: status: 3% (262275072/8589934592), sparse 1% (141709312), duration 71, read/write 2/1 MB/s
INFO: status: 4% (349700096/8589934592), sparse 1% (145674240), duration 116, read/write 1/1 MB/s
INFO: status: 5% (429522944/8589934592), sparse 1% (150396928), duration 153, read/write 2/2 MB/s
INFO: status: 6% (520749056/8589934592), sparse 1% (152633344), duration 226, read/write 1/1 MB/s
INFO: status: 7% (604372992/8589934592), sparse 1% (165466112), duration 290, read/write 1/1 MB/s
INFO: status: 8% (691798016/8589934592), sparse 2% (178405376), duration 351, read/write 1/1 MB/s
INFO: status: 9% (775421952/8589934592), sparse 2% (179695616), duration 461, read/write 0/0 MB/s
INFO: status: 10% (859045888/8589934592), sparse 2% (184717312), duration 522, read/write 1/1 MB/s
INFO: status: 11% (946470912/8589934592), sparse 2% (187383808), duration 580, read/write 1/1 MB/s
INFO: status: 12% (1033895936/8589934592), sparse 2% (198127616), duration 611, read/write 2/2 MB/s
INFO: status: 13% (1117519872/8589934592), sparse 2% (212615168), duration 650, read/write 2/1 MB/s
INFO: status: 14% (1208745984/8589934592), sparse 2% (228769792), duration 680, read/write 3/2 MB/s
INFO: status: 15% (1288568832/8589934592), sparse 2% (244436992), duration 706, read/write 3/2 MB/s
INFO: status: 16% (1379794944/8589934592), sparse 3% (262086656), duration 728, read/write 4/3 MB/s
INFO: status: 17% (1467219968/8589934592), sparse 3% (266350592), duration 768, read/write 2/2 MB/s
INFO: status: 18% (1547042816/8589934592), sparse 3% (283295744), duration 797, read/write 2/2 MB/s
INFO: status: 19% (1638268928/8589934592), sparse 3% (296665088), duration 831, read/write 2/2 MB/s
INFO: status: 20% (1721892864/8589934592), sparse 3% (298917888), duration 867, read/write 2/2 MB/s
INFO: status: 21% (1805516800/8589934592), sparse 3% (302403584), duration 911, read/write 1/1 MB/s
INFO: status: 22% (1896742912/8589934592), sparse 3% (313217024), duration 945, read/write 2/2 MB/s
INFO: status: 23% (1976565760/8589934592), sparse 3% (315031552), duration 974, read/write 2/2 MB/s
INFO: status: 24% (2063990784/8589934592), sparse 3% (329031680), duration 1013, read/write 2/1 MB/s
INFO: status: 25% (2155216896/8589934592), sparse 4% (354226176), duration 1047, read/write 2/1 MB/s
INFO: status: 26% (2288254976/8589934592), sparse 5% (457666560), duration 1065, read/write 7/1 MB/s
INFO: status: 27% (2326265856/8589934592), sparse 5% (457670656), duration 1083, read/write 2/2 MB/s
INFO: status: 28% (2406088704/8589934592), sparse 5% (458784768), duration 1106, read/write 3/3 MB/s
INFO: status: 29% (2554331136/8589934592), sparse 6% (528928768), duration 1131, read/write 5/3 MB/s
INFO: status: 39% (3360292864/8589934592), sparse 15% (1322266624), duration 1136, read/write 161/2 MB/s
INFO: status: 100% (8589934592/8589934592), sparse 76% (6551891968), duration 1139, read/write 1743/0 MB/s
INFO: transferred 8589 MB in 1139 seconds (7 MB/s)
INFO: archive file size: 971MB
INFO: Finished Backup of VM 900 (00:19:02)
INFO: Backup finished at 2020-05-11 13:09:19
INFO: Backup job finished successfully
TASK OK

pvesm status (nach erfolgreichen Backup)
I
Name Type Status Total Used Available %
local dir active 59600812 3672688 52870872 6.16%
local-lvm lvmthin active 154533888 30474082 124059805 19.72%
nfsbackup nfs active 5754154624 2888146944 2865888896 50.19%
usb-sda1 dir active 960349188 326800 911169604 0.03%
usb-sdb1 dir active 15033720 1450980 12799352 9.65%

Log Backup (MIT Abbruch):
INFO: starting new backup job: vzdump 900 --remove 0 --node pve2 --storage usb-sdb1 --mode stop --compress lzo
INFO: Starting Backup of VM 900 (qemu)
INFO: Backup started at 2020-05-11 13:12:45
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: include disk 'scsi0' 'local-lvm:vm-900-disk-0' 8G
INFO: stopping vm
INFO: creating archive '/media/sdb1/dump/vzdump-qemu-900-2020_05_11-13_12_45.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task 'f663ef1c-a2bf-4ef6-b693-befa61e1940f'
INFO: resuming VM again after 3 seconds
INFO: status: 0% (38010880/8589934592), sparse 0% (31756288), duration 3, read/write 12/2 MB/s
INFO: status: 1% (140640256/8589934592), sparse 1% (123174912), duration 8, read/write 20/2 MB/s
INFO: status: 2% (174850048/8589934592), sparse 1% (126148608), duration 26, read/write 1/1 MB/s
ERROR: interrupted by signal
INFO: aborting backup job

pvesm status (nach Backup Abbruch)
Name Type Status Total Used Available %
local dir active 59600812 3672776 52870784 6.16%
local-lvm lvmthin active 154533888 30474082 124059805 19.72%
nfsbackup nfs active 5754154624 2888250752 2865785088 50.19%
usb-sda1 dir active 960349188 326800 911169604 0.03%
usb-sdb1 dir active 15033720 1484512 12765820 9.87%

 

[Soc]

Log siehe file