search for: ext4_journal_check_start

...cal block 262144, lost sync page write [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 [ 483.912192] blk_update_request: I/O error, dev vda, sector 2048 [ 483.913221] Buffer I/O error on dev vda1, logical block 0, lost sync page write [ 483.914546] EXT4-fs error (device vda1): ext4_journal_check_start:56: Detected aborted journal [ 483.916230] EXT4-fs (vda1): Remounting filesystem read-only [ 483.917231] EXT4-fs (vda1): previous I/O error to superblock detected [ 483.917353] JBD2: Error -5 detected when updating journal superblock for vda1-8. [ 483.921106] blk_update_request: I/O error, dev...

FYI I set up replica 3 (no arbiter this time), did the same thing - rebooted one node during lots of file IO on VM and IO stopped. As I mentioned either here or in another thread, this behavior is caused by high default of network.ping-timeout. My main problem used to be that setting it to low values like 3s or even 2s did not prevent the FS to be mounted as read-only in the past (at least with

..., sector 8652800 [ 572.874707] Buffer I/O error on dev vda1, logical block 1081344, lost sync page write [ 572.875472] blk_update_request: I/O error, dev vda, sector 2048 [ 572.876009] Buffer I/O error on dev vda1, logical block 0, lost sync page write [ 572.876727] EXT4-fs error (device vda1): ext4_journal_check_start:56: Detected aborted journal[ 572.878061] JBD2: Error -5 detected when updating journal superblock for vda1-8. [ 572.878807] EXT4-fs (vda1): Remounting filesystem read-only [ 572.879311] EXT4-fs (vda1): previous I/O error to superblock detected [ 572.880937] blk_update_request: I/O error, dev...

...ge write > [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 > [ 483.912192] blk_update_request: I/O error, dev vda, sector 2048 > [ 483.913221] Buffer I/O error on dev vda1, logical block 0, lost > sync page write > [ 483.914546] EXT4-fs error (device vda1): > ext4_journal_check_start:56: Detected aborted journal > [ 483.916230] EXT4-fs (vda1): Remounting filesystem read-only > [ 483.917231] EXT4-fs (vda1): previous I/O error to superblock detected > [ 483.917353] JBD2: Error -5 detected when updating journal > superblock for vda1-8. > [ 483.921106] blk_update...

....911121] blk_update_request: I/O error, dev vda, sector 2048 >> [ 483.912192] blk_update_request: I/O error, dev vda, sector 2048 >> [ 483.913221] Buffer I/O error on dev vda1, logical block 0, lost >> sync page write >> [ 483.914546] EXT4-fs error (device vda1): >> ext4_journal_check_start:56: Detected aborted journal >> [ 483.916230] EXT4-fs (vda1): Remounting filesystem read-only >> [ 483.917231] EXT4-fs (vda1): previous I/O error to superblock detected >> [ 483.917353] JBD2: Error -5 detected when updating journal >> superblock for vda1-8. >> [ 48...