Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jun 11, 2008 at 12:57:11PM +0200, Norbert Tretkowski wrote:
> Am Mittwoch, den 11.06.2008, 12:35 +0200 schrieb Norbert Tretkowski:
> > Neither enabling data-integrity-alg, nor disabling TOE on both network
> > cards helps.
>
> Okay, maybe it's just a misunderstanding on my side, this is the syslog
> output:
>
> Jun 11 12:04:18 localhost kernel: drbd0: conn( Connected -> VerifyS )
> Jun 11 12:13:12 localhost kernel: drbd0: Out of sync: start=98873208, size=8 (sectors)
> Jun 11 12:36:44 localhost kernel: drbd0: Online verify done (total 1945 sec; paused 0 sec; 90716 K/sec)
> Jun 11 12:36:44 localhost kernel: drbd0: conn( VerifyS -> Connected )
> Jun 11 12:36:44 localhost kernel: drbd0: Writing the whole bitmap, due to failed kmalloc
> Jun 11 12:36:44 localhost kernel: drbd0: writing of bitmap took 6 jiffies
> Jun 11 12:36:44 localhost kernel: drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
>
> What's confusing me here is the second line, which tells me there's an
> out of sync block, and the last line, which tells me there were 0 KB
> marked out of sync.
which exact version of drbd?
do you start verify on secondary or on primary?
context:
there has been a race in the verify code where it could report
in-flight io as out-of sync. once the in-flight hits the other
node, it gets marked as in sync again. it should be fixed in 8.2.6
in any case, if any application write hits the same block after it has
been verified as out-of-sync, it will be set in-sync again, obviously.
so this may be what you observe.
--
: Lars Ellenberg http://www.linbit.com :
: DRBD/HA support and consulting sales at linbit.com :
: LINBIT Information Technologies GmbH Tel +43-1-8178292-0 :
: Vivenotgasse 48, A-1120 Vienna/Europe Fax +43-1-8178292-82 :
__
please don't Cc me, but send to list -- I'm subscribed