| ▲ | b5n 2 hours ago | |||||||
This supports my initial reply. This was an f2fs bug in a bleeding edge kernel released only seven days earlier. The thread suggests perfectly reasonable mitigations, especially for an arch user: use the lts kernel or downgrade to 6.8.9. If you're not familiar with linux and/or don't want to deal with trivial issues periodically, don't hang out at the bleeding edge. There are plenty of boring and/or beginner friendly choices out there. I'm not saying linux is perfect, but your conclusions in this instance appear to be uninformed rather than supported by the facts. | ||||||||
| ▲ | 1970-01-01 2 hours ago | parent [-] | |||||||
Ok fair point, here's plenty more of the same on stable. My point is Linux is always fine right until it isn't. Then you're back to a day of debugging your update. https://bugzilla.kernel.org/show_bug.cgi?id=218770 https://lore.kernel.org/linux-f2fs-devel/20240409203411.1885... https://lkml.iu.edu/hypermail/linux/kernel/2511.2/07280.html https://lkml.iu.edu/hypermail/linux/kernel/2511.2/07260.html https://bugzilla.suse.com/show_bug.cgi?id=1226043 https://lists.opensuse.org/archives/list/bugs@lists.opensuse... https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/15478... | ||||||||
| ||||||||