[DRBD-user] Problems restarting DRBD 8.3 cluster after power failure

[Gokak, Arun Madhukar]

If you have enabled crm and using OCF Resource Agent to manage the DRBD
then you may need to apply a small path for it to work with DRBD 8.3.0.
Please refer to the below HA mailing list thread to understand the
problem and apply Dejan's patch and also include a small correction
suggested for it.

http://www.gossamer-threads.com/lists/linuxha/users/54352

Regards,
Arun.

From: Clint Rosander <clint at vmix.com>
Subject: [DRBD-user] Problems restarting DRBD 8.3 cluster after power
	failure
To: drbd-list <drbd-user at lists.linbit.com>
Message-ID: <69831536-A740-408B-AD3F-40DD069DE3E5 at vmix.com>
Content-Type: text/plain; charset="us-ascii"

We recently had a the joy of experiencing a power failure at our  
datacenter.

I have setup a few different clusters using a 2 node Active/Passive  
DRBD/Heartbeat configuration with MySQL running on the Active/Primary  
node. These clusters are setup using versions DRBD 0.7.21 and  
Heartbeat 2.0.7. When these boxes rebooted, and I restarted DRBD and  
Heartbeat on the Primary and Secondary nodes in each cluster,  
everything got back to their original states with no problems.

I have a new cluster I have been doing a proof of concept on, with  
the same 2 node style configuration, except running versions DRBD  
8.3.0 and Heartbeat 2.07. When I restarted DRBD on these servers I  
got the following:

Node #1:

drbd driver loaded OK; device status:
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: <removed> build by root at node1, 2009-02-03 10:44:58
m:res            cs         ro                 ds                 p   
mounted  fstype
0:??not-found??  Connected  Primary/Secondary  UpToDate/UpToDate  C
1:??not-found??  Connected  Primary/Secondary  UpToDate/UpToDate  C

Node #2:

drbd driver loaded OK; device status:
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by  
root at node2, 2009-02-03 16:28:26
m:res            cs         ro                 ds                 p   
mounted  fstype
0:??not-found??  Connected  Secondary/Primary  UpToDate/UpToDate  C
1:??not-found??  Connected  Secondary/Primary  UpToDate/UpToDate  C


Can anyone please explain what the ??not-found?? means and why  
everything else in the status info looks like everything is fine?  
However, I do not see that the two devices that represent resource 0  
and 1 ever got mounted:

df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md2               5036224   1742416   3037980  37% /
/dev/md1                194366     13364    170967   8% /boot
none                   2020692         0   2020692   0% /dev/shm
/dev/md5              38637728     81852  36593140   1% /opt


The mounted disks should look like:

df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda3              5036316   2490456   2290028  53% /
/dev/sda1               194442     20111    164292  11% /boot
none                   4083052         0   4083052   0% /dev/shm
/dev/sda7             64033092   9845224  50935112  17% /opt
/dev/drbd0           280987876  10224568 256489960   4% /data
/dev/drbd1            61931268  49201936   9583408  84% /logs


Any help would be greatly appreciated. Thanks!

Clint