Hi, I'm not sure if this is a rawhide update issue, or a problem with the hard drive (sata spinning) itself. But, after updates a few days ago, the file system (ext4) eventually hangs and is corrupted. I see a glibc update, but nothing else that looks suspicious, though I'm no expert on what might impact the file system. The reason I'm not sure it is the drive is that when I boot and run smartctl from that partition, it tells me the hard drive is fine (PASSED). After it locks up with terrible messages like unable to find superblock 0, etc., I can then boot into an older Fedora and run e2fsck, and it fixes the errors. And smartctl there also shows that the drive passes. I can also access data in other partitions on the drive without problem. Notably, those partitions are *not* updated from the OS in the partition that is having problems. It's an older drive, and it is a Seagate, a brand I've had problems with in the past, so I'm going with the failing drive explanation for now. But I thought I should mention the possibility that rawhide might have a file system instability. Especially now that btrfs is the default, so not many people will be exercising ext4. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
