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

Re: [Xen-users] Stuck blkback


  • To: xen-users@xxxxxxxxxxxxx
  • From: Tom Fritz <tfritz@xxxxxxxxx>
  • Date: Fri, 12 Apr 2013 11:56:01 -0500 (CDT)
  • Delivery-date: Fri, 12 Apr 2013 16:57:06 +0000
  • Domainkey-signature: a=rsa-sha1; s=mail; d=novia.net; c=nofws; q=dns; h=received:x-authentication-warning:date:from:to:subject: in-reply-to:message-id:references:user-agent:organization:mime-version:content-type; b=HQWQn4NRVTXhuqorcdxFp03zyZUbuwsq60PTdBLUeaNUcUSN8HIFLcyWu95xlzIbS 8S0Oqmj54K17ORAv/tGQDA/NPhtHdjCmrkVyFabE/2x5IVEZ1viyWCIrS3YlHiq+CXF M4dTWkbdCVb3nRKqDE1fCDhaoLbm40YGES4GyDU=
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Greg,

We have had a few occasions in the past few months where a VPS will need a hard 
reboot.  After the
command "xm shutdown" the VM would no longer boot.  I have traced this to the 
device mapper device
having an open count of 1, and then to the fact that there is a blkback process 
running for a domain
that doesn't exist.  I'm going to go out on a limb and suggest the blkback 
device was for the VM in
question.  I can't tell if this is a symptom or cause(the trouble with the 
blkback process) however I
don't know of any way to close out that backend process without a reboot so it 
renders the LV
unusable:/  Has anybody witnessed this behavior?


Yes I have seen this a number of times om our production machines. It will render the machine unable to start/restart a VM. I have not been able to find a solution to the issue. If you figure something out I would be very interested in hearing about it.

Tom.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

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