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

RE: [Xen-devel] Making snapshot of logical volumes handling HVM domUcauses OOPS and instability


  • To: "Scott Garron" <xen-devel@xxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Mon, 13 Sep 2010 10:15:28 +1000
  • Cc:
  • Delivery-date: Sun, 12 Sep 2010 17:16:18 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: ActSq0XqML4pHG24QT2ZcX1Iwz/pYAALVQKA
  • Thread-topic: [Xen-devel] Making snapshot of logical volumes handling HVM domUcauses OOPS and instability

> > Another thing I notice, which might be of help to people who
> > understand this better then I do, in my backup-script, sometimes
step
> > "5" fails because the domU hasn't noticed the device is attached
> > again when I try to mount it. The domU-commands are run using
> > SSH-connections.
> 
>       That probably just has to do with variations in how long it
takes
> the guest kernel to poll or be notified of device changes, and how
long
> it takes for its udev to create the device files and whatnot.
> Introducing some sanity checks or just a longer delay in your backup
> script would likely get around that problem.  (I could be wrong,
though)
> 

I found that too. I just put the mount in a loop, breaking out when then
device actually appears in the DomU. It's just a timing thing and I
don't think its relevant to the problem at hand.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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