This chapter explains error messages generated during NFS mounting and by the automounter. It contains these sections:
|/etc/mtab: No such file or directory|
|mount: ... already mounted|
|mount: ... Block device required|
The mount command assumes you are doing a local mount unless it sees a colon in the file system name or the file system type is nfs in /etc/fstab. See fstab(4).
|mount: ... not found in /etc/fstab|
searches /etc/fstab for a line that has a directory name field of /krypton.src. If it finds an entry, such as this,
it mounts as if you had given this command:
If you see this message, it means the argument you gave mount is not in any of the entries in /etc/fstab.
|/etc/fstab: No such file or directory|
|mount: ... not in hosts database|
|mount: directory path must begin with a slash (/).|
|mount: ... server not responding: RPC: Port mapper failure|
This should produce a list of registered program numbers. If it does not, start the portmap daemon again. Note that starting the portmap daemon again requires that you kill and restart inetd(1M), ypbind(1M), and ypserv(1M). ypbind is active only if you are using the NIS service. The ypserv daemon only runs on NIS servers. See network(1M) for information about how to stop and restart daemons.
There are two methods for dealing with a server that is inactive or whose portmap daemon is not responding. You could reboot the server or you perform these commands:
If you cannot rlogin to the server, but the server is operational, check your network connection by trying rlogin to some other system. Also check the server's network connection.
|mount: ... server not responding: RPC: Program not registered|
Go to the server and be sure that /usr/etc/rpc.mountd exists and that an entry appears in /etc/inetd.conf exactly like this (shown wrapped):
Give the command ps –de to be sure that the internet daemon (inetd) is running. If you had to change /etc/inetd.conf, give this command:
This command informs inetd that you have changed /etc/inetd.conf.
|mount: ... No such file or directory|
and check for file systems exported without the nohide option.
|mount: not in export list for ...|
If the file system you want is not in the list, or your host name or network group name is not in the user list for the file system, log in to the server and check the /etc/exports file for the correct file system entry. A file system name that appears in the /etc/exports file but not in the output from showmount(1M) indicates that you need to run exportfs(1M).
|mount: ... Permission denied|
|mount: ... Not a directory|
|mount: ... You must be root to use mount|
The following error messages are likely to be displayed if the automounter fails and the verbose option is on (automount(1M) –v option). Below each error message is a description of the probable cause of the problem.
|no mount maps specified|
|mapname: Not found|
|leading space in map entry entry text in mapname|
In this example, the warning is generated when the automounter encounters the second line, because the first line should be terminated with a backslash (\).
|bad directory directory in indirect map mapname|
|bad directory directory in direct map mapname|
|NIS bind failed|
|Couldn't create mountpoint mountpoint: reason|
|WARNING: mountpoint already mounted on|
|server:pathname already mounted on mountpoint|
|can't mount server:pathname: reason|
|remount server:pathname on mountpoint: server not responding|
|WARNING: mountpoint not empty|
|WARNING: default option "option" ignored for map mapname|
|option ignored for directory in mapname|
|bad entry in map mapname "directory" map mapname, directory directory: bad|
|Can't get my address|
|Cannot create UDP service|
|couldn't create pathname: reason|
|Can't mount mountpoint: reason|
|Can't update pathname|
This is an advisory message only. The automounter has received a SIGTERM (has been killed) and is exiting.
|WARNING: pathname: line line_number: bad entry|
|server:pathname no longer mounted|
|trymany: servers not responding: reason|
|server:pathname – linkname : dangerous symbolic link|
|host server not responding|
|Mount of server:pathname on mountpoint: reason|
|pathconf: server: server not responding|
|pathconf: no info for server:pathname|
|hierarchical mountpoints: pathname1 and pathname2|
|mountpoint: Not a directory|
|dir mountpoint must start with '/'|
|hostname: exports: rpc_err|
|nfscast: cannot send packet: reason|
|nfscast: cannot receive reply: reason|
|nfscast:select: reason Cannot create socket for nfs: rpc_err|
|NFS server (pid@mountpoint) not responding; still trying|
This section describes the error messages that may be generated from commands used to administer the CacheFS file system.
This section gives detailed descriptions of the CacheFS cfsadmin command failures that generate error messages.
|cfsadmin: must be run by root|
|cfsadmin: Cache name is in use and cannot be modified.|
|cfsadmin: cachepath already exists.|
|cfsadmin: creating labelpath failed.|
In each case, the system error is given in errmsg.
|cfsadmin: create resource failed: errmsg|
|cfsadmin: Cache cachedir is in use and cannot be modified.|
|cfsadmin: Cache size cannot be reduced, maxblocks current p%, requested n%|
|cfsadmin: Cache size cannot be reduced, maxfiles current p% requested n%|
|cfsadmin: cacheid is not a valid cache id.|
|cfsadmin: lowblocks can't be >= hiblocks.|
|cfsadmin: lowfiles can't be >= hifiles.|
|cfsadmin: Could not open resource: errmsg, run fsck|
|cfsadmin: Could not read cache_usage, val, run fsck|
|cfsadmin: Could not open option file optpath|
|cfsadmin: Could not read option file optpath|
|cfsadmin: Reading cachelabel failed.|
The above messages occur when the cache label file is not a regular file or the label contains the incorrect cache version. The system error is given in errmsg.
|cfsadmin: Could not open resource: errmsg, run fsck|
|cfsadmin: Resource file has wrong size cursize expected, run fsck|
|cfsadmin: Could not write cache_usage, val, run fsck|
|cfsadmin: Could not write file, val, run fsck|
This section gives detailed descriptions of the CacheFS mounting failures that generate error messages.
mount_cachefs(1M) is normally executed from mount(1M).
|mount_cachefs: must be run by root|
|mount_cachefs: mount failed, options do not match.|
|mount_cachefs: suid and nosuid are mutually exclusive|
|mount_cachefs: rw and ro are mutually exclusive|
|mount_cachefs: acregmin cannot be greater than acregmax|
|mount_cachefs: acdirmin cannot be greater than acdirmax|
|mount_cachefs: only one of non-shared or write-around may be specified|
This section gives detailed descriptions of the CacheFS unmounting failures that generate error messages.
umount_cachefs(1M) is normally executed from umount(1M).
|umount_cachefs: must be run by root|
|umount_cachefs: warning: dir not in mtab|
|umount_cachefs: could not exec /sbin/umount on back file system errmsg|