Red Hat Bugzilla – Bug 191863
autofs does not umount CDROM
Last modified: 2013-03-13 00:50:17 EDT
Description of problem:
I use autofs to mount CD/DVD drives on machines that does not
run X. Mounting works fine. However, the drive is never unmounted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd /misc/cd
2. cd /root
/misc/cd is not unmounted
/misc/cd should umount after the timeout.
/misc /etc/auto.misc --timeout=10
cd -fstype=auto,ro,nosuid,nodev :/dev/cdrom
Also, I cannot unmount the cd manually, neither with umount nor
(In reply to comment #0)
> Description of problem:
> I use autofs to mount CD/DVD drives on machines that does not
> run X. Mounting works fine. However, the drive is never unmounted.
If you stop the HAL daemon (service haldaemon stop) does the
problem go away?
Yes, it does.
How do I tell the hal dÃ¦mon to keep its hands
off /dev/cdrom ?
(In reply to comment #2)
> Yes, it does.
> How do I tell the hal dÃ¦mon to keep its hands
> off /dev/cdrom ?
Wish I new.
I've reported it to the HAL folks but have had no feedabck
on a resolution yet. So I'm not sure how to get this resolved.
I'll post to this BZ when I know more.
Reassigning to HAL.
Turn HAL off. autofs and hal don't mix well because HAL probes some devices to
detect media inserts. This causes autofs to mount the drive. I don't think
there is a solution here except to make autofs HAL aware. If you don't run X or
NetworkManager you should be fine turning off HAL.
In this case, it's better to turn autofs off. ;) You really don't need autofs
managing your removable media. The udev/hal combination can provide much richer
functionality for removable media than autofs was ever intended to.
So, by "turn autofs off", I really mean get rid of the entries in auto.misc that
reference removable media. Included in that list would be cdrom and the floppy
I think we can close this as NOTABUG. If you disagree, please feel free to
re-open it and explain.
Please explain to me how I obtain the same/better functionality
than autofs on an FC5 machine not running X.
If gnome-mount is the answer, I would prefer to run the machine
without the haldaemon running.
As autofs is included in FC5, and it doesn't work, I would still
call it a bug, fixable or not.
just disable HAL then if you don't need the functionality.
How would I know if I need the functionality? :-)
As long as you don't use NetworkManager or care about mounting via an X desktop
you should be fine. Of course this will become less and less true as HAL get
more deeply integrated. We are working on a way to let autofs and HAL play nice.
I just filed bug 192923 that might have some relevance with this.
(In reply to comment #14)
> I just filed bug 192923 that might have some relevance with this.
This problem is definitely HAL triggering a mount immediately
after the expire. John has put together a patch for HAL which
should resolve it.
*** Bug 192923 has been marked as a duplicate of this bug. ***
New packages should show up in testing soon. Please test and tell me if there
are any issues before I push to final. Thanks.
hal-0.5.7-3.fc5.3 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
hal-0.5.7-3.fc5.3 doesn't quite solve this problem.
When the autofs timeout has expired (10 sec. in my case),
the drive is unmounted (I can see the LED on the drive
flicker), but it is immediately mounted again.
One has to wait a couple of minutes, then the drive is unmounted
and not mounted again.
can you attach the contents of /proc/mounts? Thanks.
Created attachment 130068 [details]
Content of /proc/mounts
This is the contents of /proc/mounts
I made a script that saves the contents of /proc/mounts every two
seconds. While this script runs, the CDROM drive stays mounted.
I tested hal-0.5.7-11 from rawhide and I can confirm that it fixes
haldaemon/autofs interaction problem that I reported in bug 192923.