[DRBD-user] SyncingAll at any drbd startup

Paolo Morandi paolo at i-dome.com
Tue Jun 1 11:29:37 CEST 2004

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


Lars Ellenberg wrote:
>>- for shutdown the cluster i must before stopping drbd on primary node 
>>and after shutdown the two machine (graceful shutdown): a question, but 
>>shutting down are not executed the 'drbd stop' ?
> 
> 
> depending on your setup. most likely it is.
> but you may have a race, if you shutdown both at the same time.
Now the cluster is running with heartbeat and work fine. If i start drbd 
i see on the primary machine in Secondary/Secondary state, after 
heartbeat i see the filesystem mounted and the cluster state in 
Primary/Secondary.
If i stop heartbeat the filesystem are unmounted and the cluster state 
back to Secondary/Secondary. So if I stop drbd, can restart without sync.
The problem is when i want shutdown the cluster: if i dont make manually 
the operation at the new statup the cluster go to SyncAll.
In the log i see that correctly heartbeat send the datadisk stop and 
also i see the trace of the drbd stop, but to restart drbd i see in the 
log this rows:
May 31 23:06:13 elena kernel: drbd0: Connection established. 
size=73545472 KB / blksize=4096 B
May 31 23:06:13 elena kernel: drbd0: Synchronisation started blks=15
May 31 23:06:13 elena drbd: drbd:  drbd0  done.
May 31 23:06:13 elena drbd: 'drbd0' SyncingAll, but I have the good 
data. No need to wait.
May 31 23:06:13 elena drbd: drbd: 'drbd0' SyncingAll, but I have the 
good data. No need to wait.
May 31 23:06:13 elena drbd: WARNING: a cluster manager should not 
failover yet!
May 31 23:06:13 elena drbd: drbd: 'drbd0' SyncingAll, but I have the 
good data. No need to wait.
May 31 23:06:13 elena drbd: drbd: WARNING: a cluster manager should not 
failover yet!
May 31 23:06:13 elena drbd: drbd: WARNING: a cluster manager should not 
failover yet!
May 31 23:06:13 elena drbd: drbd: 'drbd0' still not in Connected state, 
but SyncingAll
May 31 23:06:13 elena drbd: ^I[>...................] sync'ed:  0.1% 
(71821/71821)M
May 31 23:06:13 elena drbd: ^Ifinish: 40:52:29h speed: 476 (476) K/sec
May 31 23:06:13 elena rc: Starting drbd:  succeeded

> 
> 
>>- for mounting the filesystem i must make this manually or use datadisk
>>- never i can mount the filesystem on the secondary machine
> 
> 
> not "on the secondary machine", but "on *A* machine in Secondary *state*".
> just to explicitly point out one of the most common misunderstandings
> about what *you* (the administrator) think of as the primary and backup
> servers, and what *state* the cluster nodes are currently in...
> 
> 
>>An other question:
>>
>>are possible to increase the speed of syncronization? For syncing 73Gb 
>>needs 20h! So is very difficult to probe the mechanism.
> 
> 
> 73G / 20h == 73*1024*1024 k / 20*3600sec == 1063 k/sec
> this is slooow.
> I have seen sync speeds of >= 50000 k/sec == 50M/sec
> 
> so the answer obviously is yes.  how you do this depends from your
> particular hardware and configuration.
> double check sync-max please, and whether DMA is enabled for your disks, and ...
> just do your homework and find your bottleneck :)
> 
I use for each machine  two SATA disk on Intel Controller 5013C-T in 
softrware RAID 1

I have edited the original drbd.conf so, for the disk, i see this records:
sync-min    = 500k
sync-max    = 1M    # maximal average syncer bandwidth
tl-size     = 5000  # transfer log size, ensures strict write ordering
timeout     = 60    # unit: 0.1 seconds
connect-int = 10    # unit: seconds
ping-int    = 10    # unit: seconds
ko-count    = 4     # if some block send times out this many times,

I must increase sync-min to 5M and sync-max to 500M ?

Thank

Paolo Morandi




More information about the drbd-user mailing list