The issue I am facing:
Disk shortage (/etc/pihole/pihole-FTL.db) ahead: 99% used
/etc/pihole: 52.3GB used, 52.5GB total
Details about my system:
I run pihole as LXC Container on Proxmox.
Storage: 50GB
RAM: 2GB
OS: debian
SWAP: 512MB
What I have changed since installing Pi-hole:
after i installed pihole (native), i also installed unbound and pialert.
i let it run for about a week. then i found an error in Pi-hole diagnosis.
is pialert the reason to fill the storage so fast?
should i increase the ram size?
should i disable zram?
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
Also, there are no warnings about Disk Space on the debug log.
The Pi-hole diagnosis messages section is empty.
Where did you see this warning message? Pi-hole web interface, Pi-alert, system log, elsewhere?
Also, there are a lot of PHP errors, but none are related to Pi-hole:
...
2023-02-04 13:19:30: mod_fastcgi.c.487) FastCGI-stderr:PHP Notice: Undefined index: login in /root/pialert/front/devices.php on line 13
2023-02-04 13:19:31: mod_fastcgi.c.487) FastCGI-stderr:PHP Notice: Undefined index: login in /root/pialert/front/devices.php on line 13
2023-02-04 13:19:31: mod_fastcgi.c.487) FastCGI-stderr:PHP Notice: Undefined index: SubmitConfigFileEditor in /root/pialert/front/index.php on line 8
2023-02-04 13:19:31: mod_fastcgi.c.487) FastCGI-stderr:PHP Notice: Undefined index: action in /root/pialert/front/index.php on line 21
2023-02-04 13:19:31: mod_fastcgi.c.487) FastCGI-stderr:PHP Notice: Undefined variable: pia_lang_selected in /root/pialert/front/index.php on line 39
The warning is just saying Pi-hole noticed your disk is 92% used.
Pi-hole is not saying which files are too big.
It only identified the disk was 92% used when saving to the disk (In your case, pi-hole saved data to pihole-FTL.db and added text to FTL.log, checked the disk and warn about the disk shortage.).
Your debug log shows /dev/mapper/pve-vm--100--disk--0 is the one triggering the warning, but you will need to investigate which files are growing.