Possible lack of validation during pct move-volume

[kmonti]

It's possible to move when source and destination storage are the same - is that intended?

root@pve:~# pct config 126|grep root
rootfs: local-lvm:vm-126-disk-0,size=2G
root@pve:~# pct stop 126; pct move-volume 126 rootfs local-lvm --delete
  Logical volume "vm-126-disk-1" created.
Creating filesystem with 524288 4k blocks and 131072 inodes
Filesystem UUID: 0ac2449b-7af6-4fdb-a705-13fb367d91be
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912

 

[leesteken]

This might be useful when a storage supports both sparse and non-sparse virtual disks and you want to switch (which only affects newly created virtual disks).

 

[fabian]

in fact we also plan to lift the limitation in move_disk for VMs, where you currently need to either change format or change storage, but can't use it to "reinitialize" a disk