[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] [XCP 1.1 ISSUE] If SR gets stuck in a read only state nothing can be done with VMs.


  • To: xen-api@xxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Fri, 09 Nov 2012 21:19:50 +0400
  • Delivery-date: Fri, 09 Nov 2012 17:20:00 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

On 09.11.2012 04:20, Kigen wrote:
Hi,

Today we experienced an issue with our ReadyNAS which caused it to get
stuck in a read-only state.  Unfortunately, it seems that our only
solution is to backup the current contents of the NAS and format it.
This takes a long time to do with the size of the NAS.  So we
attempted to use XenCenter's Move, Copy or Export to get the VMs off
the NAS that were critical.   Unfortunately, this fails as it appears
that XCP always wants to modify the file regardless of the nature of
the request.

So I feel its appropriate to list this so that hopefully the next
version of Xen can work with an SR that is stuck in a read only state.
  Our simple goal was to copy the critical VMs down to local storage
and begin working on them from there.
You asking to open Pandora's box. If NAS behaves strangely, the best XCP can do - do nothing. Because there is a bunch of issues can happens to storage, every one is escalated to XCP as one or other symptom. In some cases is better to continue to operate in R/O mode, in others is better to stop any operations as soon as possible, in third is better to replug PBD and so on.

If you want fast move some of VDI's, i think, manual VHD chain copy (to something like local ext3 SR) can helps. But you need to know what you do.



_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.