+++ This bug was initially created as a clone of Bug #657472 +++ Description of problem: Specifying an unknown check sum type in the checksum API causes the umount/umount-all to fail. Version-Release number of selected component (if applicable): libguestfs-1.6.2-4.el6.x86_64 How reproducible: 100% Steps to Reproduce: $ guestfish -a test.img ... ><fs> checksum blabla /test libguestfs: error: checksum: unknown checksum type, expecting crc|md5|sha1|sha224|sha256|sha384|sha512 ><fs> exit libguestfs: error: umount_all: umount: /sysroot: umount: /sysroot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) Expected results: no failure when exit or umount. --------------------------- Simple reproducer from the command line: $ guestfish -N fs -m /dev/sda1 touch /test : checksum blabla /test libguestfs: error: checksum: unknown checksum type, expecting crc|md5|sha1|sha224|sha256|sha384|sha512 libguestfs: error: umount_all: umount: /sysroot: umount: /sysroot: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
Fixed upstream: http://git.annexia.org/?p=libguestfs.git;a=commitdiff;h=403ac796a5067ac558ceca2409270eb55b477299
I assume this in the currentrelease, given that it's been in modified for 1.5 years :)