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] High availability and live migration with just LVMand ha

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] High availability and live migration with just LVMand hardware fencing
From: Bart Coninckx <bart.coninckx@xxxxxxxxxx>
Date: Mon, 24 May 2010 20:00:21 +0200
Cc: Frank S Fejes III <frank@xxxxxxxxx>, John Madden <jmadden@xxxxxxxxxxx>
Delivery-date: Mon, 24 May 2010 11:01:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BFAB77F.3060301@xxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <201005191146.18169.bart.coninckx@xxxxxxxxxx> <AANLkTilTE8J1QWZUJ1cAe6JPhFgbyX9IMaq6ZuvQ5Qpj@xxxxxxxxxxxxxx> <4BFAB77F.3060301@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.4 (Linux/2.6.31.12-0.2-desktop; KDE/4.3.5; x86_64; ; )
On Monday 24 May 2010 19:29:35 John Madden wrote:
> > John, I'm interested as to why you feel this is unsafe and what bad
> > experiences you may have had doing shared lvm in a manual (ie,
> > non-clvm) fashion.  In clusters of up to six Xen hosts per iscsi
> > target I've been using a combination of scripted lvchange/lvscan
> > commands in lvm wrappers and have never yet run into corruption.  As
> > far as I'm aware, there's nothing magical that clvm is doing under the
> > covers besides locking and if all lvm commands are run via the
> > "clustered" wrappers then the metadata should not be changing
> > unexpectedly.
> 
> (Btw, I'm not a LVM expert or anything.)
> 
> If you carefully coordinate changes to the metadata and, for example,
> reload the data on all cluster members on every change, I think you
> would be ok.  CLVM takes care of all this for you and uses locking to
> ensure changes on one node can't clash with other nodes.
> 
> John
> 

Quite interesting point of view, since it is so different from the one of 
authors commenting before ...
This is somewhat difficult in regards to taking decisions on setups: one party 
says "don't", the other says "do".

Rgds,


Bart

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

<Prev in Thread] Current Thread [Next in Thread>