Backup-Error - job failed with err -125 - Operation canceled

D

Digital_Data

Member
May 10, 2019
19
0
6
Sehr geehrte Damen und Herren,

Folgende Situation:
Der Proxmox-Server betreibt aktuell 6 virtuelle Maschinen.
Über Nacht läuft ein Backup dieser Maschinen.
Zwei der Maschinen laufen in einen Error - 125 - Operation canceled
Dabei ist es egal ob der Backup nachts durch ein Job gestartet wird oder manuell per Hand.

Der Job bricht immer bei ca 61% ab.

INFO: Starting Backup of VM 305 (qemu) INFO: Backup started at 2021-03-04 02:34:07 INFO: status = stopped INFO: backup mode: stop INFO: ionice priority: 7 INFO: VM Name: tDD-VMP03-VM05 INFO: include disk 'virtio0' 'local-lvm:vm-305-disk-1' 50G INFO: include disk 'virtio1' 'local-lvm:vm-305-disk-2' 20G INFO: include disk 'virtio2' 'local-lvm:vm-305-disk-0' 30G INFO: creating vzdump archive '/mnt/pve/NFS-STO01-Backup/dump/vzdump-qemu-305-2021_03_04-02_34_07.vma.zst' INFO: starting kvm to execute backup task INFO: started backup task '886e1e6a-cdbe-47e4-a479-ac0708ccb7a8' INFO: 0% (141.4 MiB of 100.0 GiB) in 3s, read: 47.1 MiB/s, write: 37.0 MiB/s INFO: 1% (1.0 GiB of 100.0 GiB) in 23s, read: 45.9 MiB/s, write: 45.8 MiB/s INFO: 2% (2.5 GiB of 100.0 GiB) in 30s, read: 210.6 MiB/s, write: 44.6 MiB/s INFO: 5% (5.0 GiB of 100.0 GiB) in 33s, read: 863.8 MiB/s, write: 14.8 MiB/s INFO: 6% (6.5 GiB of 100.0 GiB) in 36s, read: 513.9 MiB/s, write: 20.7 MiB/s INFO: 8% (8.4 GiB of 100.0 GiB) in 39s, read: 659.2 MiB/s, write: 16.4 MiB/s INFO: 11% (11.5 GiB of 100.0 GiB) in 42s, read: 1.0 GiB/s, write: 548.0 KiB/s INFO: 14% (14.6 GiB of 100.0 GiB) in 45s, read: 1.0 GiB/s, write: 0 B/s INFO: 18% (18.0 GiB of 100.0 GiB) in 48s, read: 1.1 GiB/s, write: 0 B/s INFO: 21% (21.1 GiB of 100.0 GiB) in 51s, read: 1.0 GiB/s, write: 0 B/s INFO: 24% (24.0 GiB of 100.0 GiB) in 54s, read: 1011.4 MiB/s, write: 0 B/s INFO: 27% (27.1 GiB of 100.0 GiB) in 57s, read: 1.0 GiB/s, write: 0 B/s INFO: 30% (30.0 GiB of 100.0 GiB) in 1m, read: 996.7 MiB/s, write: 3.3 MiB/s INFO: 31% (31.4 GiB of 100.0 GiB) in 1m 7s, read: 205.1 MiB/s, write: 65.5 MiB/s INFO: 32% (32.9 GiB of 100.0 GiB) in 1m 10s, read: 499.4 MiB/s, write: 22.3 MiB/s INFO: 33% (33.1 GiB of 100.0 GiB) in 1m 13s, read: 79.0 MiB/s, write: 44.6 MiB/s INFO: 34% (34.5 GiB of 100.0 GiB) in 1m 16s, read: 466.1 MiB/s, write: 21.2 MiB/s INFO: 36% (36.9 GiB of 100.0 GiB) in 1m 19s, read: 804.6 MiB/s, write: 5.6 MiB/s INFO: 37% (37.6 GiB of 100.0 GiB) in 1m 22s, read: 270.3 MiB/s, write: 35.9 MiB/s INFO: 38% (38.3 GiB of 100.0 GiB) in 1m 30s, read: 77.3 MiB/s, write: 42.9 MiB/s INFO: 39% (39.1 GiB of 100.0 GiB) in 1m 41s, read: 80.2 MiB/s, write: 38.1 MiB/s INFO: 40% (40.1 GiB of 100.0 GiB) in 1m 48s, read: 148.6 MiB/s, write: 31.9 MiB/s INFO: 42% (42.2 GiB of 100.0 GiB) in 1m 51s, read: 709.4 MiB/s, write: 12.0 MiB/s INFO: 44% (44.6 GiB of 100.0 GiB) in 1m 54s, read: 801.4 MiB/s, write: 6.6 MiB/s INFO: 46% (46.8 GiB of 100.0 GiB) in 1m 57s, read: 764.2 MiB/s, write: 16.7 MiB/s INFO: 49% (49.4 GiB of 100.0 GiB) in 2m, read: 878.7 MiB/s, write: 5.9 MiB/s INFO: 50% (50.6 GiB of 100.0 GiB) in 2m 3s, read: 406.9 MiB/s, write: 24.9 MiB/s INFO: 51% (51.0 GiB of 100.0 GiB) in 2m 10s, read: 70.2 MiB/s, write: 66.8 MiB/s INFO: 52% (52.0 GiB of 100.0 GiB) in 2m 23s, read: 76.1 MiB/s, write: 75.6 MiB/s INFO: 53% (53.0 GiB of 100.0 GiB) in 2m 37s, read: 75.9 MiB/s, write: 74.2 MiB/s INFO: 54% (54.0 GiB of 100.0 GiB) in 2m 49s, read: 83.5 MiB/s, write: 76.6 MiB/s INFO: 55% (55.0 GiB of 100.0 GiB) in 3m 1s, read: 83.7 MiB/s, write: 83.4 MiB/s INFO: 56% (56.0 GiB of 100.0 GiB) in 3m 13s, read: 87.5 MiB/s, write: 86.4 MiB/s INFO: 57% (57.0 GiB of 100.0 GiB) in 3m 26s, read: 77.5 MiB/s, write: 76.8 MiB/s INFO: 58% (58.0 GiB of 100.0 GiB) in 3m 39s, read: 80.4 MiB/s, write: 77.9 MiB/s INFO: 59% (59.0 GiB of 100.0 GiB) in 3m 51s, read: 82.9 MiB/s, write: 82.4 MiB/s INFO: 60% (60.0 GiB of 100.0 GiB) in 4m 4s, read: 79.6 MiB/s, write: 77.1 MiB/s INFO: 61% (61.0 GiB of 100.0 GiB) in 4m 18s, read: 74.8 MiB/s, write: 73.4 MiB/s INFO: 61% (61.2 GiB of 100.0 GiB) in 4m 20s, read: 60.1 MiB/s, write: 59.7 MiB/s ERROR: job failed with err -125 - Operation canceled INFO: aborting backup job INFO: stopping kvm after backup task ERROR: Backup of VM 305 failed - job failed with err -125 - Operation canceled INFO: Failed at 2021-03-04 02:38:34

Wie könnte ich denn vorgehen dem Fehler auf den Grund zugehen?
Existiert eine Liste mit den verschiedenen Fehlercodes?

Vielen Dank
Digital Data
 
hi,

die fehlermeldung scheint vom system zu kommen [0]:

Macro: int ECANCELED
“Operation canceled.” An asynchronous operation was canceled before it completed. See Asynchronous I/O. When you call aio_cancel, the normal result is for the operations affected to complete with this error; see Cancel AIO Operations.
Click to expand...

kannst du vielleicht probieren:
* vm config posten: qm config VMID
* das backup auf einem anderen storage zu machen (versuch mal auf lokal)


[0]: https://www.gnu.org/software/libc/manual/html_node/Error-Codes.html
 
qm config 305
agent: 1
bootdisk: virtio0
cores: 4
description: -
ide2: none,media=cdrom
memory: 4096
name: tDD-VMP03-VM05
net0: virtio=AE:AE:66:43:69:E8,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=35783326-3833-4f9d-890d-2c631520bd69
sockets: 1
virtio0: local-lvm:vm-305-disk-1,size=50G
virtio1: local-lvm:vm-305-disk-2,size=20G
virtio2: local-lvm:vm-305-disk-0,size=30G
vmgenid: f7b0659f-fe56-49f0-bcf7-2bca8977a834
_________________________________________________________________


Ein Backup auf einen anderen Storage und Local schlägt ebenfalls fehl
 
Last edited:
Heute ncht sind wieder 2 Maschinen nicht fertig durchgeladen.


305: 2021-03-08 02:34:22 INFO: Starting Backup of VM 305 (qemu)
305: 2021-03-08 02:34:22 INFO: status = stopped
305: 2021-03-08 02:34:22 INFO: backup mode: stop
305: 2021-03-08 02:34:22 INFO: ionice priority: 7
305: 2021-03-08 02:34:22 INFO: VM Name: tDD-VMP03-VM05
305: 2021-03-08 02:34:22 INFO: include disk 'virtio0' 'local-lvm:vm-305-disk-1' 50G
305: 2021-03-08 02:34:22 INFO: include disk 'virtio1' 'local-lvm:vm-305-disk-2' 20G
305: 2021-03-08 02:34:22 INFO: include disk 'virtio2' 'local-lvm:vm-305-disk-0' 30G
305: 2021-03-08 02:34:24 INFO: creating vzdump archive '/mnt/pve/NFS-STO01-Backup/dump/vzdump-qemu-305-2021_03_08-02_34_22.vma.zst'
305: 2021-03-08 02:34:24 INFO: starting kvm to execute backup task
305: 2021-03-08 02:34:25 INFO: started backup task '651a2e78-fb8a-4071-8888-3139fbe32040'
305: 2021-03-08 02:34:28 INFO: 0% (138.7 MiB of 100.0 GiB) in 3s, read: 46.2 MiB/s, write: 36.1 MiB/s
305: 2021-03-08 02:34:50 INFO: 1% (1.0 GiB of 100.0 GiB) in 25s, read: 41.8 MiB/s, write: 41.7 MiB/s
305: 2021-03-08 02:34:57 INFO: 2% (2.1 GiB of 100.0 GiB) in 32s, read: 158.9 MiB/s, write: 44.6 MiB/s
305: 2021-03-08 02:35:00 INFO: 4% (4.3 GiB of 100.0 GiB) in 35s, read: 730.9 MiB/s, write: 14.8 MiB/s
305: 2021-03-08 02:35:03 INFO: 6% (6.5 GiB of 100.0 GiB) in 38s, read: 751.7 MiB/s, write: 4.8 MiB/s
305: 2021-03-08 02:35:06 INFO: 7% (7.6 GiB of 100.0 GiB) in 41s, read: 378.3 MiB/s, write: 30.9 MiB/s
305: 2021-03-08 02:35:09 INFO: 10% (10.6 GiB of 100.0 GiB) in 44s, read: 1.0 GiB/s, write: 2.0 MiB/s
305: 2021-03-08 02:35:12 INFO: 13% (13.7 GiB of 100.0 GiB) in 47s, read: 1.0 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:15 INFO: 16% (16.9 GiB of 100.0 GiB) in 50s, read: 1.1 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:18 INFO: 20% (20.1 GiB of 100.0 GiB) in 53s, read: 1.1 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:21 INFO: 23% (23.1 GiB of 100.0 GiB) in 56s, read: 1.0 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:24 INFO: 26% (26.2 GiB of 100.0 GiB) in 59s, read: 1.0 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:27 INFO: 29% (29.3 GiB of 100.0 GiB) in 1m 2s, read: 1.0 GiB/s, write: 0 B/s
305: 2021-03-08 02:35:30 INFO: 30% (30.2 GiB of 100.0 GiB) in 1m 5s, read: 295.6 MiB/s, write: 60.0 MiB/s
305: 2021-03-08 02:35:36 INFO: 31% (31.3 GiB of 100.0 GiB) in 1m 11s, read: 190.3 MiB/s, write: 47.8 MiB/s
305: 2021-03-08 02:35:39 INFO: 32% (32.9 GiB of 100.0 GiB) in 1m 14s, read: 540.1 MiB/s, write: 22.5 MiB/s
305: 2021-03-08 02:35:42 INFO: 33% (33.1 GiB of 100.0 GiB) in 1m 17s, read: 76.4 MiB/s, write: 42.0 MiB/s
305: 2021-03-08 02:35:45 INFO: 34% (34.4 GiB of 100.0 GiB) in 1m 20s, read: 447.8 MiB/s, write: 24.3 MiB/s
305: 2021-03-08 02:35:48 INFO: 36% (36.9 GiB of 100.0 GiB) in 1m 23s, read: 837.6 MiB/s, write: 5.6 MiB/s
305: 2021-03-08 02:35:51 INFO: 37% (37.7 GiB of 100.0 GiB) in 1m 26s, read: 259.8 MiB/s, write: 37.1 MiB/s
305: 2021-03-08 02:35:59 INFO: 38% (38.4 GiB of 100.0 GiB) in 1m 34s, read: 94.8 MiB/s, write: 42.5 MiB/s
305: 2021-03-08 02:36:10 INFO: 39% (39.1 GiB of 100.0 GiB) in 1m 45s, read: 65.5 MiB/s, write: 36.5 MiB/s
305: 2021-03-08 02:36:18 INFO: 40% (40.4 GiB of 100.0 GiB) in 1m 53s, read: 163.6 MiB/s, write: 31.4 MiB/s
305: 2021-03-08 02:36:21 INFO: 42% (42.5 GiB of 100.0 GiB) in 1m 56s, read: 726.7 MiB/s, write: 8.9 MiB/s
305: 2021-03-08 02:36:24 INFO: 44% (45.0 GiB of 100.0 GiB) in 1m 59s, read: 844.1 MiB/s, write: 9.5 MiB/s
305: 2021-03-08 02:36:27 INFO: 47% (47.3 GiB of 100.0 GiB) in 2m 2s, read: 809.2 MiB/s, write: 14.7 MiB/s
305: 2021-03-08 02:36:30 INFO: 49% (50.0 GiB of 100.0 GiB) in 2m 5s, read: 890.0 MiB/s, write: 6.2 MiB/s
305: 2021-03-08 02:36:33 INFO: 50% (50.6 GiB of 100.0 GiB) in 2m 8s, read: 231.4 MiB/s, write: 45.4 MiB/s
305: 2021-03-08 02:36:39 INFO: 51% (51.0 GiB of 100.0 GiB) in 2m 14s, read: 64.2 MiB/s, write: 61.2 MiB/s
305: 2021-03-08 02:36:53 INFO: 52% (52.0 GiB of 100.0 GiB) in 2m 28s, read: 74.9 MiB/s, write: 74.3 MiB/s
305: 2021-03-08 02:37:07 INFO: 53% (53.0 GiB of 100.0 GiB) in 2m 42s, read: 73.3 MiB/s, write: 71.6 MiB/s
305: 2021-03-08 02:37:20 INFO: 54% (54.1 GiB of 100.0 GiB) in 2m 55s, read: 82.5 MiB/s, write: 76.2 MiB/s
305: 2021-03-08 02:37:32 INFO: 55% (55.1 GiB of 100.0 GiB) in 3m 7s, read: 84.3 MiB/s, write: 83.9 MiB/s
305: 2021-03-08 02:37:44 INFO: 56% (56.0 GiB of 100.0 GiB) in 3m 19s, read: 83.1 MiB/s, write: 82.1 MiB/s
305: 2021-03-08 02:37:57 INFO: 57% (57.0 GiB of 100.0 GiB) in 3m 32s, read: 76.4 MiB/s, write: 75.7 MiB/s
305: 2021-03-08 02:38:10 INFO: 58% (58.0 GiB of 100.0 GiB) in 3m 45s, read: 78.1 MiB/s, write: 75.5 MiB/s
305: 2021-03-08 02:38:23 INFO: 59% (59.1 GiB of 100.0 GiB) in 3m 58s, read: 82.8 MiB/s, write: 81.9 MiB/s
305: 2021-03-08 02:38:36 INFO: 60% (60.0 GiB of 100.0 GiB) in 4m 11s, read: 77.1 MiB/s, write: 75.0 MiB/s
305: 2021-03-08 02:38:50 INFO: 61% (61.0 GiB of 100.0 GiB) in 4m 25s, read: 74.3 MiB/s, write: 72.9 MiB/s
305: 2021-03-08 02:38:52 INFO: 61% (61.2 GiB of 100.0 GiB) in 4m 27s, read: 54.4 MiB/s, write: 54.1 MiB/s
305: 2021-03-08 02:38:54 ERROR: job failed with err -125 - Operation canceled
305: 2021-03-08 02:38:54 INFO: aborting backup job
305: 2021-03-08 02:38:54 INFO: stopping kvm after backup task
305: 2021-03-08 02:38:56 ERROR: Backup of VM 305 failed - job failed with err -125 - Operation canceled

Danke
Digital Data
 
ist die zweite maschine ist auch windows?

siehst du irgendwelche fehlermeldung in der VM ueber disks?

kannst du beim cmd chkdsk fuer die disks ausfuehren (z.b. chkdsk C:)
 
oguz said:
ist die zweite maschine ist auch windows?

siehst du irgendwelche fehlermeldung in der VM ueber disks?

kannst du beim cmd chkdsk fuer die disks ausfuehren (z.b. chkdsk C:)
Click to expand...
Hallo,

chkdsk und sfc erkennen keine Fehler.

Die Disks scheinen in Ordnung zu sein

Mit freundlichen Grüßen
Digital Data
 
danke fuers schauen

* kannst du auch probieren die VM zu clonen?

* siehst du vielleicht etwas in journalctl waehrenddessen?

* und bitte pveversion -v posten
 
Hier die PVEversion -v: der Clone-Prozess kann erst am wochenende erfolgen:

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-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.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-3
libpve-guest-common-perl: 3.1-4
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-3
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-1
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
 
Ein Clone-Prozess lief ebenfalls in ein Error
im journalctl konnte ich keine Probleme erkennen

WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "vm-311-disk-3" created.
WARNING: Sum of all thin volume sizes (1015.00 GiB) exceeds the size of thin pool pve/data and the size of whole volume group (930.48 GiB).
transferred: 0 bytes remaining: 53687091200 bytes total: 53687091200 bytes progression: 0.00 %
transferred: 536870912 bytes remaining: 53150220288 bytes total: 53687091200 bytes progression: 1.00 %
transferred: 1079110533 bytes remaining: 52607980667 bytes total: 53687091200 bytes progression: 2.01 %
transferred: 1615981445 bytes remaining: 52071109755 bytes total: 53687091200 bytes progression: 3.01 %
transferred: 2158221066 bytes remaining: 51528870134 bytes total: 53687091200 bytes progression: 4.02 %
transferred: 2695091978 bytes remaining: 50991999222 bytes total: 53687091200 bytes progression: 5.02 %
transferred: 3231962890 bytes remaining: 50455128310 bytes total: 53687091200 bytes progression: 6.02 %
qemu-img: error while reading at byte 3728735744: Input/output error
Logical volume "vm-311-disk-0" successfully removed
Logical volume "vm-311-disk-1" successfully removed
Logical volume "vm-311-disk-2" successfully removed
Logical volume "vm-311-disk-3" successfully removed
TASK ERROR: clone failed: copy failed: command '/usr/bin/qemu-img convert -p -n -f raw -O raw /dev/pve/vm-308-disk-1 zeroinit:/dev/pve/vm-311-disk-3' failed: exit code 1
 
You must log in or register to reply here.

About

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

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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 yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back