Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upTraditional (no LVM) disk setup means space does not get recouped from deletion of files from VMS #3963
Comments
andrewdavidwong
added
bug
C: other
labels
Jun 6, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
Jun 6, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
fosslinux commentedJun 6, 2018
Qubes OS version:
R4.0
Affected component(s):
any VM's
Steps to reproduce the behavior:
dd if=/dev/zero of=bigfile.img bs=1000000 count=10000)Expected behavior:
The size of the VM should be (sizeWithBigFile - sizeOfBigFile).
Actual behavior:
The file gets deleted but remains in the disk space of the VM.
General notes:
In Qubes R3.2 the file would get deleted upon an
fstrimoperation in the VM. Now, in Qubes 4.0, due to the use of LVM Thin by default,fstrimis no longer needed to make the VM usage smaller. If LVM thin is not used, then the VM will not get smaller. This is visible by runningduon the VM image.fstrimdoes not work either, see #3255 for more details.Related issues:
#3255