Update2:
I’ve finally found a confirmation for one of my suspicions.
One of the “culprits”, that leave me in this unfortunate situation, is this
command for creating the thin pool from the example in the Qubes docs:
“sudo lvcreate -T -n poolhd0 -l +100%FREE qubes”
Using 100% of the VG is discouraged from because of the exact situation I’m currently in.
The Arch Wiki explains this (as always) very well:
Create the thin pool LV, MyThinPool. This LV provides the blocks for storage.
# lvcreate --type thin-pool -n MyThinPool -l 95%FREE MyVolGroupThe thin pool is composed of two sub-volumes, the data LV and the metadata LV. This command creates both automatically. But the thin pool stops working if either fills completely, and LVM currently does not support the shrinking of either of these volumes. This is why the above command allows for 5% of extra space, in case you ever need to expand the data or metadata sub-volumes of the thin pool.
So, it seems, the only option I currently have, is to add an external drive, add it to the VG, and then expand tmeta…
Gonna report back, once I’ve tried this.
P.S.
I won’t change the example in the Qubes docs, since github doesn’t allow me to register an account (seems they have a problem with my FF privacy settings).
So, whoever has access to the docs, feel free to change the “faulty” command in my stead.