[DRBD-user] Removing DRBD Kernel Module Blocks

[Andrew Martin]

Hi Felix, 


I was attempting to failover from node1 to node2 by putting node1 into standby mode. I have not been able to get crm resource migrate to work - e.g. I'll instruct it to migrate the DRBD resource (which should cause all other resources to migrate as well) with crm resource migrate ms_drbd_mount1 node2 , but this doesn't seem to have any effect. 


Here are the software versions: 
pacemaker 1.1.6-2ubuntu0~ppa2 
heartbeat 1:3.0.5-3ubuntu0~ppa1 
drbd8-utils 2:8.3.7-1ubuntu2.2 
Ubuntu 10.04.3 


The versions of pacemaker and heartbeat above are from the Ubuntu HA Maintainers Stable PPA: 
https://launchpad.net/~ubuntu-ha-maintainers/+archive/ppa 


I had to use this version of heartbeat/pacemaker because the version included with 10.04 does not support the ocf:heartbeat:exportfs OCF resource. 


Thanks, 


Andrew 

----- Original Message -----

From: "Felix Frank" <ff at mpexnet.de> 
To: "Andrew Martin" <amartin at xes-inc.com> 
Cc: "drbd-user" <drbd-user at lists.linbit.com> 
Sent: Tuesday, January 31, 2012 2:44:47 AM 
Subject: Re: [DRBD-user] Removing DRBD Kernel Module Blocks 

Hi, 

On 01/30/2012 11:27 PM, Andrew Martin wrote: 
> this behavior is still present when failing over with the DRBD 

what's the scenario here? node2 is master for both drbd0 and drbd1 and 
you're trying to fail over using crm resource migrate? 

> device.What does the digit after the resource indicate, e.g. the :1 or 
> :1_stop_0 below: 

Pacemaker internals I believe. 

Can you post the versions of all involved software? 
Is it possible your pacemaker and/or cluster-agents are old/broken? 

Regards, 
Felix 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120131/8ab5af4a/attachment.htm>