PVE Storage Issue

[lalakers]

Hello everyone, I am a beginner just starting to use Proxmox VE (PVE).
I've encountered a small issue with my PVE setup and am looking for guidance from experienced PVE users.
Currently, I have an OpenWrt virtual machine and an Ubuntu LXC container in my PVE environment. In the LXC container's downloader, I've set up unfinished files to be stored on the LXC container's disk and moved to an NFS-mounted local network storage drive upon completion (essentially using the LXC container as a cache drive).
However, the problem is that after the downloads and transfers are complete, the space in the LXC container is freed up, but there is still some usage in the PVE local storage (specifically, I've downloaded a total of 240GB, but now it shows 130GB as used). Is this some kind of cache-related issue? P.S. I have already removed the local-lvm, allocating all space to the local storage. The total PVE storage is 1TB of NVMe.
Thank you for your time

 

[leesteken]

Not all types of storage support thin provisioning. The local-lvm probably supported snapshots and therefore trimming. The local storage is a directory storage which does not support trimming unless you use the qcow2 format. I hope the links to the manual begin to answer your question.

 

[lalakers]

Not all types of storage support thin provisioning. The local-lvm probably supported snapshots and therefore trimming. The local storage is a directory storage which does not support trimming unless you use the qcow2 format. I hope the links to the manual begin to answer your question.

Thank you for your reply. I have checked, and only virtual machines (VMs) can use the qcow2 format. My current LXC container cannot use it and is limited to using the raw format. So, can I understand it this way: there is no solution to this issue under LXC? Additionally, when the local (PVE) storage disk (which is initially installed under /var/lib/vz) is fully used, will it become impossible to continue writing data to it?
Thanks again

 

[leesteken]

Thank you for your reply. I have checked, and only virtual machines (VMs) can use the qcow2 format. My current LXC container cannot use it and is limited to using the raw format. So, can I understand it this way: there is no solution to this issue under LXC?

Use a storage type that supports snapshot and trim, like LVM-thin (which you removed) or BTRFS or ZFS, and move the (virtual disks of the) containers to that storage.

Additionally, when the local (PVE) storage disk (which is initially installed under /var/lib/vz) is fully used, will it become impossible to continue writing data to it?

Yes, but I think each container should not use more than the size you set for their virtual disk(s).

 

[lalakers]

Use a storage type that supports snapshot and trim, like LVM-thin (which you removed) or BTRFS or ZFS, and move the (virtual disks of the) containers to that storage.

Yes, but I think each container should not use more than the size you set for their virtual disk(s).

Thank you very much! I'll try it
However, the reason I initially removed the local-lvm storage space was that I encountered this issue when I had installed the LXC container on the local-lvm.