NFS Mounts and Client Packages
The objective is the client side, and step one is the one that wastes the most time: nfs-utils is not installed on a minimal RHEL 10, and without it mount -t nfs fails with a message about a "remote address" that mentions no package at all. After that, root_squash is demonstrated rather than described.
File Systems Guide 38 of 67 Intermediate
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 16 min
The mount helper is /usr/sbin/mount.nfs, from nfs-utils. Without it, mount -t nfs hands the specification straight to the kernel, which cannot resolve a hostname into an address - hence the error. Installing the package is the whole fix.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| RHCSA-A01 | 192.168.0.31 | RHEL 10.0 | Practice node (graded) - spare /dev/sda | 2 Core | 4 GB | 50 GB + 15 GB |
| RHCSA-UTIL01 | 192.168.0.32 | RHEL 10.0 | Utility - repository server and NFS exports | 2 Core | 4 GB | 50 GB |
This guide includes
Use this because step one is the one that wastes the most time. This matters because the client package is not installed by default - so the mount fails before anything about NFS is even wrong.
- installing the package nobody mentions
- discovering what the server actually exports
- mounting read-only, and then meeting root_squash
- making the mount persistent
- unmounting, and finding out when it refuses
Before you start
- An NFS server exporting something. Here it is RHCSA-UTIL01.
- The session installs
nfs-utils, appends to/etc/fstab, and removes its own lines.
-
The package nobody mentions
-
Discovering what is exported
-
Mounting read-only
-
root_squash
-
Making it persistent
-
Unmounting, and when it refuses