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] Questions on qcow, qcow2 versus LVM

To: matt@xxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Questions on qcow, qcow2 versus LVM
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Wed, 30 Dec 2009 10:01:09 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Dec 2009 19:01:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5557c7d0881f6365cacb5d022142c283.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
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: <2ff3192ddfc512732cd0a6955fa51595.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <eb42866b97a96eb5bd57b22e47cde8cc.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0912240451m76d65118y5fb9a32ed63f411b@xxxxxxxxxxxxxx> <83c17d8cd6753530b00f134159151864.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0912240624hf1d0d17w658048dac8311cb5@xxxxxxxxxxxxxx> <f17de79d17fea73fa0ea0c22259f779d.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0912241358o1bdcf15bi1514f6628b86068d@xxxxxxxxxxxxxx> <aa8fed56d2dbf587df790cda9f9525de.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0912291404h24d7daeat3ea634edc368357f@xxxxxxxxxxxxxx> <5557c7d0881f6365cacb5d022142c283.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Dec 30, 2009 at 6:26 AM, Matthew Law <matt@xxxxxxxxxxxxxxxxxx> wrote:
> After this I set about trying to find which of the previous operations was
> holding the LV in the open state, so I started again with a clean lv and
> incrementally performed each operation on it and tried to remove it.  The
> error occurs after running:
>
> parted /dev/VolGroupVM/testvm mkpartfs primary ext2 0 10240
>
> So, parted is the culprit (or at least the first one to cause the
> problem).  Is there perhaps another, scriptable way to create the
> partitions on the LV?

I usually use fdisk :D
Not scriptable, but has worked great. You might also use sfdisk
(available by default), or (like you said) upgrade parted to latest
version.

-- 
Fajar

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