WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Block devices stuck in dead domain?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Block devices stuck in dead domain?
From: "John Hannfield" <hal9020@xxxxxxxxx>
Date: Tue, 10 Jun 2008 18:35:45 +0100
Delivery-date: Tue, 10 Jun 2008 10:36:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=wZU/gzOQqbg4tqM+zttXwynRYni/zaekWqWI5GHRu6c=; b=kcp2dOvp5KtFMGy/6v9L5A5WlEbItK06R0lVZisLgS9hbywe27IQB4Y/dSRtu8F3Pz Bueo4o/+dtOOM1kmnD8xx2oFBqdL0WQxrSH4jnrM6nCMBoYKmBczTKBG9jtFQEqqRAJq 411DRm/lcbhB8wWJZhMPc9StY/nutKOvMRo/I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=H8vIHPArjaAaT4X2Y62t2wrjPKBfXhkT4w+OIMI/K4bcUXUwisO5koI+gKwunjHHx3 RmB1WKJZuVYcimtzX5Q4zf9oNW/uL2oG3FxDuLLPaymPIdYo41ciijL7QEmfLMq53YM+ VLhgDlfwed5jdhFJpQgg2JQIkhkoal3OOJ7wA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I'm running xen 3.1.0 on a AMD Opteron system.
Sometimes 'xm list' hangs forever, even though 'xm info' works straight away.
Usually this happens after a guest domain dies.

The only thing I can do, to get xm responsive again, is to stop and start
xend.

/etc/init.d/xend stop
/etc/init.d/xend start

This works fine, and the existing running VM's are OK.
But for the one that died, I can't restart it because xen sees the
file systems as still in use. I get the message.

Error: Device 769 (vbd) could not be connected.
Device /dev/vg1/www.abc.com_root is mounted in a guest domain,
and so cannot be mounted now.

Even though the guest domain is no longer in the 'xm list' output.
Any idea how to tell xen that it can use this LVM volume?

Thanks,
-- 

John

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

<Prev in Thread] Current Thread [Next in Thread>