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] Recovering resources from old guests

To: Caleb Call <caleb@xxxxxxxxxxx>
Subject: Re: [Xen-users] Recovering resources from old guests
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Tue, 6 Apr 2010 16:55:07 +0700
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Apr 2010 02:56:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <s2k276929711004051427v86ba0205q44dcdbaf5133bdc8@xxxxxxxxxxxxxx>
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: <s2k276929711004051427v86ba0205q44dcdbaf5133bdc8@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Apr 6, 2010 at 4:27 AM, Caleb Call <caleb@xxxxxxxxxxx> wrote:
> We currently have several old guests that we are removing from the inventory
> and recovering their resources.  I've ran in to a minor (probably very
> simple) issue.  Instead of using logical volumes like the rest of our
> guests, these ones are using tap:aio:  The main question is, is there
> anything special I need to do to reclaim the resources from these disks, or
> is it as simple as just deleting these images?

That's pretty much it. Make sure the guest is not running, then you
can delete the file images.

>  My second(ary) question is,
> what is tap:aio:?  I've been searching but have been unable to find
> anything definitive on what they are.  Is it just a disk image used by Xen,
> or is there something special about it?  How is a tap:aio: disk created,
> etc?

The image itself is basically just a raw disk image. What makes
tap:aio:/ different from file:/ (or manually creating loopback
devices) is that tap:aio is supposed to be more reliable and have
better performance, not effected by dom0 caching effect, thus reducing
possible data loss.  This is different from (for example) tap:qcow,
which uses its own (not raw) file format. See
http://wiki.xensource.com/xenwiki/blktap for details

-- 
Fajar

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