Chapter 20. Mounting file systems on demand
As a system administrator, you can configure file systems, such as NFS, to mount automatically on demand.
20.1. The autofs service Copy linkLink copied to clipboard!
The autofs
service can mount and unmount file systems automatically (on-demand), therefore saving system resources. It can be used to mount file systems such as NFS, AFS, SMBFS, CIFS, and local file systems.
One drawback of permanent mounting using the /etc/fstab
configuration is that, regardless of how infrequently a user accesses the mounted file system, the system must dedicate resources to keep the mounted file system in place. This might affect system performance when, for example, the system is maintaining NFS mounts to many systems at one time.
An alternative to /etc/fstab
is to use the kernel-based autofs
service. It consists of:
- A kernel module that implements a file system.
- A user-space service that performs all of the other functions.
For more information, see the autofs(8)
man page on your system.
20.2. The autofs configuration files Copy linkLink copied to clipboard!
This section describes the usage and syntax of configuration files used by the autofs
service.
The master map file
The autofs
service uses /etc/auto.master
(master map) as its default primary configuration file. This can be changed to use another supported network source and name using the autofs
configuration in the /etc/autofs.conf
configuration file in conjunction with the Name Service Switch (NSS) mechanism.
All on-demand mount points must be configured in the master map. Mount point, host name, exported directory, and options can all be specified in a set of files (or other supported network sources) rather than configuring them manually for each host.
The master map file lists mount points controlled by autofs
, and their corresponding configuration files or network sources known as automount maps. The format of the master map is:
mount-point map-name options
mount-point map-name options
The variables used in this format are:
- mount-point
-
The
autofs
mount point; for example,/mnt/data
. - map-file
- The map source file, which contains a list of mount points and the file system location from which those mount points should be mounted.
- options
- If supplied, these apply to all entries in the given map, if they do not themselves have options specified.
Example 20.1. The /etc/auto.master file
The following is a sample line from /etc/auto.master
file:
/mnt/data /etc/auto.data
/mnt/data /etc/auto.data
Map files
Map files configure the properties of individual on-demand mount points.
The automounter creates the directories if they do not exist. If the directories exist before the automounter was started, the automounter will not remove them when it exits. If a timeout is specified, the directory is automatically unmounted if the directory is not accessed for the timeout period.
The general format of maps is similar to the master map. However, the options field appears between the mount point and the location instead of at the end of the entry as in the master map:
mount-point options location
mount-point options location
The variables used in this format are:
- mount-point
-
This refers to the
autofs
mount point. This can be a single directory name for an indirect mount or the full path of the mount point for direct mounts. Each direct and indirect map entry key (mount-point) can be followed by a space separated list of offset directories (subdirectory names each beginning with/
) making them what is known as a multi-mount entry. - options
-
When supplied, these options are appended to the master map entry options, if any, or used instead of the master map options if the configuration entry
append_options
is set tono
. - location
-
This refers to the file system location such as a local file system path (preceded with the Sun map format escape character
:
for map names beginning with/
), an NFS file system or other valid file system location.
Example 20.2. A map file
The following is a sample from a map file; for example, /etc/auto.misc
. To use this map file for mounting under /misc
, add the following to the master map file /etc/auto.master
:
/misc /etc/auto.misc
/misc /etc/auto.misc
The /etc/auto.misc file contains:
payroll -fstype=nfs4 personnel:/exports/payroll sales -fstype=xfs :/dev/hda4
payroll -fstype=nfs4 personnel:/exports/payroll
sales -fstype=xfs :/dev/hda4
The first column in the map file indicates the autofs
mount point: sales
and payroll
from the server called personnel
. The second column indicates the options for the autofs
mount. The third column indicates the source of the mount.
Following the given configuration, the autofs
mount points will be /home/payroll
and /home/sales
. The -fstype=
option is often omitted and is not needed if the file system is NFS, including mounts for NFSv4 if the system default is NFSv4 for NFS mounts.
Using the given configuration, if a process requires access to an autofs
unmounted directory such as /home/payroll/2006/July.sxc
, the autofs
service automatically mounts the directory.
The amd map format
The autofs
service recognizes map configuration in the amd
format as well. This is useful if you want to reuse existing automounter configuration written for the am-utils
service, which has been removed from Red Hat Enterprise Linux.
However, Red Hat recommends using the simpler autofs
format described in the previous sections.
For more information, see the: * autofs(5)
, autofs.conf(5)
, and auto.master(5)
man pages on your system * /usr/share/doc/autofs/README.amd-maps
file
20.3. Configuring autofs mount points Copy linkLink copied to clipboard!
Configure on-demand mount points by using the autofs
service.
Prerequisites
Install the
autofs
package:dnf install autofs
# dnf install autofs
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Start and enable the
autofs
service:systemctl enable --now autofs
# systemctl enable --now autofs
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
-
Create a map file for the on-demand mount point, located at
/etc/auto.identifier
. Replace identifier with a name that identifies the mount point. - In the map file, enter the mount point, options, and location fields as described in The autofs configuration files section.
- Register the map file in the master map file, as described in The autofs configuration files section.
Allow the service to re-read the configuration, so it can manage the newly configured
autofs
mount:systemctl reload autofs.service
# systemctl reload autofs.service
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Try accessing content in the on-demand directory:
ls automounted-directory
# ls automounted-directory
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
20.4. Configuring autofs to use ldap for storing and retrieving automount maps Copy linkLink copied to clipboard!
You can configure the autofs
service to retrieve automount maps stored in an LDAP directory.
Prerequisites
-
The
autofs
andopenldap
packages are installed. - A Kerberos-capable service is running for secure authentication.
Procedure
-
To configure LDAP access, modify the
/etc/openldap/ldap.conf
file. Ensure that theBASE
andURI
options are set to reflect the appropriate server and base for locating automount entries. In the
/etc/autofs.conf
file configure the LDAP schema for automount maps. By default,autofs
will check the commonly used schemas in the order given in the configuration file:Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou can also set these values explicitly to marginally reduce LDAP queries. You can write the attributes in both lower and upper cases in the
/etc/autofs.conf
file.The most recently established schema for storing automount maps in LDAP is described by the
rfc2307bis
draft. To use this schema, configure it in the/etc/autofs.conf
file by uncommenting and setting the appropriate value for theldap_schema
option. For example, if you are using a non-standard schema or need to override the default behavior, you can specify the relevant schema attributes in the/etc/autofs.conf
file. The following values correspond to commonly used schema settings such as those from therfc2307bis
draft:default_map_object_class = automountMap default_entry_object_class = automount default_map_attribute = automountMapName default_entry_attribute = automountKey default_value_atrribute = automountInformation
default_map_object_class = automountMap default_entry_object_class = automount default_map_attribute = automountMapName default_entry_attribute = automountKey default_value_atrribute = automountInformation
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note that the autofs automatically detects standard schemas, and specifying these settings is typically only necessary in custom or mixed-schema environments. If used, only one complete set of schema definitions should be active.
If you choose to specify a custom schema in the configuration, ensure that only one complete set of schema-related entries is active. Comment out any other to avoid conflicts. In the
rfc2307bis
schema, theautomountKey
attribute replaces thecn
attribute used in the olderrfc2307
schema. The following is an example of a corresponding LDAP Data Interchange Format (LDIF) configuration:Copy to Clipboard Copied! Toggle word wrap Toggle overflow To allow authentication from an LDAP server, edit the
/etc/autofs_ldap_auth.conf
file:-
Change
authrequired
to yes. Set the principal to the Kerberos host principal for the LDAP server,
host/FQDN@REALM
. The principal name is used to connect to the directory as part of GSS client authentication:Copy to Clipboard Copied! Toggle word wrap Toggle overflow For more information about host principal, see Using canonicalized DNS host names in IdM. You can also run
klist -k
to get the exact host principal information.
-
Change
20.5. Automounting NFS server user home directories with autofs service Copy linkLink copied to clipboard!
Configure the autofs service to mount user home directories automatically.
Prerequisites
- The autofs package is installed.
- The autofs service is enabled and running.
Procedure
Define the mount point and the local automount map by editing the
/etc/auto.master
file on the server where you want to mount user home directories, and add:/home /etc/auto.home
/home /etc/auto.home
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the local automount map file
/etc/auto.home
on the server where you need to mount user home directories, and add:* -fstype=nfs,rw,sync host.example.com:/home/&
* -fstype=nfs,rw,sync host.example.com:/home/&
Copy to Clipboard Copied! Toggle word wrap Toggle overflow You can skip
fstype
parameter, as it isnfs
by default. For more information, seeautofs(5)
man page on your system.Reload the
autofs
service:systemctl reload autofs
# systemctl reload autofs
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
20.6. Overriding or augmenting autofs site configuration files Copy linkLink copied to clipboard!
It is sometimes useful to override site defaults for a specific mount point on a client system.
Initial conditions:
For example, consider the following conditions:
-
nsswitch
tells autofs which services to check for maps. -
The map you want to augment or add to is named
auto.home
. The
auto.home
map is stored inldap
and the/etc/nsswitch.conf
has the following directive:automount: files ldap
automount: files ldap
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The
/etc/auto.master
map file contains:/home /etc/auto.home
/home /etc/auto.home
Copy to Clipboard Copied! Toggle word wrap Toggle overflow The map /etc/auto.home` file contains:
* fileserver.example.com:/export/home/&
* fileserver.example.com:/export/home/&
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Using plus map inclusion:
To read the centrally managed auto.home
map through nsswitch
, remove the the wildcard map entry * fileserver.example.com:/export/home/&
from the local /etc/auto.home
file and replace it with +auto.home
.
Plus map inclusion can only be used in local maps. When autofs
encounters the files
source through a plus map inclusion, it skips it if the included map name is identical to the map currently being read. In this case, since both are auto.home
, autofs
proceeds to the next source defined in nsswitch.conf
, which is ldap
. If a wildcard map entry is present in the map, it does not affect the directory listing, even when browse mode is enabled. This is because autofs
does not know what the wildcard might match when a lookup is done. As a result, it cannot create mount point directories in advance.
Overriding or Adding Entries
To override or add specific entries locally, place them before the +auto.home
line in /etc/auto.home
. For example the /etc/auto.home
file would look like:
mydir someserver:/export/mydir +auto.home
mydir someserver:/export/mydir
+auto.home
To display local entries like mydir when listing /home, enable browse mode by setting browse_mode = yes in /etc/autofs.conf. Wildcard entries (like *) do not appear in directory listings unless accessed.
20.7. Using systemd.automount to mount a file system on-demand with /etc/fstab Copy linkLink copied to clipboard!
Mount a file system on-demand using the automount systemd units when mount point is defined in /etc/fstab
. You have to add an automount unit for each mount and enable it.
Procedure
Add desired fstab entry as documented in Persistently mounting file systems. For example:
/dev/disk/by-id/da875760-edb9-4b82-99dc-5f4b1ff2e5f4 /mount/point xfs defaults 0 0
/dev/disk/by-id/da875760-edb9-4b82-99dc-5f4b1ff2e5f4 /mount/point xfs defaults 0 0
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Add
x-systemd.automount
to the options field of entry created in the previous step. Load newly created units so that your system registers the new configuration:
systemctl daemon-reload
# systemctl daemon-reload
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Start the automount unit:
systemctl start mount-point.automount
# systemctl start mount-point.automount
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Check that
mount-point.automount
is running:systemctl status mount-point.automount
# systemctl status mount-point.automount
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check that automounted directory has desired content:
ls /mount/point
# ls /mount/point
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
For more information, see Managing systemd
20.8. Using systemd.automount to mount a file system on-demand with a mount unit Copy linkLink copied to clipboard!
Mount a file system on-demand using the automount systemd units when mount point is defined by a mount unit. You have to add an automount unit for each mount and enable it.
Procedure
Create a mount unit. For example:
mount-point.mount [Mount] What=/dev/disk/by-uuid/f5755511-a714-44c1-a123-cfde0e4ac688 Where=/mount/point Type=xfs
mount-point.mount [Mount] What=/dev/disk/by-uuid/f5755511-a714-44c1-a123-cfde0e4ac688 Where=/mount/point Type=xfs
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Create a unit file with the same name as the mount unit, but with extension
.automount
. Open the file and create an
[Automount]
section. Set theWhere=
option to the mount path:[Automount] Where=/mount/point [Install] WantedBy=multi-user.target
[Automount] Where=/mount/point [Install] WantedBy=multi-user.target
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Load newly created units so that your system registers the new configuration:
systemctl daemon-reload
# systemctl daemon-reload
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enable and start the automount unit instead:
systemctl enable --now mount-point.automount
# systemctl enable --now mount-point.automount
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Check that
mount-point.automount
is running:systemctl status mount-point.automount
# systemctl status mount-point.automount
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check that automounted directory has desired content:
ls /mount/point
# ls /mount/point
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
For more information, see Managing systemd