Have run 3 variants of df with following results. *raspberrypi9:~ $* df Bestandssysteem 1K-blokken Gebruikt Beschikbaar Geb% Aangekoppeld op /dev/root 30358348 30341964 0 100% / devtmpfs 439400 0 439400 0% /dev tmpfs 472680 0 472680 0% /dev/shm tmpfs 472680 47740 424940 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 0 94536 0% /run/user/1000 *raspberrypi9:~ $* df -i Bestandssysteem I-nodes IGebr IVrij IGeb% Aangekoppeld op /dev/root 1899328 116283 1783045 7% / devtmpfs 109850 379 109471 1% /dev tmpfs 118170 1 118169 1% /dev/shm tmpfs 118170 523 117647 1% /run tmpfs 118170 3 118167 1% /run/lock tmpfs 118170 15 118155 1% /sys/fs/cgroup /dev/mmcblk0p1 0 0 0 - /boot tmpfs 118170 13 118157 1% /run/user/1000 *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 *raspberrypi9:~ $*
Op maandag 16 oktober 2023 om 09:05:07 UTC+2 schreef Ton vanN: > Question of Vince triggers other observation. > Subject Raspberry should have a RAM-fs, but when viewing the folders, > don’t find /var/tmp and it’s subfolders. > Sign for corruption? > > Op maandag 16 oktober 2023 om 00:58:30 UTC+2 schreef Greg from Oz: > >> What does df -i show? >> You could have run out of inodes. >> >> On Monday, 16 October 2023 at 07:58:31 UTC+11 vince wrote: >> >>> Lets see the output of "df -h" because it sure sounds like /var or /tmp >>> is full... >>> >>> On Sunday, October 15, 2023 at 11:45:51 AM UTC-7 Ton vanN wrote: >>> >>>> Since WeeWX4.4 available have been using it without much problems >>>> running on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded >>>> through Raspi-Config. >>>> Setup of WeeWX to (re)start when (re)booting. >>>> Occasionally stopping, but either by restart through PuttySSH, or (as >>>> last resort) by an 'emergency' hard reset, was always able to restart. >>>> Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart >>>> It still happily reports: [ ok ] Restarting weewx (via systemctl): >>>> weewx.service >>>> >>>> However, this weekend such simple measures did not help, and database >>>> and many files stuck/frozen at 14-10-23 10:15:00, while last >>>> FTP-upload at 14-1023 22:17:36, but related files all 0kb. Date&Time of >>>> that FTP-upload also valid for all external uploads coming from WeeWX. >>>> >>>> Fresh reinstall&setup (using copies of latest sdb-file etc.) obviously >>>> a pragmatic remedy, >>>> but would shorter route be available to revive this existing >>>> configuration? >>>> >>>> Observed 2nd effect: cannot access crontab, getting report that no >>>> space left on device. >>>> But df shows plenty of space >>>> >>> -- 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/74559913-90b4-4fab-b6ba-cf2e4757fa15n%40googlegroups.com.
