Backup size vs bootsize?

swanemar

New Member
Oct 21, 2024
4
3
3
I've tried searching but didn't really find a great reply.

I have an lxc with a 60GB rootfs mount, however the backup -> Size tells me the size is a whopping 3.45TB(!) and I cannot for the life of me understand why/how. I noticed that it takes forever for the backup to run, hence why I found this massive size from the getgo.

pct config:
Code:
root@swanemar:~# pct config 105
arch: amd64
cores: 2
features: nesting=1
hostname: docker
lock: backup
memory: 3072
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:XX:XX:XX:XX,ip=dhcp,type=veth
onboot: 1
ostype: debian
parent: vzdump
rootfs: local-lvm:vm-105-disk-0,size=60G,mountoptions=discard
swap: 512
tags: 192.168.X.XXX
lxc.cgroup2.devices.allow: a
lxc.cap.drop:
lxc.cgroup2.devices.allow: c 188:* rwm
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/serial/by-id  dev/serial/by-id  none bind,optional,create=dir
lxc.mount.entry: /dev/ttyUSB0       dev/ttyUSB0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyUSB1       dev/ttyUSB1       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM0       dev/ttyACM0       none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM1       dev/ttyACM1       none bind,optional,create=file

df -h:
Code:
root@docker:~# df -h
Filesystem                        Size  Used Avail Use% Mounted on
/dev/mapper/pve-vm--105--disk--0   59G   42G   15G  75% /
none                              492K  4.0K  488K   1% /dev
udev                              6.7G     0  6.7G   0% /dev/ttyACM0
tmpfs                             7.6G     0  7.6G   0% /dev/shm
tmpfs                             3.1G  436K  3.1G   1% /run
tmpfs                             5.0M     0  5.0M   0% /run/lock
overlay                            59G   42G   15G  75% /var/lib/docker/overlay2/55a00e59207ca7c29f8a514bb3540a35fc6f3a97f6ac043c3ad829b8c460aadc/merged
overlay                            59G   42G   15G  75% /var/lib/docker/overlay2/7e0b13cf19f33d57d7d7f1b2e099b66662155b6d8bcd3f9cbdcf7f8bd6949700/merged
overlay                            59G   42G   15G  75% /var/lib/docker/overlay2/8222df364741d237062e230f6b5ac8fd82c984b9b8edbc252356de4844e78239/merged
overlay                            59G   42G   15G  75% /var/lib/docker/overlay2/34dfeb466eb2f5311fdfb3b18058c9c37508e5e8404b1e1ec0379bee6bff1aa5/merged

LXC->Backup:
1788418572372.png

Tried running a manual backup job and now (5 minutes in) i'm at processed 0.5TB or so and counting. How can this be?

Help a confused (semi) newbie please.

Oh, and this container runs docker with mealie + calibre (that's it)

Brs
 
Update:

Found it. It was core files dumped from a crash which I had not caught. They totaled ~3.4TB but didn't end up in df when checking. Removed these and I'm good to go.

Code:
pct exec 105 -- find / -xdev -type f -size +500M -printf '%s\t%p\n' 2>/dev/null | sort -rn | head -20
1134004129792   /root/docker/calibre/config/core.1562272
....
....