Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jul 22, 2008 at 10:14 PM, Patrick Coleman <blinken at gmail.com> wrote:
> On Tue, Jul 22, 2008 at 6:01 PM, Lars Ellenberg
> <lars.ellenberg at linbit.com> wrote:
>> On Tue, Jul 22, 2008 at 05:03:23PM +0800, Patrick Coleman wrote:
<snip>
Replying to my own post, sorry. I've just noticed the following
interesting thing in the kernel log:
Taking the log from the resync that just finished:
drbd0: receiver (re)started
drbd0: conn( Unconnected -> WFConnection )
drbd0: Handshake successful: Agreed network protocol version 88
drbd0: conn( WFConnection -> WFReportParams )
drbd0: Starting asender thread (from drbd0_receiver [9371])
drbd0: data-integrity-alg: <not-used>
drbd0: Becoming sync target due to disk states.
drbd0: bm_set was 781246677, corrected to 782082361.
/usr/src/modules/drbd8/drbd/drbd_receiver.c:2144
drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT )
pdsk( DUnknown -> UpToDate )
drbd0: Writing meta data super block now.
drbd0: conn( WFBitMapT -> WFSyncUUID )
drbd0: helper command: /sbin/drbdadm before-resync-target
drbd0: conn( WFSyncUUID -> SyncTarget )
drbd0: Began resync as SyncTarget (will sync 3128329444 KB [782082361
bits set]).
drbd0: Writing meta data super block now.
drbd0: Resync done (total 27906 sec; paused 0 sec; 112100 K/sec)
drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate )
drbd0: bm_set was 0, corrected to 782082361.
/usr/src/modules/drbd8/drbd/drbd_worker.c:675
drbd0: helper command: /sbin/drbdadm after-resync-target
drbd0: cs:Connected rs_left=782082361 > rs_total=0 (rs_failed 0)
drbd0: Writing meta data super block now.
and /proc/drbd:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
phil at fat-tyre, 2008-05-30 12:59:17
0: cs:Connected st:Secondary/Primary ds:UpToDate/UpToDate C r---
ns:0 nr:1001628124 dw:2123051180 dr:2008 al:1 bm:259638 lo:0 pe:0
ua:0 ap:0 oos:3128329444
I was looking at the line in the log where it says "bm_set was 0,
corrected to 78208236". 78208236*4K = 3128329444K, which is the oos
value.
-Patrick
--
http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting