|Summary:||autofs apparently unhappy with "auto" filesystem type|
|Product:||[Fedora] Fedora||Reporter:||Michal Jaegermann <michal>|
|Component:||autofs||Assignee:||Ian Kent <ikent>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||8||CC:||ikent, jmoyer, triage|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-01-09 07:12:27 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Michal Jaegermann 2007-08-09 20:51:50 UTC
Description of problem: On two quite different machines I see that automount is repeatedly dropping in /var/log/messages entries like this one: automount: open_mount: (mount):cannot open mount module auto (/usr/lib64/autofs/mount_auto.so: cannot open shared object file: No such file or directory) AFAICT the reason for that noise is that one or more entries in /etc/fstab has "auto" in a filesystem field; which is allowed and can be even very appropriate. Another possibility is in one of autofs configuration files I have a line: cdrom -fstype=auto,ro,nosuid,nodev,user :/dev/cdrom which is precisely what is desired there. The above does not seem to affect automount operation at all. At least CDs with an entry like the above are getting automounted with appropriate file system types (I have around iso9660 and hfsplus samples). So it appears that for a "fix" it would be enough to kill a complaint in this particular case. Version-Release number of selected component (if applicable): autofs-5.0.2-10 autofs-5.0.1-0.rc3.33 How reproducible: all the time
Comment 1 Ian Kent 2007-08-10 03:14:35 UTC
I know about this one. I haven't got to fixing it yet. You are correct, it doesn't affect autofs operation. Ian
Comment 2 Michal Jaegermann 2007-11-21 21:04:36 UTC
> I know about this one. > I haven't got to fixing it yet. I got somewhat impatient with that for assorted reasons. It appears that 'ln -s mount_generic.so mount_auto.so' at least hides the problem. Do you know of any reasons why this could be harmful? It seems to be fine when I tried.
Comment 3 Bug Zapper 2008-04-04 13:34:38 UTC
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Comment 4 Bug Zapper 2008-11-26 07:40:04 UTC
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Bug Zapper 2009-01-09 07:12:27 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.