Well, the main question is 'does this really need?'. Base copy VDIs is a
normal (but, yes, ugly) operational state for XCP. You can rid off them
by using only 'fresh' disks (e.g. copy instead of cloning, no snapshots).
On 03.05.2012 17:16, Carlos Eduardo Tavares Terra wrote:
So... in this case
So... in this case must I move the only VM in this SR to another SR and
reformat the first SR?
Is there any way to do this without downtime?
On Thu, May 3, 2012 at 8:21 AM, George Shuklin wrote:
> base copy is part of very ugly snapshot/clone model of VHD-based storage
> in XCP.
>
> When you do
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 oper
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 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, f
After sr-scan, one more ghost is displayed, named 'base copy':
# xe sr-scan uuid=8bdbf594-168f-f54d-4a2a-1be70995868f
# xe vdi-list sr-uuid=8bdbf594-168f-f54d-4a2a-1be70995868f
uuid ( RO): 3c8bc8ec-eb30-4f99-8e5d-0a6a5ee3762c
name-label ( RW): cnetweb03 1
name-descrip
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
