Bug 232818 - autofs unhappy with 'auto' file system
autofs unhappy with 'auto' file system
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: autofs (Show other bugs)
rawhide
All Linux
medium Severity low
: ---
: ---
Assigned To: Ian Kent
Brock Organ
bzcl34nup
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-18 08:25 EDT by Michal Jaegermann
Modified: 2008-04-04 13:20 EDT (History)
3 users (show)

See Also:
Fixed In Version: autofs-5.0.3-11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-04 13:20:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2007-03-18 08:25:40 EDT
Description of problem:

I am trying to use autofs with CDs and a specific file system is
not an option as various CDs I want to mount are not of a uniform
type.  So I put in a correspondig configuration file
"-fstype=auto,ro,nosuid,...".  This does work as expected but every
time when autofs starts mount I am getting:

... automount[2910]: open_mount: (mount):cannot open mount module auto
(/usr/lib/autofs/mount_auto.so: cannot open shared object file: No such file or
directory)

It appears that as things work that mythical "mount_auto.so" could be
just a "do nothing" module (although I put a corresponding line
in /etc/fstab in order to 'eject' to work without complaints).

Version-Release number of selected component (if applicable):
autofs-5.0.1-0.rc3.26

How reproducible:
always
Comment 1 Ian Kent 2007-03-18 21:20:30 EDT
(In reply to comment #0)
> ... automount[2910]: open_mount: (mount):cannot open mount module auto
> (/usr/lib/autofs/mount_auto.so: cannot open shared object file: No such file or
> directory)

I'm aware of this.

I've checked this out a couple of times and the dilemma is
if I get rid of the message then I could miss real errors.

It appears that the mount should still work OK making this
more of an annoyance than anything else. Is that correct?

Ian
Comment 2 Michal Jaegermann 2007-03-18 22:14:13 EDT
> It appears that the mount should still work OK making this
> more of an annoyance than anything else. Is that correct?

Correct.  That is why severity was set to "low" (there is no
"annoyance" among choices :-).

That is also why I suggested supplying "do nothing and pass"
mount_auto.so module which would catch that.  What real errors
would be missed that way?  I gather that you worry about mistyped
file system types.  Those will be not "auto".

I indeed may miss reasons why such cleanup would be detrimental.

Comment 3 Ian Kent 2007-03-18 22:31:11 EDT
(In reply to comment #2)
> > It appears that the mount should still work OK making this
> > more of an annoyance than anything else. Is that correct?
> 
> Correct.  That is why severity was set to "low" (there is no
> "annoyance" among choices :-).

OK, so it is what I thought.

> 
> That is also why I suggested supplying "do nothing and pass"
> mount_auto.so module which would catch that.  What real errors
> would be missed that way?  I gather that you worry about mistyped
> file system types.  Those will be not "auto".
> 
> I indeed may miss reasons why such cleanup would be detrimental.

Maybe I'm wrong, I'll look again.

Ian
Comment 4 Bug Zapper 2008-04-04 02:34:41 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are 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.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 5 Ian Kent 2008-04-04 13:20:55 EDT
This annoying message no longer appears.

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