[DRBD-user] Problem DRBD With Xen

Lars Ellenberg lars.ellenberg at linbit.com
Tue Dec 21 17:54:14 CET 2010

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, Dec 22, 2010 at 01:14:25PM -0200, gilmarlinux at agrovale.com.br wrote:

Please avoid html mail on mailing lists,
even more so if their plain text "alternative"
looks like the incomprehensible garbage below.
Anyways, I see no obvious indication of any problem here.

Maybe you have different expectations about the result of whatever it is
you are doing?

> Hello!I'm using xen with drbd lvm where the domU on drbd it applied.Maybe
> someone knows if the log below this a problem for me is not correct.

Don't refer to logs without describing what you did,
what you expected to happen, and what actually did happen.

> Dec 20
> 22:52:39 pitanga kernel: block drbd0: Resync done (total 196 sec; paused 0 sec; 102044
> K/sec)Dec 20 22:52:39 pitanga kernel: block drbd0: conn( SyncSource ->
> Connected ) pdsk( Inconsistent -> UpToDate )Dec 20 22:53:09 pitanga kernel:
> block drbd0: peer( Primary -> Secondary )Dec 20 22:53:09 pitanga kernel: block
> drbd0: peer( Secondary -> Unknown ) conn( Connected -> TearDown ) pdsk( UpToDate
> -> DUnknown )Dec 20 22:53:09 pitanga kernel: block drbd0: Creating new current
> UUIDDec 20 22:53:09 pitanga kernel: block drbd0: meta connection shut down by
> peer.

Without the knowledge about what you did and what you thought _should_
happen, the logs just show some fraction of what _did_ happen,
and there is hardly anything wrong with drbd shutting down per se, if
you (or your cluster manager) told it to.  It usually won't shut down
all by itself.

> drbd.confglobal {    usage-count no;}common {  syncer { rate 100M; }resource xen {  protocol C;  handlers {  }  startup {     wfc-timeout  15;   
> degr-wfc-timeout 20;    # 2 minutes.   
> become-primary-on both;}  disk {} 
> net {    sndbuf-size 512k;    timeout 60;    connect-init 10;   
> ping-int        10;   
> ping-timeout  5;    max-buffers 2048;   
> max-epoch-size  2048;    allow-two-primaries;    after-sb-0pri discard-zero-changes;   
> after-sb-0pri discard-least-changes;    after-sb-1pri
> discard-secondary;}syncer {rate 100M;al-extents 257;}on pitanga {  device    /dev/drbd0; 
> disk        /dev/sda7;  address
>;  meta-disk  internal;}on inga {  device    /dev/drbd0; 
> disk        /dev/sda7;  address
>;  meta-disk  internal;}} The heartbeat is configured ha.cf with auto_failback on.Thanks

: 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

More information about the drbd-user mailing list