diff options
Diffstat (limited to 'results/classifier/gemma3:12b/files/1920211')
| -rw-r--r-- | results/classifier/gemma3:12b/files/1920211 | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/1920211 b/results/classifier/gemma3:12b/files/1920211 new file mode 100644 index 00000000..247dd585 --- /dev/null +++ b/results/classifier/gemma3:12b/files/1920211 @@ -0,0 +1,14 @@ + +shrink option for discard (for bad host-filesystems and -backup solutions) + +When using discard=unmap for virtio or scsi devices with QCOW2 images, space discarded by the guest will be unmaped on the host, which is basically great! + +This will turn the QCOW2 image into a sparse file which is efficient for most scenarios. But it may be that you need to avoid big sparse files on your host. For example because you need to use a backup solution which doesn't support sparse files well. Or maybe the QCOW2 image is on a filesystem mount which doesn't support sparse files at all. + +For those scenarios an alternative option for the discard setting (discard=shrink) would be great, so that the QCOW2 file itself gets shrunken again. +I'm not sure about how the initial growing* of QCOW2 images is implemented and if there are maybe limitations. But I hope it may be possible do the inverse and actually shrink (not sparse) an QCOW2 image with internally discarded blocks. + + +I'm using Qemu-5.2.0 and Linux >= 5.3 (host and guest). + +*If you use "qemu-img create -f qcow2 ..." withOUT the "preallocation" option. \ No newline at end of file |