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, May 06, 2004 at 01:34:05PM +0400, Eugene Crosser wrote: > On Thu, 2004-05-06 at 13:26, Lars Ellenberg wrote: > > > this is no problem, but just an explicitly requested stack backtrace > > from within the drbd_send code, which reminds us about some things we > > still have to do. it is a little bit noisy, but no problem... > > > > drbd1: Resync started as target (need to sync 212928 KB). > > > drbd0: Resync started as target (need to sync 380800 KB). > > But both being target is a problem here, isn't it? no, why? these are not host names, but device names :) so he has two devices, both sync target. > BTW, returning to the question of "sync complete" on primary lagging > after that on secondary. I have the following situation for several > *days* already! > > root at nfsa1:~# cat /proc/drbd > version: 0.7-pre6 (api:72/proto:72) > > 0: cs:Connected st:Secondary/Primary ld:Consistent > ns:0 nr:12633120 dw:12633120 dr:0 al:0 bm:784 lo:0 pe:0 ua:0 > > root at nfsa2:~# cat /proc/drbd > version: 0.7-pre6 (api:72/proto:72) > > 0: cs:SyncSource st:Primary/Secondary ld:Consistent > ns:12633120 nr:47883624 dw:47883624 dr:1788060 al:55944 bm:3836 lo:0 pe:0 ua:0 > [===================>] sync'ed:100.0% (1/1748)M > finish: 0:00:00 speed: 0 (4) K/sec > > Eugene We *think* we have fixed that one yesterday... Lars Ellenberg