[DRBD-user] drbd problem

Shaun Thomas sthomas at optionshouse.com
Wed Jun 20 15:11:27 CEST 2012

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

On 06/19/2012 11:59 PM, Dagia Dorjsuren wrote:

> after node1 crashed, I run below command on node2. But it was not run.

Since this is node 2, it was secondary. Unless you have Pacemaker or 
some other tool installed, it won't automatically become primary. You 
need to do that manually:

drbdadm primary r0

If it doesn't let you make this node primary, disconnect and then make 
it primary:

drbdadm disconnect r0
drbdadm primary r0

Once you've done that, you should be able to do this:

> mount /dev/drbd0 /srv/data

If/when you get node 1 working again, you'll have to reconnect, and 
possibly re-sync it with node 2. The easiest way to do this is:

On node 2:

drbdadm connect r0

On node 1:

drbdadm -- --discard-my-data connect r0

Try to do them in that order. After that, it's a good idea to validate 
the data:

drbdadm validate r0

Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
sthomas at optionshouse.com


See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

More information about the drbd-user mailing list