The backup size is displayed as 391 GB, but the lxc size is 20 GB

[al.semenenko88]

Actual container size 20 GB, but its backup 391 GB.
391 GB it is displayed in the web interface, but much less backup is used on the disk.


Proxmox VE:



Config lxc:


Proxmox BS:


Partition size for backups (used 93 GB). There is not 1 backup, but more:

 

[dcsapak]

mhm there are probably big sparse files inside the container. this looks to the backup like zeroes and deduplicates, so it does not take up the whole space

 

[al.semenenko88]

mhm there are probably big sparse files inside the container. this looks to the backup like zeroes and deduplicates, so it does not take up the whole space

The container was placed from a template.
Tell me, how you can find a big sparse file using Linux utilities.

 

[dcsapak]

Tell me, how you can find a big sparse file using Linux utilities.

e.g. this site has some answers to this: https://unix.stackexchange.com/questions/86442/finding-sparse-files

 

[al.semenenko88]

e.g. this site has some answers to this: https://unix.stackexchange.com/questions/86442/finding-sparse-files

Thanks, understood!

# du -sh /var/log/lastlog
553K    /var/log/lastlog
# ls -lh /var/log/lastlog
-rw-rw-r-- 1 root utmp 387G May 11  2018 /var/log/lastlog

 

[al.semenenko88]

mhm there are probably big sparse files inside the container. this looks to the backup like zeroes and deduplicates, so it does not take up the whole space

If the container is in the domain AD, then the lastlog is very large and the archive looks large.
If you can fix the problem with sparse files, great!