Suggestion to determine where al the space is being used. Go to the mount point of the filesystem n question, in this case, / Run the command du -s * | sort -n The directories/files with the largest usage will show up at the bottom of the list. If a directory, cd into that directory and run du -s * | sort again. Eventually you will find it.
Note that a file open for writing but not yet closed may not appear. A reboot may either make it visible or get rid of it. A good start if it is in /var/log is to blow away all the gzipped log files. Those have been archived and compressed by logwatch and should not affect anything. Per my above comment, deleting an open file will merely delete the directory entry, not the file. If you want to remove the space used by those, try "> filename". On Wednesday, October 18, 2023 at 3:05:08 AM UTC-5 Ton vanN wrote: > After removal of .1-files and .gz-files for checking reran df, showing > > Bestandssysteem 1K-blokken Gebruikt Beschikbaar Geb% Aangekoppeld op > /dev/root 30358348 28786676 287176 100% / > > devtmpfs 439400 0 439400 0% /dev > tmpfs 472680 0 472680 0% /dev/shm > tmpfs 472680 47796 424884 11% /run > > tmpfs 5120 4 5116 1% /run/lock > tmpfs 472680 0 472680 0% /sys/fs/cgroup > /dev/mmcblk0p1 258095 49395 208700 20% /boot > tmpfs 94536 4 94532 1% /run/user/1000 > > /dev/root at 100% occupancy does not seem healthy, and breeding new > problems ....... > > Op dinsdag 17 oktober 2023 om 22:15:54 UTC+2 schreef vince: > >> Just delete the big logs from /var/log and reboot - that's all you need >> to do. > > >> With you providing no data on which files in /var/log are the big ones, >> no we can't help you much. >> >> On Tuesday, October 17, 2023 at 1:13:19 PM UTC-7 Ton vanN wrote: >> >>> Was on wrong leg, assuming KBs ..... >>> Unpleasant surprise, which seems to lead to conclusion that this install >>> cannot be saved, but new start required. >>> What is best practical approach to make new, small configuration while >>> 'borrowing' from the old configuration the sdb-file and various conf-files? >>> Somewhere a description for that kind of clean-up/restart? >>> >>> Obviously keen to avoid the 'error' that lead to this 'saturated' >>> install: >>> any hint? >>> >>> Op dinsdag 17 oktober 2023 om 13:06:53 UTC+2 schreef Tom Keffer: >>> >>>> The "-m" option to du means that sizes are in *megabytes*. Your >>>> /var/log directory has 26 *gigabytes* in it. >>>> >>>> On Tue, Oct 17, 2023 at 2:12 AM Ton vanN <[email protected]> wrote: >>>> >>>>> Vince, >>>>> The results of the suggested checks. >>>>> >>>>> *raspberrypi9*:~ $ sudo du -sm /var/log >>>>> 25977 /var/log >>>>> *raspberrypi9:~ $ *sudo du -sm /tmp >>>>> 1 /tmp >>>>> *raspberrypi9:~ $* sudo du -sm /home/pi >>>>> 53 /home/pi >>>>> *raspberrypi9:~ $* sudo du -sm /var/tmp >>>>> 1 /var/tmp >>>>> >>>>> IMHO contents of checked files are minimal .... >>>>> Wondering why /dev/root full, with this Raspberry only running WeeWX >>>>> plus 2 auxiliary Python-scripts (sized 2KB and 1KB), serving periodic >>>>> upload of weewx.sdb to a remote, backup server >>>>> >>>>> Guessing/speculation: >>>>> might expansion of the file system (via raspi-config) have had some >>>>> effects? >>>>> Op maandag 16 oktober 2023 om 20:58:56 UTC+2 schreef vince: >>>>> >>>>>> Your / partition is full. You have 29G Size and 29G Used and 0 >>>>>> Available. >>>>>> >>>>>> *raspberrypi9:~ $* df -h >>>>>> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op >>>>>> /dev/root 29G 29G 0 100% / >>>>>> devtmpfs 430M 0 430M 0% /dev >>>>>> tmpfs 462M 0 462M 0% /dev/shm >>>>>> tmpfs 462M 47M 415M 11% /run >>>>>> tmpfs 5,0M 4,0K 5,0M 1% /run/lock >>>>>> tmpfs 462M 0 462M 0% /sys/fs/cgroup >>>>>> /dev/mmcblk0p1 253M 49M 204M 20% /boot >>>>>> tmpfs 93M 0 93M 0% /run/user/1000 >>>>>> >>>>>> Check your /var/log partition to see what its size is: >>>>>> >>>>>> sudo du -sm /var/log >>>>>> >>>>>> If it is not many GB, check your /home/pi and /tmp and /var/tmp >>>>>> directories the same way. >>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "weewx-user" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/80e35d3b-a3a2-4a42-ac38-19899dcf59f9n%40googlegroups.com.
