bad key key in direct map mapname
Description: While scanning a direct map, autofs has found an entry key without a prefixed /.
Solution: Keys in direct maps must be full path names.
bad key key in indirect map mapname
Description: While scanning an indirect map, autofs has found an entry key that contains a /.
Solution: Indirect map keys must be simple names, not path names.
can't mount server:pathname: reason
Description: The mount daemon on the server refuses to provide a file handle for server:pathname.
Solution: Check the export table on the server.
couldn't create mount point mountpoint: reason
Description: Autofs was unable to create a mount point that was required for a mount. This problem most frequently occurs when you attempt to hierarchically mount all of a server's exported file systems.
Solution: A required mount point can exist only in a file system that cannot be mounted, which means the file system cannot be exported. The mount point cannot be created because the exported parent file system is exported read-only.
leading space in map entry entry text in mapname
Description: Autofs has discovered an entry in an automount map that contains leading spaces. This problem is usually an indication of an improperly continued map entry. For example:
fake /blat frobz:/usr/frotz
Solution: In this example, the warning is generated when autofs encounters the second line because the first line should be terminated with a backslash (\).
Description: The required map cannot be located. This message is produced only when the –v option is used.
Solution: Check the spelling and path name of the map name.
remount server:pathname on mountpoint: server not responding
Description: Autofs has failed to remount a file system that it previously unmounted.
Solution: Contact My Oracle Support for assistance. This error message is extremely rare and has no straightforward solution.
WARNING: mountpoint already mounted on
Description: Autofs is attempting to mount over an existing mount point. This message means that an internal error occurred in autofs (an anomaly).
Solution: Contact My Oracle Support for assistance. This error message is extremely rare and has no straightforward solution.