Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Jun 28, 2012 at 01:58:57PM +0200, Felix Frank wrote: > 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. 4 TiB minus a few sectors, actually. The only explanation would be that you had been "Diskless" on one of the systems for an extended period of time, or that you had been disconnected for what ever reason, or something fiddled with DRBD meta data. Or that you are bypassing DRBD. I've seen this serveral times: people configuring their VMs to run on the LVs, then telling DRBD to replicate these LVs. [VM] [DRBD]--- replicates nothing to --- [DRBD peer] | | sits on `-- writes to [LV] Because no-one is writing to DRBD, DRBD cannot replicate anything. So don't do that. DRBD logs and complete configuration (including the VM configuration) may help to understand what was going on in your setup. Lars