Hello,
i#m actually cloning (offline copy) a VM with 125GB RAM (yeah, really, a HANA setup) and three 300GB zvol-volumes from a (ZVOL-SSD to a ZVOL-HDD).
After 8h running, not even one zvol got copied.
When i look into iotop, i see that there are some qemu-img convert running, each with a write speed BELOW 1MB/s.
The overall write activity is about 5MB/s.
I mean, is this a bad joke? Is this a expected behavior? I wondered already about the slow speed of snapshots (on HyperV nearly instantly, in Proxmox it takes time and time ....) but this makes the system nearly unusable.
How to address this problem? And how to stop the running clone process?
Also a look into ps shows me this
i#m actually cloning (offline copy) a VM with 125GB RAM (yeah, really, a HANA setup) and three 300GB zvol-volumes from a (ZVOL-SSD to a ZVOL-HDD).
After 8h running, not even one zvol got copied.
When i look into iotop, i see that there are some qemu-img convert running, each with a write speed BELOW 1MB/s.
The overall write activity is about 5MB/s.
I mean, is this a bad joke? Is this a expected behavior? I wondered already about the slow speed of snapshots (on HyperV nearly instantly, in Proxmox it takes time and time ....) but this makes the system nearly unusable.
How to address this problem? And how to stop the running clone process?
Also a look into ps shows me this
But this is the wrong target zvol. It should copy from vm-101-disk-2 to vm-102-disk-2 and not to vm-102-disk-1. Right?/usr/bin/qemu-img convert -p -n -t none -T none -f raw -O raw /dev/zvol/ZFS-SSD/vm-101-disk-2 zeroinit:/dev/zvol/ZFS-HDD/vm-102-disk-1