search for: 2161832

Back to replica 3 w/o arbiter. Two fio jobs running (direct=1 and direct=0), rebooting one node... and VM dmesg looks like: [ 483.862664] blk_update_request: I/O error, dev vda, sector 23125016 [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.904045] Aborting journal on device vda1-8. [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.909585] Buffer I/O error on 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

...l Szalbot wrote: > Back to replica 3 w/o arbiter. Two fio jobs running (direct=1 and > direct=0), rebooting one node... and VM dmesg looks like: > > [ 483.862664] blk_update_request: I/O error, dev vda, sector 23125016 > [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 > [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 > [ 483.904045] Aborting journal on device vda1-8. > [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 > [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 > [ 483.909585]...

...t;> Back to replica 3 w/o arbiter. Two fio jobs running (direct=1 and >> direct=0), rebooting one node... and VM dmesg looks like: >> >> [ 483.862664] blk_update_request: I/O error, dev vda, sector 23125016 >> [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 >> [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 >> [ 483.904045] Aborting journal on device vda1-8. >> [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 >> [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 &gt...