Yes. My advice is to remove what you don't need, then do an 'fstrim -a'.
The volume's virtual size will of course stay the same, but the
allocated size will reduce to only what is used by the template.
Controlling the virtual size of private volumes is more of an issue,
IMO, because they see a lot more varied use than root volumes and
space-hungry apps in many vms can result in a surprising amount of disk
usage. You can keep on top of this by viewing disk usage in Qube
Manager, and investigate a vm using an allocation grapher like filelight
or baobab.
OTOH, if you really need to reduce a volume's virtual size then its
possible by attaching a volume to a non-networked dispvm, running
'resize2fs' in the dispvm, then using 'qvm-volume resize --force
vm:volume size' in dom0.
--
Chris Laprise,
tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886