[DRBD-user] Avoiding semi-fullsync's?

Lars Marowsky-Bree lmb at suse.de
Wed Apr 27 14:52:16 CEST 2005

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


On 2005-04-27T14:27:46, Leroy van Logchem <leroy.vanlogchem at wldelft.nl> wrote:

> Based on the story below, why are so many bits set
> while it was perfectly in sync a few moments before
> the Local IO failure? I really like to aviod these
> semi-fullsync's. Please help. The story goes like:
> 
> Left-side server is Secondary and has Heartbeat running
> ready to takeover..
> 
> 13:14:45 drbd0: Secondary/Secondary --> Secondary/Primary
> 13:28:34 drbd0: PARTNER DISKLESS
		  ^^^^^^^^^^^^^^^^

drbd initiates a full restore in response to that IIRC, because it
assumes the full remote image has been "lost".


Sincerely,
    Lars Marowsky-Brée <lmb at suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business




More information about the drbd-user mailing list