[Xen-API] XCP 1 Beta - recovering from the vdi is not available

To:	xen-api@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-API] XCP 1 Beta - recovering from the vdi is not available without destroying san connection
From:	Chris Percol <chris.percol@xxxxxxxxx>
Date:	Wed, 5 Jan 2011 17:40:19 +0000
Delivery-date:	Wed, 05 Jan 2011 09:40:35 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=h5R+LLEVrkGcKVqJ1Lzw2WAR0r6Cbp+Liu1yMIErbSk=; b=BMjaeJ/ujnxZioUNKjwd1VDwB0AkOs/6+HZ7SBRoxa+iuYEHYMIV7sA9XiU+Wwz7xo qamNAijaXmpF7UQUTH4201BcsdLDJwl0OQKKYZnS2HoBmTf88Upa7gEy+4oVb0xWkNhK YIhIMF3+GUkBOjU5Y3BD5aPrCRr0RuDH/f7HU=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=D4zy1I+XUmm9Q59Vqby3BUutEZpbyT/TnsM1sugxBCV0LJN/8OO8msker2kgOvwCJl rf2WK50jzsBbjXtXGMEms/OSXdsjODa+LBFJh4GxyVUk1LsrhMN2unFo1a5/yuPaG6K/ oKWql/qIFAcE1ksOBcRcU+eRkhRvqO3Ix6QbY=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Hi,

We have been testing our xcp 1 setup connected to an iscsi san (qsan).

If we pull the plug on the system and start up the san while xcp is nearly done booting xen looses the connection to the san (as it would).

If we repair the san sr connection in xencenter all seems to go well. However, we can not start vms with the error 'the vdi is not available' from the san.

The only workaround we have found so far is to destroy the san connection and re-attach the disks (which now have no metadata).

I am hoping someone can suggest a better fix as this wouldn't be ideal in a scenario were bad stuff, like power issues, reboots the servers?

I had a look at lvchange but couldn't see a solution that would get my vms booting again and recover from 'the vdi is not available' issue.

Many thanks,

Chris

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

WARNING - OLD ARCHIVES

xen-api

[Xen-API] XCP 1 Beta - recovering from the vdi is not available without