Hello
Recently we moved a 30GB disk from storage 1 to storage 2. Format of the vm disk is qcow2. On the storage 1, when we do qemu-img info, we see following info
image: vm-149-disk-1.qcow2
file format: qcow2
virtual size: 30G (32212254720 bytes)
disk size: 27G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
The disk size is 27 GB instead of 30GB, but on storage 2, same disk shows the data as follows
image: vm-149-disk-1.qcow2
file format: qcow2
virtual size: 30G (32212254720 bytes)
disk size: 30G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
the disk size has become similar to virtual size and this issue is happening for any drive size and any format. Now when we run the qemu-img convert on storage 2 , we get the disk space back to 27G instead of 30G.
Can any one suggest how this issue can be resolved or is this a bug in the system.
Recently we moved a 30GB disk from storage 1 to storage 2. Format of the vm disk is qcow2. On the storage 1, when we do qemu-img info, we see following info
image: vm-149-disk-1.qcow2
file format: qcow2
virtual size: 30G (32212254720 bytes)
disk size: 27G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
The disk size is 27 GB instead of 30GB, but on storage 2, same disk shows the data as follows
image: vm-149-disk-1.qcow2
file format: qcow2
virtual size: 30G (32212254720 bytes)
disk size: 30G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
the disk size has become similar to virtual size and this issue is happening for any drive size and any format. Now when we run the qemu-img convert on storage 2 , we get the disk space back to 27G instead of 30G.
Can any one suggest how this issue can be resolved or is this a bug in the system.