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, May 22, 2009 at 04:00:47PM -0700, Alireza Nematollahi wrote: > Hi guys, > > I have specified 30M to be my syncer rate in drbd.conf file but when I > do cat /proc/drbd, I get this: > > 0: cs:SyncSource st:Primary/Secondary ds:UpToDate/Inconsistent C r--- > ns:13008216 nr:0 dw:17701660 dr:10605873 al:1808 bm:2682 lo:52 pe:18 > ua:69 ap:0 oos:10368640 > [>....................] sync'ed: 1.2% (10125/10239)M > finish: 0:04:25 speed: 39,016 (39,016) K/sec > There are two possible ways for an out-of-sync region to become in-sync again: application WRITE (gets replicated right away, so will be in sync on both replicas once completed) or resync writes. The sync rate as set in the drbd configuration only throttles the bandwidth the resyncer is allowed to use up. The resync progress indicator in /proc/drbd also takes those blocks into account that have been "resynced" by application writes. And, it is a rought guess only, anyways. -- : 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