As almost anything in Linux is a file or folder, if a disk runs full, you can run into issues with establishing new network connections which in a sense is also a file.
Why not create some room first by deleting some and try the Teleporter export again after.
You can safely delete any of the archived .gz
log files from Pi-hole to free up some space:
pi@ph5b:~ $ ls -lh /var/log/pihole*.gz
-rw-r--r-- 1 pihole pihole 152 May 9 00:00 /var/log/pihole-FTL.log.2.gz
-rw-r--r-- 1 pihole pihole 239 May 8 00:00 /var/log/pihole-FTL.log.3.gz
-rw-r--r-- 1 pihole pihole 28K May 9 00:00 /var/log/pihole.log.2.gz
-rw-r--r-- 1 pihole pihole 76K May 8 00:00 /var/log/pihole.log.3.gz
-rw-r--r-- 1 pihole pihole 62K May 7 00:00 /var/log/pihole.log.4.gz
Most of that data is stored in the /etc/pihole/pihole-FTL.db
dbase file anyway.
And you can use the df -h
command instead of pihole -c
to figure out disk space.
And if want to know where most of the disk space has gone: