On Tue, Jul 19, 2022 at 12:50 AM Patrick Hemmer
wrote:
> Just to close this out, and not be "that guy" (https://xkcd.com/979/), I
> ended up just rolling the
kernel back to the Fedora 35 kernel (5.14.10).
> Without a good way to isolate where the problem is (between XFS & LVM), I
> really didn't
Just to close this out, and not be "that guy" (https://xkcd.com/979/), I ended
up just rolling the kernel back to the Fedora 35 kernel (5.14.10).
Without a good way to isolate where the problem is (between XFS & LVM), I
really didn't want to waste time tracking this down, and restoring my system
You might include a full dmesg/messages. This is the sort of error
you get when there is an underlying read failure/breakage on the
device that the data is actually on.
You get scsi errors/block errors first and then that shows up as
filesystem errors similar to these. This sounds like the under
On Mon, 2022-07-18 at 07:29 -0300, George N. White III wrote:
> Cables and connectors should also be considered. Try swapping cables
> and connections. "Contact enhancer" sometimes solves connection
> problems (now that cars are full of computers, you can buy
> contact enhancer at auto supply sto
On Mon, Jul 18, 2022 at 12:10 AM Patrick Hemmer
wrote:
> Ever since upgrading to Fedora 36, my root filesystem is getting corrupted
> every few hours. I maintain block level backups, and I have to restore
> every time this happens. xfs_repair can fix the filesystem, but the system
> is typically
Ever since upgrading to Fedora 36, my root filesystem is getting corrupted
every few hours. I maintain block level backups, and I have to restore every
time this happens. xfs_repair can fix the filesystem, but the system is
typically unusable as there's often over 10k files in lost+found.
I hav
