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-api

RE: [Xen-API] XCP 1.0 beta - Locked VDI issue

To: Jonathon Royle <jonathon@xxxxxxxxxxxxxxxx>
Subject: RE: [Xen-API] XCP 1.0 beta - Locked VDI issue
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Fri, 31 Dec 2010 16:13:26 +0300
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Dec 2010 05:12:36 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=skdaqwGuYIwxB68JNAFIlM6W5lYR4AVDfyKkot2X/5o=; b=jYiC/aRireHEIei9eMVRXhJa9MBT9WCzzCl1ByPi4CbzmDRnQ5jXYB8+hZuK5ec+Q1 2f79p/m/cdGEoMZeFp37vC5NJVOo9JP3X6e7519G12rwvKtO9lvqNSJP5nlT7Akb2ckz zJGRvWhFm5yd+dnafrvjFrE8a91iEfnM2yyak=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=n8QQlHAkjC+vEAGyX21QqtI6GNaL1Ut75e43STnIrLR49T/D/BtceFpRXom5T5qqQj aRM+NsJ7p9lklXkW4Wcbd8FPhEgr4gQSlWpkXJm4c0BBc6bqavABu/MlHQUg5UVDXWGA FVF7nS8UZrkRbTVSCQ/efoltNmvhWCtVmQVkU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9DCB8EAC815DAA4890EDFA50240D7CF90A4DAA@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <9DCB8EAC815DAA4890EDFA50240D7CF90A4DA8@xxxxxxxxxxxxxxxxxxxxxxxxx> <1293797148.18543.44.camel@xxxxxxxxxxxxxxxx> <9DCB8EAC815DAA4890EDFA50240D7CF90A4DAA@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Oops, sorry, miss it.

Next: is SR iscsi-based? Check if corresponding volume mounted and try
to deactivate it by lvchange. (name of LV will contain VDI uuid).


В Птн, 31/12/2010 в 12:13 +0000, Jonathon Royle пишет:
> George,
> 
> Thanks for quick response.
> 
> List of created VBD is as per original post - ie only attached to intended 
> VM.  As part of initial trouble shoot I did remove all VBDs as there was 
> (from memory) an errant one.
> 
> Regards,
> 
> Jon
> 
> 
> -----Original Message-----
> From: George Shuklin [mailto:george.shuklin@xxxxxxxxx] 
> Sent: 31 December 2010 12:06
> To: Jonathon Royle
> Cc: xen-api@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-API] XCP 1.0 beta - Locked VDI issue
> 
> Try to see created vbd for this vdi (xe vbd-list vdi-uuid=UUID), some of
> them will be attached to control domain where VM was stopped. 
> 
> 
> В Птн, 31/12/2010 в 11:42 +0000, Jonathon Royle пишет:
> > First time post so hope I am using the correct list.
> > 
> >  
> > 
> > I have been trialling XCP1.0 beta for a few weeks now and have had no
> > issues until now.  If the host is ungracefully shutdown (power fail in
> > my case) then the VDI of the running VM become unusable upon host
> > restart.
> > 
> >  
> > 
> >  
> > 
> > [root@----]# xe vm-start uuid=03ed2489-49f6-eb48-0819-549c74a96269
> > 
> > Error code: SR_BACKEND_FAILURE_46
> > 
> > Error parameters: , The VDI is not available [opterr=VDI
> > fc77b366-950b-49be-90ce-2a466cf73502 already attached RW],
> > 
> >  
> > 
> > I have been able to repeat this on several occasions.
> > 
> >  
> > 
> > I have tried toolstack restart, host reboot as well as vbd-unplug
> > etc.  The only solution I have found is to use sr-forget (a bit
> > drastic) and then reintroduce the SR
> > 
> >  
> > 
> > Some config output.
> > 
> >  
> > 
> > [root@----]# xe vdi-list uuid=fc77b366-950b-49be-90ce-2a466cf73502
> > 
> > uuid ( RO)                : fc77b366-950b-49be-90ce-2a466cf73502
> > 
> >           name-label ( RW): Cacti - /
> > 
> >     name-description ( RW): System
> > 
> >              sr-uuid ( RO): 0fe9e89c-e244-5cf2-d35d-1cdca89f798e
> > 
> >         virtual-size ( RO): 8589934592
> > 
> >             sharable ( RO): false
> > 
> >            read-only ( RO): false
> > 
> >  
> > 
> > [root@----]# xe vbd-list vdi-uuid=fc77b366-950b-49be-90ce-2a466cf73502
> > 
> > uuid ( RO)             : 350d819b-ec36-faf4-5457-0a81668407f0
> > 
> >           vm-uuid ( RO): 03ed2489-49f6-eb48-0819-549c74a96269
> > 
> >     vm-name-label ( RO): Cacti
> > 
> >          vdi-uuid ( RO): fc77b366-950b-49be-90ce-2a466cf73502
> > 
> >             empty ( RO): false
> > 
> >            device ( RO):
> > 
> >  
> > 
> >  
> > 
> > Is this a known bug, is there a better solution – happy to test
> > further
> > 
> >  
> > 
> > Regards,
> > 
> >  
> > 
> > Jon
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > 
> > _______________________________________________
> > xen-api mailing list
> > xen-api@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/mailman/listinfo/xen-api
> 
> 



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>