[Bug 335472] [NEW] device-mapper: remove ioctl failed: Device or resource busy

[Loïc Minier]

Public bug reported:

Hi,

While building a VM today with "ubuntu-vm-builder kvm jaunty":
...
2009-02-27 14:54:26,202 INFO     Can not write log, openpty() failed (/dev/pts not mounted?)
2009-02-27 14:54:26,282 INFO     Can not write log, openpty() failed (/dev/pts not mounted?)
2009-02-27 14:54:26,324 INFO     Can not write log, openpty() failed (/dev/pts not mounted?)
2009-02-27 14:54:27,136 INFO     Can not write log, openpty() failed (/dev/pts not mounted?)
2009-02-27 14:54:30,271 INFO     Copying to disk images
2009-02-27 14:54:49,060 INFO     Installing bootloader
2009-02-27 14:54:55,501 INFO     Unmounting target filesystem
2009-02-27 14:54:55,833 INFO     device-mapper: remove ioctl failed: Device or resource busy
2009-02-27 14:54:55,834 INFO     ioctl: LOOP_CLR_FD: Device or resource busy
2009-02-27 14:54:55,835 INFO     Cleaning up
Traceback (most recent call last):
  File "/usr/bin/ubuntu-vm-builder", line 29, in <module>
    VMBuilder.run()
  File "/usr/lib/python2.5/site-packages/VMBuilder/__init__.py", line 66, in run
    frontend.run()
  File "/usr/lib/python2.5/site-packages/VMBuilder/plugins/cli/__init__.py", line 67, in run
    vm.create()
  File "/usr/lib/python2.5/site-packages/VMBuilder/vm.py", line 469, in create
    raise e
VMBuilder.exception.VMBuilderException: Process (['kpartx', '-d', '/tmp/vmbuildervru1bq/disk0.img']) returned 1. stdout: , stderr: device-mapper: remove ioctl failed: Device or resource busy
ioctl: LOOP_CLR_FD: Device or resource busy

sudo losetup -a shows:
/dev/loop0: [fc00]:5914861 (/tmp/vmbuildervru1bq/disk0.img)

sudo kpartx -l /dev/loop0:
loop0p1 : 0 7998048 /dev/loop0 32
loop0p2 : 0 2000000 /dev/loop0 7998080

however I only have a /dev/mapper/loop0p1 (no /dev/mapper/loop0p2); I
suspect something prevented the removal of all mapped devices as it
stopped in the middle; perhaps it was still busy writing (my PC was
under another IO load when creating the vm)?  Perhaps you need to sync
after umount for instance.

/tmp/vmbuildervru1bq/disk0.img was gone at this point, "sudo kpartx -d
/dev/loop0" dropped the remaining mapper device and "sudo losetup -d
/dev/loop0" the loopback mapping.

Bye

** Affects: vm-builder (Ubuntu)
     Importance: Undecided
         Status: New

-- 
device-mapper: remove ioctl failed: Device or resource busy
https://bugs.launchpad.net/bugs/335472
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs