On Mon, Nov 22, 2021 at 12:50:06PM -0800, Kevin Fenzi wrote: > I think there's something deeper going on. ;( > > That builder has in dmesg: > > [399371.168000] print_req_error: 2 callbacks suppressed > [399371.168007] blk_update_request: I/O error, dev vda, sector 174077464 op 0x1:(WRITE) flags 0x100000 phys_seg 134 prio class 0 > [399371.168231] blk_update_request: I/O error, dev vda, sector 174079864 op 0x1:(WRITE) flags 0x104000 phys_seg 106 prio class 0 > [399371.168268] blk_update_request: I/O error, dev vda, sector 174082424 op 0x1:(WRITE) flags 0x104000 phys_seg 72 prio class 0 > [399371.168299] blk_update_request: I/O error, dev vda, sector 174084984 op 0x1:(WRITE) flags 0x100000 phys_seg 79 prio class 0 > [399371.168334] blk_update_request: I/O error, dev vda, sector 174087264 op 0x1:(WRITE) flags 0x104000 phys_seg 246 prio class 0 > [399371.168364] blk_update_request: I/O error, dev vda, sector 174089824 op 0x1:(WRITE) flags 0x100000 phys_seg 11 prio class 0 > [399371.168394] blk_update_request: I/O error, dev vda, sector 174089984 op 0x1:(WRITE) flags 0x104000 phys_seg 232 prio class 0 > [399371.168535] blk_update_request: I/O error, dev vda, sector 174092544 op 0x1:(WRITE) flags 0x100000 phys_seg 25 prio class 0 > [399371.168632] blk_update_request: I/O error, dev vda, sector 174092800 op 0x1:(WRITE) flags 0x104000 phys_seg 217 prio class 0 > [399371.168661] blk_update_request: I/O error, dev vda, sector 174095360 op 0x1:(WRITE) flags 0x100000 phys_seg 40 prio class 0 > [399371.169478] vda6: writeback error on inode 204925378, offset 0, sector 174074904 > [399371.196642] vda6: writeback error on inode 70353785, offset 0, sector 72333240 > [399371.204462] vda6: writeback error on inode 70353792, offset 0, sector 73328008 > [399371.206361] vda6: writeback error on inode 70353784, offset 0, sector 72295304 > > It is running a old kernel tho (it was reinstalled recently). > Along with 3 others. > > I have updated them all and rebooted them into the latest kernel. > If you see this again, please file a ticket on it and we can dig deeper. > > I'll also try and keep an eye out on them but I am on PTO this week.... So, they all started showing the issues again... I have reinstalled them, this time with different (more conservative) cache settings for the disk. Hopefully this will fix things and the new mainframe is just more sensitive for i/o than the old one was. Will keep watching them. There is also: https://pagure.io/fedora-infrastructure/issue/10362 to report seeing issues now. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
