May 13, 2019 2:48 AM, "Chris Laprise" wrote:
> This is thin lvm's Achilles heel. In Qubes' case there is no un-allocated
> space in the volume group
> (the installer created the pool to occupy all the remaining space) so you
> can't simply enlarge the
> metadata size.
>
> What you can do (some
This is thin lvm's Achilles heel. In Qubes' case there is no
un-allocated space in the volume group (the installer created the pool
to occupy all the remaining space) so you can't simply enlarge the
metadata size.
What you can do (something I've done myself) is to take advantage of the
unnece
--- Logical volume ---
Internal LV Name lvol0_pmspare
VG Namequb
LV UUIDJ8VXWl-UoWw-C6bU-mcPC-C6Fa-7SK1-s3aybZ
LV Write Accessread/write
LV Creation host, time localhost.localdomain, 2018-04-26 14:35:24 +0200
LV Status NOT avail
May 12, 2019 10:05 AM, m...@disroot.org wrote:
>> Backup your full system first. You can then try running sudo fstrim -av in
>> dom0 and your VMs, and
>> deleting unused ones.
No matter how much space I free up by deleting VMs I can't extend the
metadata. Volumes are
completely full.
I have
m...@disroot.org:
`Domain disp6345 has failed to start: WARNING: Remaining free space in metadata of
thin pool qub/pool00 is too low (94.73%% >= 94.44%%). Resize is recommended.
Cannot create new thin volume, free space in thin pool qub/pool00 reached
threshold.`
If I try to extend the metada
`Domain disp6345 has failed to start: WARNING: Remaining free space in metadata
of thin pool qub/pool00 is too low (94.73%% >= 94.44%%). Resize is recommended.
Cannot create new thin volume, free space in thin pool qub/pool00 reached
threshold.`
If I try to extend the metadata it says:
`sudo lv
