today I lost quite some data because /tmp ran out of space and there was no indication in the ui to this
- Screenshot 2020-04-30 at 07.31.36.png (137.32 KiB) Viewed 4153 times
- Screenshot 2020-04-30 at 07.34.41.png (144.03 KiB) Viewed 4153 times
5404 -rw-r--r-- 1 root root 5533696 Apr 30 02:20 dbase
96 -rw-r--r-- 1 root root 98304 Apr 30 02:58 dbase-shm
40368 -rw-r--r-- 1 root root 41336832 Apr 30 07:32 dbase-wal
After reboot
-rw-r--r-- 1 root root 5533696 Apr 30 07:41 dbase
-rw-r--r-- 1 root root 32768 Apr 30 07:35 dbase-shm
-rw-r--r-- 1 root root 2163032 Apr 30 07:44 dbase-wal
and /tmp is at 38%
In the log I can see quite some error indicating that something ran out of space
Thu Apr 30 02:05:05 2020 daemon.warn dnsmasq-dhcp[1172]: no address range available for DHCP request via apcli0
Thu Apr 30 03:05:05 2020 daemon.warn dnsmasq-dhcp[1172]: no address range available for DHCP request via apcli0
Thu Apr 30 03:08:35 2020 daemon.warn dnsmasq-dhcp[1172]: no address range available for DHCP request via apcli0
Thu Apr 30 03:10:02 2020 daemon.err uhttpd[976]: sh: write error: No space left on device
Thu Apr 30 03:15:01 2020 daemon.err uhttpd[976]: sh: write error: No space left on device
Is there a way to prevent this ?
Bernd
PS: Not sure whether this is triggered by the same cause that makes my nano stop adding adding data to the db (viewtopic.php?p=32749#p32749)