Red Hat Bugzilla – Bug 657472
checksum: wrong check sum type causes umount to fail
Last modified: 2015-09-27 22:27:37 EDT
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):
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
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))
no failure when exit or umount.
Upstream fix is here:
Fix included in the rebase.
$ guestfish -N fs:ext2 -m /dev/sda1 -- touch /test : checksum blabla /test
The umount error has gone away upon exit.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The guestfish checksum command contained a file descriptor that was not closed properly in an error path. If the checksum command resulted in an error, this would later prevent the file system from being unmounted with either umount or umount-all. The file descriptor is now closed properly on the error path, so an error in checksum no longer causes problems unmounting file systems.
This is fine, thanks.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.