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] Re: cLVM on Debian/Lenny

To: Jan Kalcic <jandot@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: cLVM on Debian/Lenny
From: John Madden <jmadden@xxxxxxxxxxx>
Date: Mon, 20 Apr 2009 14:07:16 -0400
Cc: Olivier Le Cam <Olivier.LeCam@xxxxxxxxxxxxxxxxxxxxx>, Ferenc Wagner <wferi@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx>, Javier Guerra <javier@xxxxxxxxxxx>
Delivery-date: Mon, 20 Apr 2009 11:08:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49ECB001.9060202@xxxxxxxxx>
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: <49E61DED.7030607@xxxxxxxxxxxxxxxxxxxxx> <87k55kvbdn.fsf@xxxxxxxxxxxxx> <90eb1dc70904160912i5c4741c9v8385e481694159c3@xxxxxxxxxxxxxx> <49E8827B.3070305@xxxxxxxxxxxxxxxxxxxxx> <90eb1dc70904171031j6b83fa3dp76ff2f060cebe789@xxxxxxxxxxxxxx> <6b7f6eb0904171201s2cb48281h924343236b3bbb07@xxxxxxxxxxxxxx> <49EC5342.4090202@xxxxxxxxxxxxxxxxxxxxx> <49EC65CF.3020001@xxxxxxxxx> <1240235155.21421.473.camel@quagmire> <49EC8482.7020508@xxxxxxxxx> <90eb1dc70904200828p1b781433k315849f8741c1223@xxxxxxxxxxxxxx> <49ECB001.9060202@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> Now I think I can figure out that there is no difference between a
> domU
> based on a file block device on top of a cluster file system, let's
> suppose OCFS2, and a domU based on physical block device on top of LVM
> (cLVM). In both case, I am eventually able to run the domU on both
> nodes
> having data corruption. Neither OCFS2 nor cLVM with their different
> lock
> managers can provide that mechanism to assure consistency. Right? If
> yes, I would say that the best solution should always be using LVM, at
> least it provides more features.

OCFS2 is a filesystem, LVM is a volume manager.  Don't use the two
products in the same sentence unless it's to say "I formatted an LVM LV
with OCFS2 instead of ext3."  

OCFS2 will allow you to run two domU's (or dom0's, or any host for that
matter) sharing storage and writing to it at the same time without
corruption because it is a cluster filesystem.  You don't need LVM to
accomplish this, either, although you should use it too to manage the
volumes.

John




-- 
John Madden
Sr UNIX Systems Engineer
Ivy Tech Community College of Indiana
jmadden@xxxxxxxxxxx


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