WARNING: Thin volume qubes_dom0/img-Tails maps 8.00 GiB while the size is only 2.00 GiB.

[Ulrich Windl]

Hi!

While experimenting with an image that didn't do what I wanted to I
ended up with this LVM warning:
WARNING: Thin volume qubes_dom0/img-Tails maps 8.00 GiB while the size
is only 2.00 GiB.

How can I "heal" LVM?
[root@dom0 master]# lvdisplay qubes_dom0/img-Tails
--- Logical volume ---
LV Path /dev/qubes_dom0/img-Tails
LV Name img-Tails
VG Name qubes_dom0
LV UUID 4IwD50-xeKY-0PNs-FbB7-99aF-fGde-162Soq
LV Write Access read/write
LV Creation host, time dom0, 2020-02-13 21:32:40 +0100
LV Pool name pool00
WARNING: LV qubes_dom0/img-Tails maps 8.00 GiB while the size is only
2.00 GiB.
LV Status available
# open 0
LV Size 2.00 GiB
Mapped size 100.00%
Current LE 512
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:11

Ulrich

[unman]

You have a consistency problem - you should be able to fix it by using
lvresize to change the size of that volume to 8.0 GiB

[ludwig jaffe]

Hi,

*urgently* clean up the disks. If you get a full disk qubes is likely to crash since some

config files are not written properly. I experienced qubes rendered unusable while the disk

was full. So some config files which manage the VMs got corrupted, so I had to boot kali

to mount the disk images and to backup all my data and then to reinstall qubes,

because dom0 did not wanted to start any vm, and reported some python errors in line xyz.

So debug the scripts or just reinstall :-(

Maybe, there is a better way, to repair qubes, but I chose the archeological approach,

as the success was guaranteed beforehand.

feature request: backup all config files into 3 archives and rotate them, so one can simply

exchange a broken state with the state before, while loosing some changes to memory size, net vm

and so on, but the system stays stable

/feature request.

So never ever let qubes fill your disk(s) completely. Leave some room.

Cheers

Ludwig

[Qubes]

On 7/20/20 5:24 PM, ludwig jaffe wrote:
> So never ever let qubes fill your disk(s) completely. Leave some room.

That should not be a warning it should be common sense, and it is true
for any storage device whether that storage device is used by an OS or
for general storage.

[Ulrich Windl]

However the issue was *Not* that the pool was full:

$ sudo lvs

WARNING: Thin volume qubes_dom0/img-Tails maps 8.00 GiB while the
size is only 2.00 GiB.

LV VG Attr
LSize Pool Origin Data%
Meta% Move Log Cpy%Sync Convert
img-Tails qubes_dom0 Vwi-a-tz--
2.00g pool00 100.00


But I deleted it anyway.

Regards,
Ulrich