pvs shows as full

[przemas]

After failed cloning of a vm I've noticed that sda3 shows as full.

root@test:~# pvs
  PV         VG  Fmt  Attr PSize    PFree 
  /dev/sda3  pve lvm2 a--  <930.98g <16.00g

root@test:~# fdisk -l


Disk /dev/sda: 931.48 GiB, 1000171331584 bytes, 1953459632 sectors
Disk model: LOGICAL VOLUME 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A27692B9-0DE1-44A2-AB6E-7DBDDD3C2DA3

Device       Start        End    Sectors  Size Type
/dev/sda1       34       2047       2014 1007K BIOS boot
/dev/sda2     2048    1050623    1048576  512M EFI System
/dev/sda3  1050624 1953459598 1952408975  931G Linux LVM


Disk /dev/mapper/pve-swap: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-vm--100--disk--0: 128 GiB, 137438953472 bytes, 268435456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 97FA4051-53D4-456E-B5E8-12CDABDF0BB6

Device                                     Start       End   Sectors   Size Type
/dev/mapper/pve-vm--100--disk--0-part1      2048    206847    204800   100M EFI System
/dev/mapper/pve-vm--100--disk--0-part2    206848    239615     32768    16M Microsoft reserved
/dev/mapper/pve-vm--100--disk--0-part3    239616 267128831 266889216 127.3G Microsoft basic data
/dev/mapper/pve-vm--100--disk--0-part4 267128832 268431359   1302528   636M Windows recovery environment


Disk /dev/mapper/pve-vm--100--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--100--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--disk--0: 120 GiB, 128849018880 bytes, 251658240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 664130F1-54C4-4234-8DCE-88DDB0C787D2

Device                                     Start       End   Sectors   Size Type
/dev/mapper/pve-vm--101--disk--0-part1      2048    206847    204800   100M EFI System
/dev/mapper/pve-vm--101--disk--0-part2    206848    239615     32768    16M Microsoft reserved
/dev/mapper/pve-vm--101--disk--0-part3    239616 250546742 250307127 119.4G Microsoft basic data
/dev/mapper/pve-vm--101--disk--0-part4 250548224 251654143   1105920   540M Windows recovery environment


Disk /dev/mapper/pve-vm--101--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--103--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

I'm probably missing something obvious (not the best day tbh) - any ideas what might be causing that, howto fix it?

 

[Matthias.]

That's just the lvm. What matters is the Used size in the thin pool.
With default naming it should be lvs pve/data