[DRBD-user] sync doesnt work

Walter Robert Ditzler ditwal001 at gmail.com
Thu Jun 28 14:24:14 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.


Felix,

Fort he manuall replicating of my devices i stoped drbd of course. My old
host, xen001 is going to be formated and reinstalled. does that mean i
should rather setup "internal" fort he meta-data?

anyway, strange ist hat the data hasn't synced at all. after coping from
xen001 onto xen002 with dd over ssh i finally have the previous state of my
domu's.

i am only a bit afraid when i bring up again my new xen001, what will be in
the future, what did i wrong in the config files or better, what
possibilities do i have to track or test the sync's of drbd devices?

thanks a lot,

walter.

-----Original Message-----
From: Felix Frank [mailto:ff at mpexnet.de] 
Sent: Donnerstag, 28. Juni 2012 13:59
To: Walter Robert Ditzler
Cc: drbd-user
Subject: Re: sync doesnt work

Hi,

On 06/28/2012 01:48 PM, Walter Robert Ditzler wrote:
> yes all volumes didn't sync even when the /etc/init.d/drbd status said
> - Primary/Secondary  UpToDate/UpToDate C I just finished to manually 
> copy all devices onto the xen002.

yes, but are they live replicating now that you have completed this task?

You can check by snapshotting the backing device on the secondary, if you
can survive the performance hit for a few minutes. Just mount the snapshot
and examine the data.

> When an /index/is specified, each index number refers to a fixed slot 
> of meta-data of 128 MB, which allows a maximum data size of 4 GB.

Interesting, I didn't know that. Is that a typo in the documentation?
Because 128MB of metadata for 4GB of data cannot be right. That should
probably be 4TB there.
If the 4G limit *was* correct, it would explain some things, seeing as your
volumes are each way above 4GB, but again - that doesn't make a lick of
sense.

Cheers,
Felix




More information about the drbd-user mailing list