История изменений
Исправление firkax, (текущая версия) :
В у себя dmesg изучили? Что там за ошибки?
[378510.200548] sd 1:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=51s
[378510.200557] sd 1:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 03 07 08 30 00 00 08 00
[378510.200562] blk_update_request: I/O error, dev sda, sector 50792496 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[378510.200571] EXT4-fs warning (device sda6): ext4_end_bio:345: I/O error 10 writing to inode 16 starting block 6349063)
[378510.200578] Buffer I/O error on device sda6, logical block 56838
[378510.200610] sd 1:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=48s
[378510.200615] sd 1:0:0:0: [sda] tag#30 CDB: Write(10) 2a 00 1a 00 28 30 00 00 08 00
[378510.200619] blk_update_request: I/O error, dev sda, sector 436217904 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[378510.200625] Buffer I/O error on dev sda8, logical block 46137350, lost async page write
.........
[378510.200854] Buffer I/O error on dev sda8, logical block 23, lost async page write
[378510.200866] Buffer I/O error on dev sda8, logical block 14, lost async page write
[378510.200929] EXT4-fs error (device sda8): ext4_check_bdev_write_error:215: comm Cache2 I/O: Error while async write back metadata
[378510.200940] EXT4-fs (sda8): previous I/O error to superblock detected
[378510.201662] Aborting journal on device sda8-8.
[378510.210953] EXT4-fs error (device sda8) in __ext4_new_inode:1089: Journal has aborted
[378510.218014] EXT4-fs error (device sda8) in ext4_create:2634: Journal has aborted
[378510.221070] EXT4-fs error (device sda8) in ext4_orphan_add:3015: Journal has aborted
[378510.227722] EXT4-fs error (device sda8) in ext4_reserve_inode_write:5761: Journal has aborted
[378510.230011] EXT4-fs error (device sda8): ext4_truncate:4296: inode #3933615: comm mozStorage #4: mark_inode_dirty error
[378510.232221] EXT4-fs error (device sda8) in ext4_truncate:4299: Journal has aborted
[378510.234433] EXT4-fs error (device sda8) in ext4_setattr:5539: Journal has aborted
[378510.286039] EXT4-fs error (device sda8): ext4_journal_check_start:83: Detected aborted journal
[378510.286048] EXT4-fs (sda8): Remounting filesystem read-only
Не знаю почему у них одинаковый таймстамп, видимо начало лага никак не логируется, а это только конец. До этого примерно минуту в top-е процам показывается %wait вместо %idle и все операции с диском висят. Если меньше минуты - всё норм, если больше - то ошибки и remount-ro.
Исправление firkax, :
В у себя dmesg изучили? Что там за ошибки?
[378510.200548] sd 1:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=51s
[378510.200557] sd 1:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 03 07 08 30 00 00 08 00
[378510.200562] blk_update_request: I/O error, dev sda, sector 50792496 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[378510.200571] EXT4-fs warning (device sda6): ext4_end_bio:345: I/O error 10 writing to inode 16 starting block 6349063)
[378510.200578] Buffer I/O error on device sda6, logical block 56838
[378510.200610] sd 1:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=48s
[378510.200615] sd 1:0:0:0: [sda] tag#30 CDB: Write(10) 2a 00 1a 00 28 30 00 00 08 00
[378510.200619] blk_update_request: I/O error, dev sda, sector 436217904 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[378510.200625] Buffer I/O error on dev sda8, logical block 46137350, lost async page write
.........
[378510.200854] Buffer I/O error on dev sda8, logical block 23, lost async page write
[378510.200866] Buffer I/O error on dev sda8, logical block 14, lost async page write
[378510.200929] EXT4-fs error (device sda8): ext4_check_bdev_write_error:215: comm Cache2 I/O: Error while async write back metadata
[378510.200940] EXT4-fs (sda8): previous I/O error to superblock detected
[378510.201662] Aborting journal on device sda8-8.
[378510.210953] EXT4-fs error (device sda8) in __ext4_new_inode:1089: Journal has aborted
[378510.218014] EXT4-fs error (device sda8) in ext4_create:2634: Journal has aborted
[378510.221070] EXT4-fs error (device sda8) in ext4_orphan_add:3015: Journal has aborted
[378510.227722] EXT4-fs error (device sda8) in ext4_reserve_inode_write:5761: Journal has aborted
[378510.230011] EXT4-fs error (device sda8): ext4_truncate:4296: inode #3933615: comm mozStorage #4: mark_inode_dirty error
[378510.232221] EXT4-fs error (device sda8) in ext4_truncate:4299: Journal has aborted
[378510.234433] EXT4-fs error (device sda8) in ext4_setattr:5539: Journal has aborted
[378510.286039] EXT4-fs error (device sda8): ext4_journal_check_start:83: Detected aborted journal
[378510.286048] EXT4-fs (sda8): Remounting filesystem read-only
Не знаю почему у них одинаковый таймстамп, видимо началолага никак не логируется, а это только конец. До этого примерно минуту в top-е процам показывается %wait вместо %idle и все операции с диском висят. Если меньше минуты - всё норм, если больше - то ошибки и remount-ro.
Исправление firkax, :
В у себя dmesg изучили? Что там за ошибки?
[378510.200548] sd 1:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=51s
[378510.200557] sd 1:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 03 07 08 30 00 00 08 00
[378510.200562] blk_update_request: I/O error, dev sda, sector 50792496 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[378510.200571] EXT4-fs warning (device sda6): ext4_end_bio:345: I/O error 10 writing to inode 16 starting block 6349063)
[378510.200578] Buffer I/O error on device sda6, logical block 56838
[378510.200610] sd 1:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=48s
[378510.200615] sd 1:0:0:0: [sda] tag#30 CDB: Write(10) 2a 00 1a 00 28 30 00 00 08 00
[378510.200619] blk_update_request: I/O error, dev sda, sector 436217904 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[378510.200625] Buffer I/O error on dev sda8, logical block 46137350, lost async page write
.........
[378510.200854] Buffer I/O error on dev sda8, logical block 23, lost async page write
[378510.200866] Buffer I/O error on dev sda8, logical block 14, lost async page write
[378510.200929] EXT4-fs error (device sda8): ext4_check_bdev_write_error:215: comm Cache2 I/O: Error while async write back metadata
[378510.200940] EXT4-fs (sda8): previous I/O error to superblock detected
[378510.201662] Aborting journal on device sda8-8.
[378510.210953] EXT4-fs error (device sda8) in __ext4_new_inode:1089: Journal has aborted
[378510.218014] EXT4-fs error (device sda8) in ext4_create:2634: Journal has aborted
[378510.221070] EXT4-fs error (device sda8) in ext4_orphan_add:3015: Journal has aborted
[378510.227722] EXT4-fs error (device sda8) in ext4_reserve_inode_write:5761: Journal has aborted
[378510.230011] EXT4-fs error (device sda8): ext4_truncate:4296: inode #3933615: comm mozStorage #4: mark_inode_dirty error
[378510.232221] EXT4-fs error (device sda8) in ext4_truncate:4299: Journal has aborted
[378510.234433] EXT4-fs error (device sda8) in ext4_setattr:5539: Journal has aborted
[378510.286039] EXT4-fs error (device sda8): ext4_journal_check_start:83: Detected aborted journal
[378510.286048] EXT4-fs (sda8): Remounting filesystem read-only
Не знаю почему у них одинаковый таймстамп, видимо началолага никак не логируется, а это только конец. До этого примерно минуту в top-е процам показывается %wait вместо %idle. Если меньше минуты - всё норм, если больше - то ошибки и remount-ro.
Исходная версия firkax, :
В у себя dmesg изучили? Что там за ошибки?
[378510.200548] sd 1:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=51s
[378510.200557] sd 1:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 03 07 08 30 00 00 08 00
[378510.200562] blk_update_request: I/O error, dev sda, sector 50792496 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[378510.200571] EXT4-fs warning (device sda6): ext4_end_bio:345: I/O error 10 writing to inode 16 starting block 6349063)
[378510.200578] Buffer I/O error on device sda6, logical block 56838
[378510.200610] sd 1:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT cmd_age=48s
[378510.200615] sd 1:0:0:0: [sda] tag#30 CDB: Write(10) 2a 00 1a 00 28 30 00 00 08 00
[378510.200619] blk_update_request: I/O error, dev sda, sector 436217904 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[378510.200625] Buffer I/O error on dev sda8, logical block 46137350, lost async page write
.........
[378510.200854] Buffer I/O error on dev sda8, logical block 23, lost async page write
[378510.200866] Buffer I/O error on dev sda8, logical block 14, lost async page write
[378510.200929] EXT4-fs error (device sda8): ext4_check_bdev_write_error:215: comm Cache2 I/O: Error while async write back metadata
[378510.200940] EXT4-fs (sda8): previous I/O error to superblock detected
[378510.201662] Aborting journal on device sda8-8.
[378510.210953] EXT4-fs error (device sda8) in __ext4_new_inode:1089: Journal has aborted
[378510.218014] EXT4-fs error (device sda8) in ext4_create:2634: Journal has aborted
[378510.221070] EXT4-fs error (device sda8) in ext4_orphan_add:3015: Journal has aborted
[378510.227722] EXT4-fs error (device sda8) in ext4_reserve_inode_write:5761: Journal has aborted
[378510.230011] EXT4-fs error (device sda8): ext4_truncate:4296: inode #3933615: comm mozStorage #4: mark_inode_dirty error
[378510.232221] EXT4-fs error (device sda8) in ext4_truncate:4299: Journal has aborted
[378510.234433] EXT4-fs error (device sda8) in ext4_setattr:5539: Journal has aborted
[378510.286039] EXT4-fs error (device sda8): ext4_journal_check_start:83: Detected aborted journal
[378510.286048] EXT4-fs (sda8): Remounting filesystem read-only