> When you clone a VM (lets say an appVM), you'll notice another private > volume is created and shows the same figures as the volume it > originates from. But looking at pool00 (the overall container for our > VM volumes), the Data% barely changes if at all.
I did see in Qubes Manager that some template-based VMs, sys-net, sys-firewall, and untrusted, have small sizes (< 100 MB) after I played around with them. I'm guessing that represents stuff that has accumulated in their private volumes. > The Linux storage options won't show a volume that grows from nothing > and has a size equal to the delta from the parent volume. That's just what I was (mistakenly) looking for, based on my experience with Hyper-V. > And that brings me to another point: On Btrfs if you have two related > files (.img volumes) but suspect they have diverged too much over > time, you can tell Btrfs to perform deduplication to find new > commonalities and reduce the overall space used. Btrfs looks interesting, but given I don't fully understand how Qubes 4 handles storage even in its vanilla configuration, I'd better get some more experience with it under my belt before I experiment with a non-default file system. Thank you again for your help! This has cleared things up and taught me some things. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/39f1776f-6b2a-4b36-9556-3619080ed42e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
