[DRBD-user] during sync, inconsistant side becomes primary

Gerald Brandt gbr at majentis.com
Fri Oct 21 17:10:20 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.


I shut down my primary for a disk upgrade.  After the upgrade, the primary was inconsistent (obviously, it was missing 13 hours of uptime data).

Heartbeat made the unit primary again, even though the data was inconsistent.

How does DRBD handle reads from a known inconsistent primary?


version: 8.3.7 (api:88/proto:86-91)                                             
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root at filer-1, 2011-03-05 08:29:38                                                                   
 1: cs:SyncTarget ro:Primary/Secondary ds:Inconsistent/UpToDate C r----         
    ns:3889896 nr:119684960 dw:123558136 dr:1413208 al:2527 bm:12480 lo:710 pe:710 ua:710 ap:0 ep:1 wo:d oos:284816636                                          
        [====>...............] sync'ed: 29.6% (278140/395036)M                  
        finish: 2:19:53 speed: 33,932 (29,128) K/sec     

More information about the drbd-user mailing list