Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, 2006-07-07 at 15:59 +0100, Luciano Miguel Ferreira Rocha wrote: > On Fri, Jul 07, 2006 at 07:44:21PM +0530, Milind Dumbare wrote: > > On Fri, 2006-07-07 at 14:59 +0100, Luciano Miguel Ferreira Rocha wrote: > > > On Fri, Jul 07, 2006 at 03:14:58PM +0200, boka wrote: > > > > Hello, > > > > > > > > My config is: > > > > > > > > slackware 10.2, > > > > 2.6.17.2 kernel, > > > > latest stable drbd as a patch for kernel, > > > > three drbd devices: > > > > drbd0 - 50GB, reiserfs > > > > drbd1 - 100GB, reiserfs > > > > drbd2 - 220GB, reiserfs > > > > on divded external array with two scsi controlers. > > > > > > > > It is fresh installation - no data on discs. > > > > > > > > Is it possible that syncing drbd2 took about 12h. > > > > > > 370/(12*3600)*2^10 = 8.77 MB/s > > > > > > Appropriate, if you only have a 100 Mbps ethernet connection connecting > > > the two servers. > > > > > > Note that drbd has no way to know whether the discs have no usefull > > > data. > > > > > > If you wanted drbd to just consider the discs to have the same data, > > > there was a trick posted some times in this mailing list. > > > > Can you please repeat that trick here, as I have also faced same > > problem. I was able to find --skip-sync option (to drbdsetup) and > > write_gc.pl trick. But confused to use which. > > IIRC, it's the write_gc.pl trick. The --skip-sync disables the automatic > sync, it doesn't make drbd consider that the devices are synced. > But, what's usage of that script? is it #./write_gc.pl /dev/drbd0 1 to make both disks consistent? Or, do we need to change all four parts of generation counter (human cnt, connected cnt, aribitary cnt, primary indicator) with above usage ? Please help out. thanks -- ...Milind