Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jul 03, 2012 at 05:22:24PM +0100, Matt Hickman wrote: Hmmm. That mail seems to have been stuck in some queue for a while. > Hi guys, I'm building a pacemaker cluster and am having problems with > the LVM resource in that it start and stop straight away. I've used > the Linbit guide to set this up, but can't seem to see why its > happening. > > > > I've copied the config etc below if anyone can help. > > Thanks in advance Matt > > > crm_mon: > > ============ > Last updated: Tue Jul 3 19:31:44 2012 > Stack: Heartbeat > Current DC: upnas2 (b1fa8c22-cd5e-4d1f-8683-2e9b0766f09e) - partition with quorum > Version: 1.0.12-unknown > 2 Nodes configured, unknown expected votes > 8 Resources configured. > ============ > > Online: [ upnas2 upnas1 ] > > Master/Slave Set: ms_drbd_infiniband2 > Masters: [ upnas2 ] > Slaves: [ upnas1 ] > Resource Group: rg_infiniband2 > p_target_infiniband2 (ocf::heartbeat:iSCSITarget): Started upnas2 > p_lvm_infiniband2 (ocf::heartbeat:LVM): Stopped > p_lu_infiniband2_lun12 (ocf::heartbeat:iSCSILogicalUnit): Stopped > p_ip2 (ocf::heartbeat:IPaddr2): Stopped > Master/Slave Set: ms_drbd_infiniband3 > Masters: [ upnas2 ] > Slaves: [ upnas1 ] > Resource Group: rg_infiniband3 > p_target_infiniband3 (ocf::heartbeat:iSCSITarget): Started upnas2 > p_lvm_infiniband3 (ocf::heartbeat:LVM): Stopped > p_lu_infiniband3_lun13 (ocf::heartbeat:iSCSILogicalUnit): Stopped > p_ip3 (ocf::heartbeat:IPaddr2): Stopped > Master/Slave Set: ms_drbd_infiniband4 > Masters: [ upnas2 ] > Slaves: [ upnas1 ] > Resource Group: rg_infiniband4 > p_target_infiniband4 (ocf::heartbeat:iSCSITarget): Started upnas2 > p_lvm_infiniband4 (ocf::heartbeat:LVM): Stopped > p_lu_infiniband4_lun14 (ocf::heartbeat:iSCSILogicalUnit): Stopped > p_ip4 (ocf::heartbeat:IPaddr2): Stopped > Master/Slave Set: ms_drbd_infiniband1 > Masters: [ upnas1 ] > Slaves: [ upnas2 ] > Resource Group: rg_infiniband1 > p_target_infiniband1 (ocf::heartbeat:iSCSITarget): Started upnas1 > p_lvm_infiniband1 (ocf::heartbeat:LVM): Stopped > p_lu_infiniband1_lun11 (ocf::heartbeat:iSCSILogicalUnit): Stopped > p_ip1 (ocf::heartbeat:IPaddr2): Stopped > > Failed actions: > p_lvm_infiniband2_start_0 (node=upnas2, call=43, rc=7, status=complete): not running > p_lvm_infiniband3_start_0 (node=upnas2, call=45, rc=7, status=complete): not running > p_lvm_infiniband4_start_0 (node=upnas2, call=49, rc=7, status=complete): not running > p_lvm_infiniband1_start_0 (node=upnas2, call=51, rc=7, status=complete): not running > p_lvm_infiniband1_start_0 (node=upnas1, call=42, rc=7, status=complete): not running > > pvscan: upnas1: > > PV /dev/sda8 VG vg_upnas_4 lvm2 [16.09 GB / 16.09 GB free] > PV /dev/sda7 VG vg_upnas_3 lvm2 [16.09 GB / 16.09 GB free] > PV /dev/sda6 VG vg_upnas_2 lvm2 [16.09 GB / 16.09 GB free] > PV /dev/drbd1 VG vg_upnas_1 lvm2 [16.09 GB / 16.09 GB free] > Total: 4 [64.35 GB] / in use: 4 [64.35 GB] / in no VG: 0 [0 ] > > vgscan: upnas1: > > Reading all physical volumes. This may take a while... > Found volume group "vg_upnas_4" using metadata type lvm2 The LVM resource agent needs at least one LV in a VG to be able to successfully deal with it. Otherwise it cannot tell the difference between a "started" or "stopped" VG. Because, without an LV, there actually is no difference... So once you created your first LV in those VGs, and do some "crm resource cleanup ...", you should be one step further. > Found volume group "vg_upnas_3" using metadata type lvm2 > Found volume group "vg_upnas_2" using metadata type lvm2 > Found volume group "vg_upnas_1" using metadata type lvm2 -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com