After transplanting a whonix app qube from Qubes 4.1 to 4.2, disk usage for the private volume vm-qubename-private, as reported by “sudo lvs” or Qubes Disk Space Monitor in dom0, seems to be growing faster than disk is being used within the /rw mount point within the vm, as reported by Use% from “df /rw” within the VM.
“sudo lvs” within dom0 shows 90.99% for Data% for vm-qubename-private
“df /rw” run within qube shows 62% for Use%
Since transplanting I have resized the volume via the “Private storage max size” setting in Qube Manager multiple times but each time it’s not long before Qubes Disk Space Monitor starts showing warnings that this qube is running out of space.
Any ideas on an explanation for what appears to me to be a discrepancy in the disk usage as reported by LVM Tools in dom0 vs “df” in the app qube itself?
No, after running bash sudo fstrim /rw and shutting down and starting the qube back up, nothing has changed with respect to my aforementioned usage percentages.
No, after running sudo fstrim /rw and shutting down and starting the qube back up, nothing has changed with respect to my aforementioned usage percentages.
I am having the same problem, but with a qube generated during my 4.2 install (so it has not been created in a previous version). It has a default size of 2 Gb. When I see the usage inside the VM (for /rw) I see that 36% of the device is used. But according to lvs in dom0, the logical volume is 96% full.
I tried the “fstrim /rw” command, and it did not change anything.
I do not really understand where all that used space is. Is there a command to “optimize” a logical volume and release all the space not really occupied in the file system?