I have the same problem. Yesterday I upgraded to kernel 3.15.3 and my
kernel.log is filling with this messages:
Jul 7 11:23:05 virtx kernel: [55267.193678] block drbd39: meta_data io:
kworker/u65:1 [31208]:drbd_md_sync_page_io(,16s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:05 virtx kernel: [55267.199652] block drbd39: meta_data io:
kworker/u65:1 [31208]:drbd_md_sync_page_io(,24s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:07 virtx kernel: [55269.757781] block drbd28: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,40s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:13 virtx kernel: [55275.193624] block drbd30: meta_data io:
kworker/u66:4 [30295]:drbd_md_sync_page_io(,56s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:13 virtx kernel: [55275.401312] block drbd9: meta_data io:
kworker/u66:4 [30295]:drbd_md_sync_page_io(,32s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:14 virtx kernel: [55276.329633] block drbd28: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,48s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:15 virtx kernel: [55277.168129] block drbd28: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,56s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:23 virtx kernel: [55285.399803] block drbd9: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,40s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:23 virtx kernel: [55285.503232] block drbd32: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,64s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:23 virtx kernel: [55285.503809] block drbd32: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,8s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:23 virtx kernel: [55286.086788] block drbd19: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,48s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:24 virtx kernel: [55286.128598] block drbd30: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,64s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Jul 7 11:23:25 virtx kernel: [55287.594011] block drbd28: meta_data io:
kworker/u66:0 [31338]:drbd_md_sync_page_io(,64s,WRITE)
_al_write_transaction+0x4f9/0xa00 [drbd]
Seems to happen on all my drbd devices (currently 52 on this server) and
is affecting functionality.
I use external meta-disk. Disk and meta-disk are LVM volumes and blocks
are used by VPSs running below kvm/libvirt/qemu.
Some of my guest VPS show errors like this:
Jul 7 09:09:51 webx kernel: [28863.199248] EXT4-fs warning (device
vda1): ext4_end_bio:317: I/O error writing to inode 1050005 (offset 0
size 0 starting block 4871811)
Jul 7 09:09:51 webx kernel: [28863.199278] Buffer I/O error on device
vda1, logical block 4871555
Jul 7 09:09:51 webx kernel: [28863.199378] EXT4-fs warning (device
vda1): ext4_end_bio:317: I/O error writing to inode 1050005 (offset 0
size 0 starting block 4871814)
Jul 7 09:09:51 webx kernel: [28863.199381] Buffer I/O error on device
vda1, logical block 4871558
Jul 7 09:09:51 webx kernel: [28863.199383] Buffer I/O error on device
vda1, logical block 4871559
And some times the guest remount the filesystem read-only due to the errors.
Marcus
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
