L limone Well-Known Member Aug 1, 2017 89 9 48 30 Oct 16, 2017 #21 Code: root@limone:~# pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 311.75g 15.79g Code: root@limone:~# vgs VG #PV #LV #SN Attr VSize VFree pve 1 16 0 wz--n- 311.75g 15.79g
Code: root@limone:~# pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 311.75g 15.79g Code: root@limone:~# vgs VG #PV #LV #SN Attr VSize VFree pve 1 16 0 wz--n- 311.75g 15.79g
L limone Well-Known Member Aug 1, 2017 89 9 48 30 Oct 16, 2017 #22 Ok I now did Code: pct mount $vmid and Code: fstrim /var/lib/lxc/$vmid/rootfs for every single vm and i got my disk space back is there any way to do this automatically? did this happen because the containers are unprivileged? edit: ok no the container which freed like 50GB is privileged Last edited: Nov 4, 2017
Ok I now did Code: pct mount $vmid and Code: fstrim /var/lib/lxc/$vmid/rootfs for every single vm and i got my disk space back is there any way to do this automatically? did this happen because the containers are unprivileged? edit: ok no the container which freed like 50GB is privileged
dcsapak Proxmox Staff Member Staff member Feb 1, 2016 10,252 1,535 273 36 Vienna Oct 16, 2017 #23 so maybe your thin-pool was partially corrupted and the mount/unmount has triggered some ext cleanup code? this is the only thing which comes to mind for this behaviour
so maybe your thin-pool was partially corrupted and the mount/unmount has triggered some ext cleanup code? this is the only thing which comes to mind for this behaviour
L limone Well-Known Member Aug 1, 2017 89 9 48 30 Oct 16, 2017 #24 I think I'll just use esxi and get away from containers Last edited: Oct 16, 2017