[DRBD-user] Possible DRBD Desync After Outage - Why?

Florian Haas florian.haas at linbit.com
Wed Jul 8 09:03:22 CEST 2009

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

On 07/07/2009 06:08 PM, Mike Sweetser - Adhost wrote:
> Hello:
> We have two DRBD machines running RHEL 5.3 with DRBD 8.3.0.  Recently,
> we had an outage that took the primary server in the cluster down,
> leaving it to failover using DRBD and Heartbeat.  This was done with no
> issues.  
> When the other server came back online, we initiated a manual resync as
> follows:
> drbdadm secondary RESOURCE
> drbdadm -- --discard-my-data connect RESOURCE

If you just had a normal node outage, and you had to do this afterwards,
then that's a setup problem. You've run yourself into split brain which
precluded normal DRBD recovery and synchronization. You shouldn't have
to intervene manually to initiate resync, it should all happen

Or you did this as a pointless exercise after DRBD had already recovered.

Look for "Split-Brain detected, dropping connection" messages in your
logs, check what the User's Guide has to say about preventing split
brain, and fix your setup.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090708/4a8b71a8/attachment.pgp>

More information about the drbd-user mailing list