Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 109687 - can not umount cdrom
Summary: can not umount cdrom
Keywords:
Status: CLOSED DUPLICATE of bug 106936
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: 1
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-10 23:24 UTC by Ignacio Galmarino
Modified: 2007-11-30 22:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:59:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ignacio Galmarino 2003-11-10 23:24:14 UTC 
Description of problem:

when you insert a cdrom its automounted but when you try to umount it
you get an error message "cdrom is busy"

Fedora Core 1 on i686


How reproducible:


Steps to Reproduce:
1. Boot Fedora (Gnome)
2. Insert a cdrom in the cdrom drive
3. click on the cdrom icon and select eject
  
Additional info:

i change the inittab to "id:3:initdefault:" to boot on text mode (also
remove rhgb on grub.conf). Loging using a standar user. Startx and
everything works OK
Comment 1 Miloslav Trmac 2003-11-11 11:22:18 UTC 
Seen here too, it seems fam holding open files there again :(
Comment 2 Nick Marsh 2003-11-23 23:29:17 UTC 
Obligatory "me too". If I use the command line to mount a cd or dvd
from inside Gnome, I cannot umount it unless I change runlevels or reboot.
Comment 3 Nick Marsh 2003-11-27 08:45:17 UTC 
Here is how you can see what files were open. The only question now is
why were the files open even though I had already closed them? Perhaps
there is something wrong with file locks and read only file systems on
Fedora (just a guess)?

$ umount -v /dev/cdrom
umount: /mnt/cdrom: device is busy

$ /usr/sbin/lsof|grep cdrom
fam       3376  nmarsh   31r   DIR      22,64     2588       269
/mnt/cdrom/VIDEO_TS

Note: I was *not* in /mnt/cdrom/VIDEO_TS anymore.

# umount -vf /dev/cdrom
umount2: Device or resource busy
umount: /mnt/cdrom: device is busy

# kill 3376

# umount -v /dev/cdrom
/dev/cdrom umounted
Comment 4 Rene 2003-12-05 03:58:43 UTC 
Can't wait till this is fixed. Was trying to show a pal how 'easy'
desktop linux can be when we got bit by this bug...hehe.  = )
Comment 5 Carlos Rodrigues 2003-12-19 00:39:24 UTC 
I guess this is a duplicate for Bug #106936.
Comment 6 Alexander Larsson 2004-02-04 11:17:44 UTC 

*** This bug has been marked as a duplicate of 106936 ***
Comment 7 Martin Nielsen 2004-06-03 19:05:24 UTC 
From KDE desktop (as root), installed rpm fam-2.6.10-9.  To unmount
and eject cd disk, go to Start Applications (red fedora) > system
tools > disk management > high lite cd-rom and click on "unmount". 
Drive will unmount and disk will eject.  This works.  If just the
eject button on the cd-rom drive is pushed, then a busy lite on the
drive will show and disk will not eject.
Comment 8 Carlos Rodrigues 2004-06-04 13:24:42 UTC 
The eject button on the drive is disabled while the drive is mounted
(the drive is locked). This is normal behavior for all drive types
that support it (cdroms, zips, ...).

Well, using the disk management tool works, but isn't it easier just
to right-click on the cdrom icon, select unmount and then press the
eject button to eject it?
Comment 9 Red Hat Bugzilla 2006-02-21 18:59:56 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.