[DRBD-user] how to do with drbd after reboot!

Edwige Odedele odedele at popsicube.fr
Tue Aug 23 17:00:46 CEST 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hello,

 

I need your help.

I have drbd install on two servers then all of them is working all right
before I reboot the servers.

After reboot I got this error when trying to start drbd:

rootx:~# cat /proc/drbd

version: 8.3.7 (api:88/proto:86-91)

GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by rootx, 2011-

08-22 14:27:51

 0: cs:Unconfigured

rootx:/tmp# pvscan

  No matching physical volumes found

rootx:/tmp# vgscan

  Reading all physical volumes.  This may take a while...

0: Failure: (114) Lower device is already claimed. This usually means it is
moun

ted.

Command 'drbdsetup 0 disk /dev/sda4 /dev/sda4 internal --set-defaults
--create-d

evice' terminated with exit code 10

rootx:/tmp# cat /proc/drbd

version: 8.3.7 (api:88/proto:86-91)

GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by rootx, 2011-

08-22 14:27:51

 0: cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown C r----

    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0

rootx:/tmp#

 

 

rootx:/tmp# drbdadm -- --overwrite-data-of-peer primary data

0: State change failed: (-2) Refusing to be Primary without at least one
UpToDat

e disk

Command 'drbdsetup 0 primary --overwrite-data-of-peer' terminated with exit
code

 17

 

 

I think that the problem come from de disk, but I don’t know what to do.

This is  the contents of my resource:

 

 

resource data {

protocol C;

startup {

# Wait for connection timeout.

# The init script blocks the boot process until the resources

# are connected. This is so when the cluster manager starts later,

# it does not see a resource with internal split-brain.

# In case you want to limit the wait time, do it here.

# Default is 0, which means unlimited. Unit is seconds.

#

# wfc-timeout 0;

# Wait for connection timeout if this node was a degraded cluster.

# In case a degraded cluster (= cluster with only one node left)

# is rebooted, this timeout value is used.

#

degr-wfc-timeout 120; # 2 minutes.

}

on rootx {

device /dev/drbd0;

disk /dev/sda4;

address 192.168.2.5:7780;

meta-disk internal;

}

on rooty {

device /dev/drbd0;

disk /dev/sda4;

address 192.168.2.6:7780;

meta-disk internal;

}

}

 

I really need your help!

 

 

 

 

 

 

 



  

 

Cordialement,

 

 

Edwige ODEDELE
Apprentie Réseaux et Sécurité 

	

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110823/4ef08781/attachment.htm>


More information about the drbd-user mailing list