[DRBD-user] dmesg

Papp Tamás tompos at martos.bme.hu
Mon Apr 7 11:37:08 CEST 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Sorry, I wanted to send this back to the list.

tamas

-------- Original Message --------
Subject: 	Re: [DRBD-user] dmesg
Date: 	Mon, 07 Apr 2008 11:04:55 +0200

	

	
References: 	<47F66CF0.80002 at martos.bme.hu> 
<20080407082053.GA5430 at barkeeper1.linbit>



Lars Ellenberg wrote:
> On Fri, Apr 04, 2008 at 08:01:20PM +0200, Papp Tamás wrote:
>   
>> Dear All,
>>
>> I see this in dmesg many many times:
>>
>> drbd0: bm_change_bits_to: (!b) in 
>> /usr/src/drbd-8.0.11/dist/BUILD/drbd-8.0.11/drbd/drbd_bitmap.c:917
>>
>>
>> What is this? is this a problem?
>>     
>
> the visible symptoms of a race condition.
> already fixed, fix will be in 8.0.12 and 8.2.6.
> nothing to be too concerned about.
>
>   
Thank you.

Unfortunately already this is not relevant for us.

First of all, I tried to create the fs on it, after that copy data to 
it, but already the mkfs was extremely slow, even only with one node 
(without syncing).
DRBD version is 8.0.11. I went back to 0.7.25 and everything is just fine.

This is the drbd.conf, I think, it's almost a default config scenario:


global {
   usage-count yes;
}
common {
 syncer { rate 100M; }
}
resource ost-1 {
 protocol C;
 handlers {
   pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
   pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
   local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
   outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
 }
 startup {
   wait-after-sb;
 }
 disk {
   on-io-error   detach;
 }
 net {
    cram-hmac-alg "sha1";
    shared-secret "ost-1-secret";
   after-sb-0pri disconnect;
   after-sb-1pri disconnect;
   after-sb-2pri disconnect;
   rr-conflict disconnect;
 }
 syncer {
   rate 100M;
   al-extents 257;
 }
 on node1 {
   device     /dev/drbd0;
   disk       /dev/sdb1;
   address    192.168.254.1:4411;
   meta-disk  internal;
 }
 on node2 {
   device    /dev/drbd0;
   disk      /dev/sdb1;
   address   192.168.254.2:4411;
   meta-disk internal;
 }
}


Any idea?

Thank you,

tamas





More information about the drbd-user mailing list