The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Things 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.
@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, pass
Code:
tail /var/log/messages
(or similar) and see what retardation is going on in real time.


Yes. rsyslog + systemd = resource exaustion because bad cert. Lmao.
Here's another example of systemd retardation:
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)
"better solution to sysvinit" :story:
 
Gentoo has a thread and a port for it right now in testing. Of course it's developed into the "muh right hwite anti vaxx retardation". How far the mighty have fallen.

One of the Romanian users is working on Xlibre too. He did also update tinyx and GTK2. I checked his github profile, he's a mathmatics major so it shouldn't be too bad right?
STEM to troon pipeline at work here folks
There are weebs in Romania. I met some of them and they were alright, not cringe. I think it is far from being as obnoxious as western weebs, since there is much more shaming on weird behaviour (and I was kind of a target because I liked rock music in middle school). And if I am not mistaken, drawn child pornography is illegal, but I don't know if it is enforced or not.
 
Last edited:
Thanks. So looks like the biggest offender is some kind of logging, with "systemd-jornald" and "rsyslogd"...

There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?

View attachment 7545259
(Pic is thumbnail. Censored SSD name after "jbd2" and other personal info further down.)
if its systemd you can just change the setting in /etc/systed/journald.conf

put
storeage=volatile

that will keep the logs in memory

also. obviously. actually take a look in the log and see what it's logging in case their is some other issue you need to take care of,
 
Anyone here compared XLibre to regular X yet? Hard to find any reports on it since most of the news is full of whining about the dev not marching in lockstep and Phoronix is full of people dicklicking RHE as usual.
I use KDE on my work laptop, and logged in to find that I had updated prior to leaving work and had unknowingly updated to a version of KDE that no longer supports X11. I figured it's as good a time as any to figure out the jump to Xlibre. Turned out all I had to do was install plasma-x11-session and kwin-x11, but now I'm learning to appreciate XFCE's cute mouse.

What gave it away I was in Wayland was none of my monitors were behaving. Every time my screen locked I would lose monitor positioning, scaling would jump to 150% for some reason. Getting Xlibre off the AUR was easy enough using the commands pinned on the AUR (have to use a bootstrap package first to avoid dependency loops), and after I figured out the missing packages for KDE it was exactly how I left it on Friday.

For reference I've got a Lenovo ThinkPad E16 with a Ryzen 7730U.

How would I even notice a difference? Is it just performance? Is an update to my Xorg server supposed to be noticeable without the desktop environment to do something like take advantage of new features?
 
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.
So if I disable "system-journald" and "rsyslogd", that shouldn't cause any major issues with the OS working?
 
I gave a second laptop to a relative and installed Cosmic Desktop. I had to use Arch because Alpine was doing some weird stuff with the wifii card, and I didn’t want to waste any more time troubleshooting it. I tested it out, and overall, it worked pretty well. One thing that really annoyed me, though, was that their file manager doesn’t support “Extract to” for 7z files. I had to use PCManFM instead. For someone like me, that’s not a big deal since I don’t typically use graphical file managers. But I can see how little things like that might frustrate normies who just want things to work. A lot of small stuff like that can prevent adoption.
 
  • Like
Reactions: oksurealright
So if I disable "system-journald" and "rsyslogd", that shouldn't cause any major issues with the OS working?
Journald and jbd2 are totally different things and unrelated.

The best solution is to check the logs and see why they're being written so much and fix the underlying problems, if any.
You can run "journalctl -b" to see all messages since last boot. You can check for large files in /var/log and /var/log/journal, if you find a large *.journal file you can use "journalctl --file FILENAME" to see what's in it and if something is going horribly wrong.

Amusingly, I have some large files in journal due to some containers I run which process PDFs and the log stores all the PDF data. This is unlikely to be your problem.
 
  • Informative
Reactions: ToroidalBoat
How would I even notice a difference? Is it just performance? Is an update to my Xorg server supposed to be noticeable without the desktop environment to do something like take advantage of new features?
You will notice that you are running XLibre if you are protected from deliberate malicious regressions plotted by Red Hat (IBM) to protect Microsoft.
 
The best solution is to check the logs and see why they're being written so much and fix the underlying problems, if any.
A recurring things I'm seeing is "gnome-system-monitor.desktop[2583]: glibtop(c=2583): [WARNING] statvfs '/run/user/1000/doc' failed: Operation not permitted" and stuff like "Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12)", but dunno if those are issues. For now I disabled the systemd journal thing.

BTW what's considered alarmingly huge? There's syslog.1 that's almost 10 MB, but I've been using this system for years.
 
Last edited:
What would be needed to install Xlibre on Linux Mint? Would the Linux Mint devs be forced to maintain it themselves if Debian and Ubuntu refuse to add it to their repositories?
 
So looks like the biggest offender is some kind of logging, with "systemd-jornald"
Sounds about right...
9yb7zj2.webp
Welcome to Linux!
:story:
(slight edit)
 
Last edited:
There's also "jbd2" doing some constant writing, though not as much. So what's this BS and how do I stop it?
jbd2 is the journaling part of ext4. You can disable this with:

Code:
sudo mke2fs -t ext4 -O ^has_journal /dev/drivename

But this will make the drive less resilient to corruption.

I also considered something that's probably causing some writes, if you're really trying to decrease writes: mount the drive with the "noatime" flag. "atime" records every time the file is accessed.
 
What would be needed to install Xlibre on Linux Mint? Would the Linux Mint devs be forced to maintain it themselves if Debian and Ubuntu refuse to add it to their repositories?
If you know how to compile a package it shouldn't be too difficult to start using it right now, but if you don't already know how to compile an application I would advise against trying to use XLibre at this early stage of development. It will take relatively no effort for Mint or any other distro to make their own XLibre package whenever they want to do that, they are not reliant on Ubuntu or Debian for this at all, although Debian will probably adopt XLibre eventually.
 
Just had to install a Win10 VM and icue to disable my corsair keyboard rgb after it reset itself. I tried openrgb and ckb-next, but neither recognized my K70. If anyone knows something I might have missed I'd appreciate it in case I have to do this again
 
Back