If you’re using the standard install LVM partitioning, then these responses/threads may be helpful in answering that question:
Yes, I would say 79% usage for the metadata volume is very concerning/risky. The basic issue here is that metadata use can fluctuate much quicker than data use when complex operations are causing fragmentation, even if only momentarily. Therefore, I stopped following my data use % as an indicator and got better results by keeping metadata use well below 50%. You can do this with lvextend --poolmetadatasize <size> qubes_dom0/vm-pool. In your case I would at least double the current size. You…
Yes, restore would also need that option… if you need automated/scripted operation. If you prefer, an env variable can be set with the passphrase and then echo the var (instead of a tmp file).
Only restore has this restriction (it will even stop the VMs you are restoring). With backup, it uses the Qubes snapshot the system took when you last started/stopped that VM. So if the VMs is running during backup it won’t see changes you made since you started the VM, but otherwise there is no confli…
Exactly.
behemothwerecat:
Is there any concievable way that running either of the two tools from dom0 could break the Qubes OS installation? (If the dest is always in an App qube and not local to dom0, as described above, so it’s not adding space to the dom0 filesystem)
It can cause issues only insofar as the metadata and snapshot space is concerned (hence the recommendation for lvextend), but nothing irreversible. So the simple answer to this question is “no.”
There is one here (though note this is for BTRFS install, though that makes little difference in the use of the tool other than pool storage locations), in Part 3:
Salt seemed daunting to me at first. It took some effort to learn but it was worth it! I’m writing this guide for beginners who enjoy an hands-on introduction with examples.
GitHub link ). In this file we can read:
qubes.user-dirs
Install and maintain …
1 Like