- Joined
- May 5, 2022
@ToroidalBoat You need to see what's causing the massive log writes. Systemd is doing something stupid per usual again would be my guess. Instead of supressing the error it's writing them all with all the errors in queue. If you can't tell from the log, passThings in [square brackets] are kernel threads doing work for the kernel. In this case jbd2 takes filesystem data from the filesystem journal onto the proper place on the disk and handles safe recovery in case of power off. Most kernel threads don't do anything on their own, lvm will take the writes to /dev/mapper and similar and send them to the proper /dev/sd* or /dev/nvm*, same for md and the [md#_raid#] threads.
Code:
tail /var/log/messages
Yes. rsyslog + systemd = resource exaustion because bad cert. Lmao.
Here's another example of systemd retardation:
"better solution to sysvinit"journald duplicate message ID bug causes rsyslog to peg CPU at 100% and spam /var/log/messages until hard disk is full (and breaks journalctl)
