Bug 657499 - checksum: wrong check sum type causes umount to fail
checksum: wrong check sum type causes umount to fail
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: libguestfs (Show other bugs)
rawhide
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Richard W.M. Jones
Fedora Extras Quality Assurance
:
Depends On:
Blocks: 657472
  Show dependency treegraph
 
Reported: 2010-11-26 04:39 EST by Richard W.M. Jones
Modified: 2012-06-17 17:21 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 657472
Environment:
Last Closed: 2012-06-17 17:21:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2010-11-26 04:39:46 EST
+++ 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))
Comment 2 Cole Robinson 2012-06-17 17:21:46 EDT
I assume this in the currentrelease, given that it's been in modified for 1.5 years :)

Note You need to log in before you can comment on or make changes to this bug.