Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
> If with direct io, you do not get larger requests than 4k in the
> "virtual" layers, your (in kernel) device mapper and/or DRBD are
> too old.
>
> If they even don't get merged into larger requests in the "real"
> device queue, then there is something wrong there as well.
ok, RHEL 5.2 is pretty old,
so we have to try this with RHEL 5.6 + DRBD 8.4.0, right?
Is DRBD 8.4.0 release in June?
>> there is no I/O error but Pacemaker detects it as DRBD's error(monitor
>> Timed out).
>
> What exactly is timing out,
> and what is the time out?
This problem arose at the customer's place,
and we are now asking them to see the logs.
If we can get them, we 'll post them here.
from what I've gathered,
They did "mke2fs" during DRBD + Pacemaker are running,
# mke2fs -F -j /dev/vg3/lv0
after that, crm_mon showed that LVM RA failed.
see attached.
I'm not sure, but util 100% might cause something delay of LVM command.
Thanks,
Junko IKEDA
-------------- next part --------------
?============
Last updated: Fri Oct 9 19:04:16 2009
Stack: Heartbeat
Current DC: node01.tyo.**********.co.jp (c16ac32e-d994-4abc-a543-042567af2a6c) - partition with quorum
Version: 1.0.4-6dede86d6105786af3a5321ccf66b44b6914f0aa
2 Nodes configured, unknown expected votes
6 Resources configured.
============
Online: [ node01.tyo.**********.co.jp node02.tyo.**********.co.jp ]
Master/Slave Set: ms_drbd_r0
Masters: [ node01.tyo.**********.co.jp ]
Slaves: [ node02.tyo.**********.co.jp ]
Master/Slave Set: ms_drbd_r1
Masters: [ node01.tyo.**********.co.jp ]
Slaves: [ node02.tyo.**********.co.jp ]
Master/Slave Set: ms_drbd_r2
Masters: [ node01.tyo.**********.co.jp ]
Slaves: [ node02.tyo.**********.co.jp ]
Resource Group: rg_vg0
res_portblock_0 (ocf::linbit:portblock): Started node01.tyo.**********.co.jp
res_ip_10 (ocf::heartbeat:IPaddr2): Started node01.tyo.**********.co.jp
res_drbdupper_r0u (heartbeat:drbdupper_mod): Started node01.tyo.**********.co.jp
res_lvm_vg0 (ocf::heartbeat:LVM): Started node01.tyo.**********.co.jp FAILED
res_target_0 (ocf::heartbeat:iSCSITarget): Started node01.tyo.**********.co.jp
res_lu_vg0_lv0 (ocf::heartbeat:iSCSILogicalUnit): Started node01.tyo.**********.co.jp
res_portunblock_0 (ocf::linbit:portblock): Started node02.tyo.**********.co.jp (unmanaged) FAILED
Resource Group: rg_vg1
res_portblock_1 (ocf::linbit:portblock) Started [ node02.tyo.**********.co.jp node01.tyo.**********.co.jp ]
res_ip_11 (ocf::heartbeat:IPaddr2): Started node01.tyo.**********.co.jp
res_drbdupper_r1u (heartbeat:drbdupper_mod): Started node01.tyo.**********.co.jp
res_lvm_vg1 (ocf::heartbeat:LVM): Started node01.tyo.**********.co.jp FAILED
res_target_1 (ocf::heartbeat:iSCSITarget): Stopped
res_lu_vg1_lv0 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_lu_vg1_lv2 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_lu_vg1_lv3 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_portunblock_1 (ocf::linbit:portblock): Stopped
res_fs_samba (ocf::heartbeat:Filesystem): Stopped
res_samba (lsb:smb): Stopped
Resource Group: rg_vg2
res_portblock_2 (ocf::linbit:portblock) Started [ node02.tyo.**********.co.jp node01.tyo.**********.co.jp ]
res_ip_12 (ocf::heartbeat:IPaddr2): Started node01.tyo.**********.co.jp
res_drbdupper_r2u (heartbeat:drbdupper_mod): Started node01.tyo.**********.co.jp
res_lvm_vg2 (ocf::heartbeat:LVM): Started node01.tyo.**********.co.jp (unmanaged) FAILED
res_target_2 (ocf::heartbeat:iSCSITarget): Stopped
res_lu_vg2_lv0 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_lu_vg2_lv1 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_lu_vg2_lv2 (ocf::heartbeat:iSCSILogicalUnit): Stopped
res_portunblock_2 (ocf::linbit:portblock): Stopped
Failed actions:
res_portunblock_0_stop_0 (node=node02.tyo.**********.co.jp, call=32, rc=1, status=complete): unknown error
res_lvm_vg0_monitor_120000 (node=node01.tyo.**********.co.jp, call=70, rc=-2, status=Timed Out): unknown exec error
res_lvm_vg2_monitor_0 (node=node01.tyo.**********.co.jp, call=218, rc=-2, status=Timed Out): unknown exec error
res_lvm_vg2_stop_0 (node=node01.tyo.**********.co.jp, call=233, rc=-2, status=Timed Out): unknown exec error
res_lvm_vg1_monitor_0 (node=node01.tyo.**********.co.jp, call=250, rc=-2, status=Timed Out): unknown exec error