After upgrade to proxmox 7 i can't do backup of Windows 10

[Fullreg]

With Proxmox i can do backup on Ubuntu, Freenas, but i received err -11 if i try with Windows 10. The last time i did backup is when proxmox are 6.xx.
here the err:

()

Task viewer: VM/CT 100 - Backup

OutputStatus

Stop
INFO: starting new backup job: vzdump 100 --storage ProxmoxShare --remove 0 --mode stop --compress zstd --node pve
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2021-07-18 22:41:52
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: Windows10UT
INFO: include disk 'ide0' 'FastSSD:vm-100-disk-0' 80G
INFO: creating vzdump archive '/mnt/pve/ProxmoxShare/dump/vzdump-qemu-100-2021_07_18-22_41_52.vma.zst'
INFO: starting kvm to execute backup task
INFO: started backup task '6b42f03e-40c0-4581-8645-1f9d2ad3c175'
INFO: 0% (36.0 MiB of 80.0 GiB) in 1s, read: 36.0 MiB/s, write: 23.4 MiB/s
ERROR: job failed with err -11 - Resource temporarily unavailable
INFO: aborting backup job
INFO: stopping kvm after backup task
ERROR: Backup of VM 100 failed - job failed with err -11 - Resource temporarily unavailable
INFO: Failed at 2021-07-18 22:41:56
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[mira]

Please provide the output of pveversion -v, qm config 100 and cat /etc/pve/storage.cfg.

 

[Fullreg]

Sorry for the delay, i just come back for Intraocular lens implant. Now i will send the info.

First question : pveversion -v

proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

Second question : qm config 100

boot: order=ide0;ide2;net0
cores: 8
ide0: FastSSD:vm-100-disk-0,size=80G
ide2: none,media=cdrom
machine: pc-i440fx-6.0
memory: 8192
name: Windows10UT
net0: e1000=26:EF:FC:4E:F2:A6,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=26a6a238-af41-4491-99ca-169b85e0c3fe
sockets: 1
vmgenid: 927f05d8-f190-4319-85b2-af83da9f2295

Third Question : cat /etc/pve/storage.cfg

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

zfspool: local-zfs
pool rpool/data
content images,rootdir
sparse 1

lvm: FastSSD
vgname FastSSD
content rootdir,images
nodes pve
shared 0

lvm: Data4To
vgname Data4To
content rootdir,images
nodes pve
shared 0

dir: HDD250
path /mnt/pve/HDD250
content images,snippets,backup,vztmpl,iso,rootdir
is_mountpoint 1
nodes pve

cifs: ProxmoxShare
path /mnt/pve/ProxmoxShare
server 192.168.2.140
share Data
content images,snippets,iso,backup,vztmpl,rootdir
prune-backups keep-all=1
username Proxmox

cifs: Backup
path /mnt/pve/Backup
server 192.168.2.140
share Data
content snippets,backup,iso,vztmpl,rootdir,images
prune-backups keep-all=1
username Proxmox

Hope you find answer.
Thank you for your time.

Regent

 

[fiona]

Hi,
could you try this workaround? We are still investigating the root cause, but it seems to be some bad low-level LVM/io_uring interaction.

 

[Fullreg]

Ok It work's with this modif on conf file. Thank's again.

 

[JoeriVD]

can also confirm that the workaround seems to do the job...Backup is running atm, albeit very slow.

 

[Fullreg]

The workaround doing well, and i think the speed was good. look like as before. Thank's