Error Messages Generated by automount -v

bad key key in direct map mapname

While scanning a direct map, autofs has found an entry key without a prefixed /. Keys in direct maps must be full path names.

bad key key in indirect map mapname

While scanning an indirect map, autofs has found an entry key containing a /. Indirect map keys must be simple names—not path names.

can't mount server:pathname: reason

The mount daemon on the server refuses to provide a file handle for server:pathname. Check the export table on the server.

couldn't create mount point mountpoint: reason

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. A required mount point can exist only in a file system that cannot be mounted (it 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

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

In this example, the warning is generated when autofs encounters the second line because the first line should be terminated with a backslash (\).

mapname: Not found

The required map cannot be located. This message is produced only when the -v option is used. Check the spelling and path name of the map name.

remount server:pathname on mountpoint: server not responding

Autofs has failed to remount a file system it previously unmounted.

WARNING: mountpoint already mounted on

Autofs is attempting to mount over an existing mount point. This message means an internal error occurred in autofs (an anomaly).