Xen project Mailing List

On Thu, May 3, 2012 at 8:21 AM, George Shuklin <george.shuklin@xxxxxxxxx> wrote:

base copy is part of very ugly snapshot/clone model of VHD-based storage in XCP.

When you do some clone/snapshot, you getting three objects.

Old (one, which was base for cloning/snapshoting)
New
base copy, which contain readonly difference between previous state and state at the moment of operation (no 'previous', means difference with zero-filled).

So you can not rid of base copy.

... I can say usage of VHD was the most unpleasant part of XCP. Extreme low performance (compare to 'raw'), high overhead on COW copy, limitation on size of VDI (2TiB max), shifted align of every block, very annoying coalesing operations and many other stuff...
On 03.05.2012 14:46, Carlos Eduardo Tavares Terra wrote:
After sr-scan I have a new VDI named 'base copy'.
What is that? A snapshot that created another vm?
On Thu, May 3, 2012 at 7:19 AM, George Shuklin <george.shuklin@xxxxxxxxx> wrote:
If that VDI is not 'base copy' from snapshots, you can remove them manually. For NFS this is just 'remove file', for LVM - do lvdisplay, find LV and do lvremove for it. After that do xe sr-scan.

On 03.05.2012 04:30, Carlos Eduardo Tavares Terra wrote:
I am having some trouble with a ghost vdi in my environment. After some tries, i got stuck in this scenario:

[root@vmserver05 ~]# xe vdi-list sr-uuid=8bdbf594-168f-f54d-4a2a-1be70995868f

uuid ( RO) : 3c8bc8ec-eb30-4f99-8e5d-0a6a5ee3762c

name-label ( RW): cnetweb03 1

name-description ( RW):

sr-uuid ( RO): 8bdbf594-168f-f54d-4a2a-1be70995868f

virtual-size ( RO): 4294967296

sharable ( RO): false

read-only ( RO): false

uuid ( RO) : ef966e58-0343-43a6-b528-902e8cfb60ae

name-label ( RW): cnetweb03 0

name-description ( RW):

sr-uuid ( RO): 8bdbf594-168f-f54d-4a2a-1be70995868f

virtual-size ( RO): 268435456000

sharable ( RO): false

read-only ( RO): false

uuid ( RO) : 50c0034c-a838-4320-9ea1-874d9a8b6027

name-label ( RW): cnetweb03 2

name-description ( RW):

sr-uuid ( RO): 8bdbf594-168f-f54d-4a2a-1be70995868f

virtual-size ( RO): 107374182400

sharable ( RO): false

read-only ( RO): false

uuid ( RO) : 322a2176-ca29-4699-951f-c4def6f0d7fc

name-label ( RW):

name-description ( RW):

sr-uuid ( RO): 8bdbf594-168f-f54d-4a2a-1be70995868f

virtual-size ( RO): 268435456000

sharable ( RO): false

read-only ( RO): true

[root@vmserver05 ~]# xe vdi-destroy uuid=322a2176-ca29-4699-951f-c4def6f0d7fc

This operation cannot be performed because the system does not manage this VDI

vdi: 322a2176-ca29-4699-951f-c4def6f0d7fc ()

How can I destroy this vdi? He isn't displayed in XenCenter.

Thanks

--
Carlos Eduardo Tavares Terra
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--
Carlos Eduardo Tavares Terra
Red Hat Certified Engineer
Consultor em Infraestrutura de TI
GNU/Linux #413291 [http://counter.li.org]

Re: [Xen-API] Problem with ghost VDI