From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kirk Allan" Subject: losetup -d fails when domU is destroyed Date: Mon, 08 May 2006 09:24:26 -0600 Message-ID: <445F0E4A.39DB.0076.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I do not see this happen very often, but every once in a while after a = domU is destroyed the loop device is still in use. From the /var/log/messa= ges file I see: May 8 08:54:00 kdell logger: /etc/xen/scripts/block: remove XENBUS_PATH=3D= backend/vbd/3/768 In the xen-hotplug.log there is an entry =20 ioctl: LOOP_CLR_FD: Device or resource busy It appears that when the /etc/xen/scripts/block script goes to remove the = device with the losetup -d =93$node=94 that the device is still busy and = the command fails. But by the time you can enter losetup -d /dev/ from the command line, the device is no longer busy and the command = succeeds. As a test I modified the /etc/xen/scripts/block script to sleep 1 and try = the losetup -d again if the first try failed. After many attempts to = cause the problem, it finally happened. The first losetup -d failed and = the second succeeded. Although this worked, it doesn't seem to be the = correct solution to the underlying problem. Any help or guidance would = greatly be appreciated. Thanks, Kirk