Created
April 13, 2023 17:36
-
-
Save mdcallag/f6914cfa907cbe91da02086d166becc8 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Sat Apr 8 12:01:41 2023] nvme nvme0: I/O 1020 QID 8 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 64 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 65 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 66 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 67 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 68 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 69 QID 5 timeout, aborting | |
[Sat Apr 8 12:01:50 2023] nvme nvme0: I/O 70 QID 5 timeout, aborting | |
[Sat Apr 8 12:02:11 2023] nvme nvme0: I/O 1020 QID 8 timeout, reset controller | |
[Sat Apr 8 12:02:43 2023] nvme nvme0: I/O 25 QID 0 timeout, reset controller | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Device not ready; aborting reset, CSTS=0x1 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:32 2023] nvme nvme0: Abort status: 0x371 | |
[Sat Apr 8 12:03:53 2023] nvme nvme0: Device not ready; aborting reset, CSTS=0x1 | |
[Sat Apr 8 12:03:53 2023] nvme nvme0: Removing after probe failure status: -19 | |
[Sat Apr 8 12:04:13 2023] nvme nvme0: Device not ready; aborting reset, CSTS=0x1 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: detected capacity change from 1953525168 to 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 3423608 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 27840 op 0x1:(WRITE) flags 0x1000 phys_seg 2 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 45476600 op 0x1:(WRITE) flags 0x100000 phys_seg 87 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 46786392 op 0x1:(WRITE) flags 0x100000 phys_seg 36 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 41174376 op 0x1:(WRITE) flags 0x100000 phys_seg 52 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 976799633 op 0x1:(WRITE) flags 0x29800 phys_seg 1 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 45475576 op 0x1:(WRITE) flags 0x104000 phys_seg 92 prio class 0 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 976799661 op 0x1:(WRITE) flags 0x29800 phys_seg 1 prio class 0 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): log I/O error -5 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 977729712 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 14999, offset 7585792, sector 3423624 | |
[Sat Apr 8 12:04:13 2023] blk_update_request: I/O error, dev nvme0n1, sector 14976 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): log I/O error -5 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): log I/O error -5 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): log I/O error -5 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 14602, offset 838139904, sector 46786744 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): AG 0 preallocation gc worker failed, err=-5 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 18835, offset 485072896, sector 53009816 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 1074705521, offset 0, sector 977727272 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 14605, offset 234364928, sector 41174936 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 1074709337, offset 0, sector 977729720 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 17432, offset 274612224, sector 45477592 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): Log I/O Error (0x2) detected at xlog_ioend_work+0x7a/0x80 [xfs] (fs/xfs/xfs_log.c:1364). Shutting down filesystem. | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 17445, offset 383008768, sector 54599864 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 14596, offset 234381312, sector 42820136 | |
[Sat Apr 8 12:04:13 2023] nvme0n1: writeback error on inode 1074695824, offset 0, sector 977717880 | |
[Sat Apr 8 12:04:13 2023] XFS (nvme0n1): Please unmount the filesystem and rectify the problem(s) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment