We are using LVM iSCSI datastores.
During instantiation of a template a clone operation of the template takes place since it’s persistent.
I have create an extra disk like:
DISK = [
FORMAT = "qcow2",
FS = "xfs",
SIZE = "614400",
TYPE = "fs" ]
This leads to the lvsize and dd alignment issues. Blocksize is set to 64KB by default and LVsize gets set to 600GiB (644GB). This will lead to an extra block writing past the LV boundary.
Found that we could set ZERO_LVM_ON_CREATE=“NO” on the datastore but that does not take effect. Blocksize could also be set but that would still cause issues since I have a need for different sizes.
Found the script:
/var/lib/one/remotes/tm/fs_lvm_ssh/mkimage.
Could potentially patch it there. But the script needs to attention regarding the blocksize. Skipping the last block could be a workaround but lead to half-a-block being non-zero:out.
But quick test comparing shred vs dd filling with zeros only dd seems faster. Could be that blocksize. Didn’t see if shred could be optimized in that sense but…