clone to smb share

[DieselDriver]

Hi,

the backup of a VM via Proxmox Backup server works fine.
When I try to clone a VM to a SMB share, I have some problems.

When I do it as vmdk, it works.

create full clone of drive scsi0 (volume1:vm-100-disk-0)
Formatting '/mnt/pve/smb/images/104/vm-104-disk-0.vmdk', fmt=vmdk size=32212254720 compat6=off hwversion=undefined
drive mirror is starting for drive-scsi0
drive-scsi0: transferred 0.0 B of 30.0 GiB (0.00%) in 0s
drive-scsi0: transferred 7.0 MiB of 30.0 GiB (0.02%) in 1s
drive-scsi0: transferred 14.0 MiB of 30.0 GiB (0.05%) in 2s
drive-scsi0: transferred 21.0 MiB of 30.0 GiB (0.07%) in 3s
drive-scsi0: transferred 29.0 MiB of 30.0 GiB (0.09%) in 4s
drive-scsi0: transferred 36.0 MiB of 30.0 GiB (0.12%) in 5s
drive-scsi0: transferred 43.0 MiB of 30.0 GiB (0.14%) in 6s

When I do it with qemu, I always get following error.

create full clone of drive scsi0 (volume1:vm-100-disk-0)
Formatting '/mnt/pve/smb/images/104/vm-104-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=full compression_type=zlib size=32212254720 lazy_refcounts=off refcount_bits=16
TASK ERROR: clone failed: unable to create image: 'storage-smb'-locked command timed out - aborting

Does anybody knows why it does not work (I also tried to change the preallocation mode from default to disabled or full)?
Thanks.

 

[fiona]

Hi,

Hi,

the backup of a VM via Proxmox Backup server works fine.
When I try to clone a VM to a SMB share, I have some problems.

When I do it as vmdk, it works.

create full clone of drive scsi0 (volume1:vm-100-disk-0)
Formatting '/mnt/pve/smb/images/104/vm-104-disk-0.vmdk', fmt=vmdk size=32212254720 compat6=off hwversion=undefined
drive mirror is starting for drive-scsi0
drive-scsi0: transferred 0.0 B of 30.0 GiB (0.00%) in 0s
drive-scsi0: transferred 7.0 MiB of 30.0 GiB (0.02%) in 1s
drive-scsi0: transferred 14.0 MiB of 30.0 GiB (0.05%) in 2s
drive-scsi0: transferred 21.0 MiB of 30.0 GiB (0.07%) in 3s
drive-scsi0: transferred 29.0 MiB of 30.0 GiB (0.09%) in 4s
drive-scsi0: transferred 36.0 MiB of 30.0 GiB (0.12%) in 5s
drive-scsi0: transferred 43.0 MiB of 30.0 GiB (0.14%) in 6s

the speed is very low, only 7 MiB/s...

When I do it with qemu, I always get following error.

create full clone of drive scsi0 (volume1:vm-100-disk-0)
Formatting '/mnt/pve/smb/images/104/vm-104-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=full compression_type=zlib size=32212254720 lazy_refcounts=off refcount_bits=16
TASK ERROR: clone failed: unable to create image: 'storage-smb'-locked command timed out - aborting

...which likely is the reason that the image cannot be created within 60 seconds here. That is the timeout for cluster-wide locking and is hard-coded for technical reasons.

Does anybody knows why it does not work (I also tried to change the preallocation mode from default to disabled or full)?
Thanks.

Turning preallocation off should improve the situation, because no (meta)data needs to be allocated for the image. I'm a bit surprised it doesn't work then, that should be very fast. Speed-wise, qcow2 and preallocation off should be very similar to raw or vmdk with preallocation off. Using full means that all space for the image is reserved ahead of time which makes the situation much worse.

 

[bbgeek17]

I would pay particular attention to network speed - has any part of the communication chain negotiated to a 100mbit by accident? A bad cable/port could be a culprit. Check network statistics on each interface - are there errors logged?

Does "backup works fine" mean it completes but at the same low speeds? If so, then as @fiona mentioned the difference is the lock thats taken out during clone.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox