[Xen-API] Re: xen-api Digest, Vol 56, Issue 4

[Chris Percol <chris.percol@xxxxxxxxx>]

Jon,

Thanks, I had read over your message and notice the issue was unresolved.

Let me know how you get on and I will do the same.

Cheers,

Chris

On Wed, Jan 5, 2011 at 8:23 PM, Jonathon Royle <jonathon@xxxxxxxxxxxxxxxx> wrote:

Chris,

FYI - I reported the same issue using a local ext SR (see XCP 1.0 beta - Locked VDI issue) and have yet to resolve.

I intend to do some more testing including comparing to Xenserver 5.6 FP1

Regards,

Jon




---
------------------------------

Message: 2
Date: Wed, 5 Jan 2011 17:40:19 +0000
From: Chris Percol <chris.percol@xxxxxxxxx>
Subject: [Xen-API] XCP 1 Beta - recovering from the vdi is not
        available without destroying san connection
To: xen-api@xxxxxxxxxxxxxxxxxxx
Message-ID:
        <AANLkTik5zvtq+a1nFoORVxccTz4MnhkPPZwet1HjaiEZ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

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