Bug 81443 - loopback device cannot be released while running gnome
loopback device cannot be released while running gnome
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: gnome-core (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-01-09 10:37 EST by Joseph Ashby
Modified: 2015-01-07 19:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-09 12:25:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joseph Ashby 2003-01-09 10:37:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020501

Description of problem:
When running Gnome and an ISO image using the '-o loop' option is mounted and
then unmounted an error is generated that the loopback device is busy, but it
does unmount the image. However the lookbackup device has not been released and
cannot be used again until Gnome is stopped and 'losetup -d /dev/loopX' is run
to release the loopback device.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start Gnome

2.mount an ISO image. 
   mount -o loop /d0/images/1.iso /mnt/cdrom

3.unmount the ISO image.
   umount /mnt/cdrom
   ioctl: LOOP_CLR_FD: Device or resource busy
The mount list will show the ISO image is unmounted.

4. losetup will show the ISO image is still assigned to the loopback device and
cannot be released.
  losetup /dev/loop0
  /dev/loop0: [0811]:32770 (/d0/images/1.iso) offset 0, no encryption
  losetup -d /dev/loop0
  ioctl: LOOP_CLR_FD: Device or resource busy

5. Stop Gnome

6. the loopback device can now be released.
  losetup -d /dev/loop0


Additional info:
Comment 1 Havoc Pennington 2003-01-09 12:25:34 EST
This should be fixed in the next release of Advanced Workstation.

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