Why my think provisioned zfspool not allowing disk to be moved back as qcow2 (only raw)?

EngChiVi

Active Member
Sep 21, 2020
11
2
43
VM with disk on shared storage

1634597423995.png

trying to move it back to local storage within the cluster

1634597472769.png


Move disk to zfs pool, only option is 'raw' - anything I am missing? Thank you

1634597520752.png
 
If you use ZFS there is no need for qcow2 because ZFS already supports snapshots and is also a CoW Filesystem. "Raw" means using ZFS natively on block level and that is the only format that ZFS allows for blocklevel access.
If you really want to force PVE to use qcow2 you could mount a ZFS dataset and use that mountpoint as a "Directory" storage. Then you are accessing ZFS on file level and image files stored ontop of that can use "qcow2". But I really wouldn't recommend that.
 
Last edited:
  • Like
Reactions: EngChiVi
If you use ZFS there is no need for qcow2 because ZFS already supports snapshots and is also a CoW Filesystem. "Raw" means using ZFS natively on block level and that is the only format that ZFS allows for blocklevel access.
If you really want to force PVE to use qcow2 you could mount a ZFS dataset and use that mountpoint as a "Directory" storage. Then you are accessing ZFS on file level and qcow2 will work. But I really wouldn't recommend that.

Thank you . I dont want to force qcow2, just want to make sure I am not needlessly moving empty bits from drives that are mostly empty (backups, migrations, etc) .