WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Debian Etch Xen Cluster (DRBD, GNBD, OCFS2, iSCSI, Heart

To: "Mehdi AMINI" <armeni67@xxxxxxxxxxx>
Subject: Re: [Xen-users] Debian Etch Xen Cluster (DRBD, GNBD, OCFS2, iSCSI, Heartbeat?)
From: Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 23 Sep 2007 12:51:00 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Sep 2007 03:51:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47195.192.168.0.6.1190540673.squirrel@tim> (Mehdi AMINI's message of "Sun, 23 Sep 2007 11:44:33 +0200 (CEST)")
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46E6A47B.3010309@xxxxxxxx> <46E92EB0.3040209@xxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01249662@trantor> <38196.192.168.0.6.1189710359.squirrel@tim> <46EA2ACF.6050807@xxxxxxxxxxxxxxxx> <874phl7sv9.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <47195.192.168.0.6.1190540673.squirrel@tim>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux)
"Mehdi AMINI" <armeni67@xxxxxxxxxxx> writes:

> Hello,
>
>> 1) Do what you would do without xen. Throw the power switch.
>>
>> That means you have to teach stonit or heartbeat about xen and the
>> power switch becomes "xm destroy" on the other node instead of a real
>> power switch.
>
> If the network is down, you won't be able to "xm destroy" the other node.

Which would mean one of the two network cards or the cable is broken
or the node is crashed. You do use a cross over cable for the
sonit(heartbeat link, right?

In that case you have to kill the other node completly with all its
domains. You throw the power switch. With xen it is just nested. You
have a small (xm destroy) and big (real) power switch.

>> 2) Would it make sense to have a bit in the lvm headers to show that a
>> volume is active and have cluster lvm respect that bit and prevent a
>> second activation if run wihtout force?
>
> I'm not sure I understand what you mean, but your bit mean only that a
> volume is mounted or unmounted (cleanly), it won't be able to detect that
> a volume has been uncleany umounted.

You can alway mount a clean volume. Obviously.

You can also mount an unclean volume if you know the other node is
down (xm destroy) or node power turned off. Mount it with force.

Otherwise you are in a critical failure situation and don't know what
to do so you scream for an admin.

MfG
        Goswin

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users