RPI_V4.1.0-RC7 - Disk full
Posted: Fri Jan 03, 2020 8:31 pm
Hello,
I am having an interesting problem that I have no idea where to correct. I loaded 4.1.0-RC7 on a PI3B+ and the hotspot stops running after several hours. I found that the looking at DMESG that it failed to open the runtime journal as noted from the log entries below. doing a DF on the cmdline it looks like /run is at 100% full, and I have seen also that /var/log is 100%. I thought that I might have a bad image or something, but I reloaded with new SD card and it seems to still be happening. apart from the log messages below, and a DF that shows /run and sometimes /var/log full I am at a loss as to where to look for further details about what is going on. I have searched the forum with not a lot of information found. Is this a bug in RC7 or is this something that on my side is causing the problem. as a side note, I was previously running 4.0 version and didn't see this problem, hotspot ran for weeks with no trouble.
anyone else seeing this type behavior?
Thanks,
Sam N4ZWR
**DF **
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 15213412 1528340 13031388 11% /
devtmpfs 367684 0 367684 0% /dev
tmpfs 499268 0 499268 0% /dev/shm
tmpfs 32768 32768 0 100% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 32768 0 32768 0% /sys/fs/cgroup
tmpfs 16 0 16 0% /var/lib/logrotate
tmpfs 16 0 16 0% /var/lib/sudo
tmpfs 32 16 16 50% /var/lib/dhcpcd5
tmpfs 1024 72 952 8% /var/cache/samba
tmpfs 65536 11952 53584 19% /var/log
tmpfs 64 0 64 0% /var/lib/php/sessions
tmpfs 65536 4 65532 1% /tmp
tmpfs 1024 0 1024 0% /var/lib/nginx/body
tmpfs 4096 2176 1920 54% /var/lib/samba/private
/dev/mmcblk0p1 64456 54416 10040 85% /boot
**DMESG Excert**
[Fri Jan 3 13:50:13 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 14:17:02 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 14:17:02 2020] systemd-journald[102]: Received request to rotate journal from PID 1
[Fri Jan 3 14:17:02 2020] systemd-journald[102]: Vacuuming done, freed 0B of archived journals from /run/log/journal/18634e1404184594bc66ddacfba0bf43.
[Fri Jan 3 14:17:02 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to create new runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open user journal directory '/var/log/journal/18634e1404184594bc66ddacfba0bf43/': No such file or directory
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
I am having an interesting problem that I have no idea where to correct. I loaded 4.1.0-RC7 on a PI3B+ and the hotspot stops running after several hours. I found that the looking at DMESG that it failed to open the runtime journal as noted from the log entries below. doing a DF on the cmdline it looks like /run is at 100% full, and I have seen also that /var/log is 100%. I thought that I might have a bad image or something, but I reloaded with new SD card and it seems to still be happening. apart from the log messages below, and a DF that shows /run and sometimes /var/log full I am at a loss as to where to look for further details about what is going on. I have searched the forum with not a lot of information found. Is this a bug in RC7 or is this something that on my side is causing the problem. as a side note, I was previously running 4.0 version and didn't see this problem, hotspot ran for weeks with no trouble.
anyone else seeing this type behavior?
Thanks,
Sam N4ZWR
**DF **
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 15213412 1528340 13031388 11% /
devtmpfs 367684 0 367684 0% /dev
tmpfs 499268 0 499268 0% /dev/shm
tmpfs 32768 32768 0 100% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 32768 0 32768 0% /sys/fs/cgroup
tmpfs 16 0 16 0% /var/lib/logrotate
tmpfs 16 0 16 0% /var/lib/sudo
tmpfs 32 16 16 50% /var/lib/dhcpcd5
tmpfs 1024 72 952 8% /var/cache/samba
tmpfs 65536 11952 53584 19% /var/log
tmpfs 64 0 64 0% /var/lib/php/sessions
tmpfs 65536 4 65532 1% /tmp
tmpfs 1024 0 1024 0% /var/lib/nginx/body
tmpfs 4096 2176 1920 54% /var/lib/samba/private
/dev/mmcblk0p1 64456 54416 10040 85% /boot
**DMESG Excert**
[Fri Jan 3 13:50:13 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 14:17:02 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 14:17:02 2020] systemd-journald[102]: Received request to rotate journal from PID 1
[Fri Jan 3 14:17:02 2020] systemd-journald[102]: Vacuuming done, freed 0B of archived journals from /run/log/journal/18634e1404184594bc66ddacfba0bf43.
[Fri Jan 3 14:17:02 2020] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to create new runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open user journal directory '/var/log/journal/18634e1404184594bc66ddacfba0bf43/': No such file or directory
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: File /run/log/journal/18634e1404184594bc66ddacfba0bf43/system.journal corrupted or uncleanly shut down, renaming and replacing.
[Fri Jan 3 15:11:17 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device
[Fri Jan 3 15:11:22 2020] systemd-journald[102]: Failed to open runtime journal: No space left on device