RH134 - ch11s03

Bookmark this page

P 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Automounting Network Storage with NFS

Install the necessary package: autofs.
Create a master map file in /etc/auto.master.d/file.autofs.
Create a map file for accessing the NFS share: /etc/auto.name.
- Direct maps.
- Indirect maps.
- Indirect maps using wildcards.
Start and enable the autofs service using systemctl.

Objectives

After completing this section, students should be able to:

Describe the benefits of using the automounter.
Automount NFS shares using direct and indirect maps, including wildcards.

Mounting NFS shares with the automounter

Automounting NFS shares

The automounter is a service (autofs) that can automatically mount NFS shares "on demand," and will automatically unmount NFS shares when they are no longer being used.

Automounter benefits

Users do not need to have root privileges to run the mount/umount commands.
NFS shares configured in the automounter are available to all users on the machine, subject to access permissions.
NFS shares are not permanently connected like entries in /etc/fstab, freeing network and system resources.
The automounter is configured entirely on the client side; no server-side configuration required.
The automounter uses the same mount options used by the mount command, including security options.
Support for both direct and indirect mount point mapping, providing flexibility in mount point locations.
Indirect mount points are created and removed by autofs, alleviating the need to manually manage them.
NFS is the default file system for the automounter, but it can be used to automount a range of different file systems.
autofs is a service that is managed like other system services.

Create an automount

Configuring an automount is a multistep process:

Install the autofs package.
```
[student@desktopX ~]$ sudo yum -y install autofs
```
This package contains everything needed to use the automounter for NFS shares.
Add a master-map file to /etc/auto.master.d—this file identifies the base directory used for mount points and identifies the mapping file used for creating the automounts.
Use vim to create and edit the master-map file:
```
[student@desktopX ~]$ sudo vim /etc/auto.master.d/demo.autofs
```
The name of the master-map file is not important, but it is normally something meaningful. The only requirement is it must have an extension of .autofs. The master-map file can hold multiple mapping entries, or use multiple files to separate configuration data.
Add the master-map entry, in this case, for indirectly mapped mounts:
```
/shares  /etc/auto.demo
```
This entry would use the /shares directory as the base of future indirect automounts. The /etc/auto.demo file contains the mount details; use an absolute filename. The auto.demo file needs to be created before starting the autofs service.
To use directly mapped mount points, add an entry to the same file (or in a separate file):
```
/-  /etc/auto.direct
```
All direct map entries use "/-" as the base directory. In this case, the mapping file that contains the mount details is /etc/auto.direct.
Create the mapping file(s). The mapping file identifies the mount point, mount options, and source location to mount.
Use vim to create and edit the mapping file:
```
[student@desktopX ~]$ sudo vim /etc/auto.demo
```
The file name is not important, but by convention is located in /etc and called auto.name, where name is something meaningful to the included contents.
```
work  -rw,sync  serverX:/shares/work
```
The format of an entry is mount point, mount options, and source location. This example is showing a basic indirect mapping entry. Direct maps and indirect maps using wildcards will be covered later in this section.
- Known as the "key" in the man pages, the mount point will be created and removed automatically by the autofs service. In this case, the fully qualified mount point will be /shares/work—see the master-map file. The /shares directory and the work directory will be created and removed as needed by the autofs service.
  In this example, the local mount point mirrors the server's directory structure. The local mount point can be named anything. There is no requirement to align the names of the local mount point and the server directory structure.
- Mount options start with a "-" (dash) and are comma-separated with no white space. The mount options available are the same as those available to the equivalent manual mount command. In this example, the automounter will try and mount the share using read/write access, security will be based on standard Linux file permissions (the default: sec=sys), and the server will be synchronized immediately during write operations.
  There are a couple of useful automounter specific options: -fstype= and -strict. Use fstype to specify the file system if it is not NFS and use strict to treat errors, when mounting file systems, as fatal.
- The source location for NFS shares follows the host:/pathname pattern; in this example, serverX:/shares/work. This directory will need to have been exported on serverX with support for read/write access and standard Linux file permissions for the mount to be successful.
  If the file system to be mounted begins with a "/" (slash), such as local device entries or SMB shares, then a ":" (colon) needs to be prefixed; for example, an SMB share would be ://serverX/share.

Start and enable the automount service.

Use systemctl to both start and enable the autofs service.

[student@desktopX ~]$ sudo systemctl enable autofs
ln -s '/usr/lib/systemd/system/autofs.service'  ...
[student@desktopX ~]$ sudo systemctl start autofs

The mapping file—direct maps

As the name implies, direct maps are used to map an NFS share to an existing mount point. The automounter will not attempt to create the mount point automatically; it must exist prior to the autofs service being started.

Continuing from the previous example, the content for the /etc/auto.direct file might look like this:

/mnt/docs  -rw,sync  serverX:/shares/docs

The mount point (or key) is always an absolute path, starting with "/" (slash). The rest of the mapping file uses the same structure.

Only the right-most directory is put under automounter control. Thus, the directory structure above the mount point (/mnt in this example) is not obscured by autofs.

The mapping file—indirect wildcard maps

When an NFS server is exporting multiple subdirectories within a directory, then the automounter can be configured to access any one of those subdirectories using a single mapping entry. As an example, this can be really useful for automounting user home directories from an NFS server.

Continuing the previous example, if serverX:/shares is exporting two or more subdirectories and they are able to be accessed using the same mount options, then the content for the /etc/auto.demo file might look like this:

*  -rw,sync  serverX:/shares/&

The mount point (or key) is an "*" (asterisk), and the subdirectory on the source location is an "&" (ampersand). Everything else in the entry is the same.

When a user attempts to access /shares/work, the key * (which is work in this example) will replace the ampersand in the source location and serverX:/shares/work will be mounted. As with the indirect example, the work directory will be created and removed automatically by the autofs service.

References

autofs(5), automount(8), auto.master(5), and mount.nfs(8) man pages

Discuss Red Hat System Administration II

Go to community

Is It possible to reset root password when the system is on multi-user.target?

jennifer1987

27 lip 2023

Hi thereWell, i have a question, Is It possible to reset root password when the system is on multi-user.target? I was not be able to found a foro o some information related with this and another question that I have, If the grub menu dont show up, is it posible to reset the root password?

991

Red Hat System Administration II (RH134)

Haley_Ruccio

21 lip 2023

Build the skills to perform the key tasks needed to become a full-time Linux administratorRed Hat System Administration II (RH134) is the second part of the RHCSA training track for IT professionals who have already attended Red Hat System Administration I. The course goes deeper into core Linux system administration skills in storage configuration and management, installation and deployment of Red Hat Enterprise Linux, management of security features such as SELinux, control of recurring system tasks, management of the boot process and troubleshooting, basic system tuning, and command-line automation and productivity. This course assumes that students have attended Red Hat System Administration I (RH124).Experienced Linux administrators who seek rapid preparation for the RHCSA certification should instead start with RHCSA Rapid Track (RH199).This course is based on Red Hat Enterprise Linux 9.0.Course summaryInstall Red Hat Enterprise Linux using scalable methodsAccess security files, file systems, and networksExecute shell scripting and automation techniquesManage storage devices, logical volumes, and file systemsManage security and system accessControl the boot process and system servicesRun containersAudience for this courseThis course is geared toward Windows system administrators, network administrators, and other system administrators who are interested in supplementing current skills or backstopping other team members, in addition to Linux system administrators who are responsible for these tasks:Configuring, installing, upgrading, and maintaining Linux systems using established standards and proceduresProviding operational supportManaging systems for monitoring system performance and availabilityWriting and deploying scripts for task automation and system administrationRecommended trainingSuccessful completion of Red Hat System Administration I (RH124) is recommended.Experienced Linux administrators seeking to accelerate their path toward becoming a Red Hat Certified System Administrator should start with the RHCSA Rapid Track course (RH199).Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technology requirements.This course is not designed for bring your own device (BYOD).Internet access is not required, but is recommended to allow students to research and access Red Hat online resources.

Welcome to the Red Hat System Administration II (RH134) group in the Red Hat Learning Community!

Deanna

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat System Administration II! To gain the most value from this group - click the "Join Group" button in the upper right hand corner.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH134.Read more about Red Hat System Administration II here.

417

Revision: rh134-7-c643331