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 03:04:30PM +0200, Walter Robert Ditzler wrote: > lars, > > when i do a: > > root at srv-ldeb-xen001:~# /etc/init.d/drbd status > drbd driver loaded OK; device status: > version: 8.3.11 (api:88/proto:86-96) > srcversion: 0D2B62DEDB020A425130935 > m:res cs ro ds p mounted > fstype > 0:server01 Connected " C > 1:server02 Connected Primary/Secondary UpToDate/UpToDate C > 2:server03 Connected Primary/Secondary UpToDate/UpToDate C > 3:server04 Connected Primary/Secondary UpToDate/UpToDate C > 4:server05_1 Connected Primary/Secondary UpToDate/UpToDate C > 5:server05_2 Connected Primary/Secondary UpToDate/UpToDate C > 6:server06 Connected Primary/Secondary UpToDate/UpToDate C > root at srv-ldeb-xen001:~# > *** > > can this mean, even when i got "Primary/Secondary UpToDate/UpToDate C" > that on one host, in my case xen002, i had a "Diskless" state? It does not tell *anything* about what may or may not have occurred earlier. For that you need logs. > i check those servers weekly once or twice, never ever had diffrent than > "Primary/Secondary UpToDate/UpToDate C". Then, maybe, you are in fact bypassing DRBD? Do you have any counter increase in /proc/drbd at all? "dw:", "ns:" and so on? > by the way: on my 2TB disk what is better, internal meta-data or external? "yes". > and in my config i didnt drbd the meta data, each host had its own meta data > onto a lvm. > > thanks a lot, > > walter > > -----Original Message----- > From: drbd-user-bounces at lists.linbit.com > [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Lars Ellenberg > Sent: Donnerstag, 28. Juni 2012 14:35 > To: drbd-user at lists.linbit.com > Subject: Re: [DRBD-user] sync doesnt work > > 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 > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed