NFS: Difference between revisions
Lahwaacz.bot (talk | contribs) (update interlanguage links) |
(Undo revision 805117 by Mwjrink (talk) - vers=4 *is* a mount option, the -O flag works with the -a flag) Tag: Undo |
||
(83 intermediate revisions by 32 users not shown) | |||
Line 2: | Line 2: | ||
[[Category:Network sharing]] | [[Category:Network sharing]] | ||
[[Category:Servers]] | [[Category:Servers]] | ||
[[de:Network File System]] | [[de:Network File System]] | ||
[[ja:NFS]] | [[ja:NFS]] | ||
[[zh-hans:NFS]] | [[zh-hans:NFS]] | ||
Line 16: | Line 12: | ||
{{Note| | {{Note| | ||
* NFS is not encrypted. | * By default, NFS is not encrypted. Configure [[#TLS encryption]], or configure [[Kerberos]] ({{ic|1=sec=krb5p}} to provide Kerberos-based encryption), or tunnel NFS through an encrypted [[VPN]] (such as WireGuard) when dealing with sensitive data. | ||
* Unlike [[Samba]], NFS does not have any user authentication by default, client access is restricted by their IP-address/[[hostname]]. | * Unlike [[Samba]], NFS does not have any user authentication by default, client access is restricted by their IP-address/[[hostname]]. Kerberos is available if stronger authentication is wanted. | ||
* NFS expects the [[user]] and/or [[user group]] | * NFS expects the [[user]] and/or [[user group]] IDs are the same on both the client and server (unless Kerberos is used). [[#Enabling NFSv4 idmapping|Enable NFSv4 idmapping]] or overrule the UID/GID manually by using {{ic|anonuid}}/{{ic|anongid}} together with {{ic|all_squash}} in {{ic|/etc/exports}}. | ||
* NFS does not support [[Access Control Lists|POSIX ACLs]]. The NFS server will still enforce ACLs, but clients will not be able to see or modify them. | |||
}} | }} | ||
== Installation == | == Installation == | ||
Both client and server only require the [[install | Both client and server only require the [[install]]ation of the {{Pkg|nfs-utils}} package. | ||
It is '''highly''' recommended to use a [[time synchronization]] daemon to keep client/server clocks in sync. Without accurate clocks on all nodes, NFS can introduce unwanted delays. | It is '''highly''' recommended to use a [[time synchronization]] daemon to keep client/server clocks in sync. Without accurate clocks on all nodes, NFS can introduce unwanted delays. | ||
== | == Server configuration == | ||
= | Global configuration options are set in {{ic|/etc/nfs.conf}}. Users of simple configurations should not need to edit this file. | ||
The NFS server needs a list of directories to share, in the form of exports (see {{man|5|exports}} for details) which one must define in {{ic|/etc/exports}} or {{ic|/etc/exports.d/*.exports}}. By default, the directories are exported with their paths as-is; for example: | |||
{{hc|/etc/exports|2= | |||
/data/music 192.168.1.0/24(rw) | |||
}} | |||
The above will make the directory {{ic|/data/music}} mountable as {{ic|MyServer:/data/music}} for both NFSv3 and NFSv4. | |||
=== Custom export root === | |||
Shares may be relative to the so-called NFS root. A good security practice is to define a NFS root in a discrete directory tree which will keep users limited to that mount point. Bind mounts are used to link the share mount point to the actual directory elsewhere on the [[filesystem]]. An NFS root used to be mandatory for NFSv4 in the past; it is now optional (as of kernel 2.6.33 and nfs-utils 1.2.2, which implement a virtual root). | |||
Consider this following example wherein: | Consider this following example wherein: | ||
Line 54: | Line 59: | ||
{{hc|/etc/exports|2= | {{hc|/etc/exports|2= | ||
/srv/nfs 192.168.1.0/24(rw | /srv/nfs 192.168.1.0/24(rw,fsid=root) | ||
/srv/nfs/music 192.168.1.0/24(rw,sync) | /srv/nfs/music 192.168.1.0/24(rw,sync) | ||
/srv/nfs/home 192.168.1.0/24(rw,sync | /srv/nfs/home 192.168.1.0/24(rw,sync) | ||
/srv/nfs/public 192.168.1.0/24(ro,all_squash,insecure) desktop(rw,sync,all_squash,anonuid=99,anongid=99) # map to user/group - in this case ''nobody'' | /srv/nfs/public 192.168.1.0/24(ro,all_squash,insecure) desktop(rw,sync,all_squash,anonuid=99,anongid=99) # map to user/group - in this case ''nobody'' | ||
}} | }} | ||
When using NFSv4, the option {{ic|1=fsid=root}} or {{ic|1=fsid=0}} denotes the "root" export; if such an export is present, then all other directories must be below it. The {{ic|rootdir}} option in the {{ic|/etc/nfs.conf}} file has no effect on this. The default behavior, when there is no {{ic|1=fsid=0}} export, is to behave the same way as in NFSv3. | |||
In the above example, because {{ic|/srv/nfs}} is designated as the root, the export {{ic|/srv/nfs/music}} is now mountable as {{ic|MyServer:/music}} via NFSv4 – note that the root prefix is omitted. | |||
{{Tip| | {{Tip| | ||
* | * For NFSv3 (not needed for NFSv4), the {{ic|crossmnt}} option makes it possible for clients to access '''all''' filesystems mounted on a filesystem marked with {{ic|crossmnt}} and clients will not be required to mount every child export separately. Note this may not be desirable if a child is shared with a different range of addresses. | ||
* Instead of {{ic|crossmnt}}, one can also use the {{ic|nohide}} option on child exports so that they can be automatically mounted when a client mounts the root export. Being different from {{ic|crossmnt}}, {{ic|nohide}} still respects address ranges of child exports. | * Instead of {{ic|crossmnt}}, one can also use the {{ic|nohide}} option on child exports so that they can be automatically mounted when a client mounts the root export. Being different from {{ic|crossmnt}}, {{ic|nohide}} still respects address ranges of child exports. Note that the option is also NFSv3-specific; NFSv4 ''always'' behaves as if nohide was enabled. | ||
* Use an asterisk (*) to allow access from any interface.}} | * The {{ic|insecure}} option allows clients to connect from ports above 1023. (Presumably only the root user can use low-numbered ports, so blocking other ports by default creates a superficial barrier to access. In practice neither omitting nor including the {{ic|insecure}} option provides any meaningful improvement or detriment to security.) | ||
* Use an asterisk ({{ic|*}}) to allow access from any interface. | |||
}} | |||
It should be noted that modifying {{ic|/etc/exports}} while the server is running will require a re-export for changes to take effect: | It should be noted that modifying {{ic|/etc/exports}} while the server is running will require a re-export for changes to take effect: | ||
Line 75: | Line 86: | ||
For more information about all available options see {{man|5|exports}}. | For more information about all available options see {{man|5|exports}}. | ||
{{Tip|[ | {{Tip|[https://ip2cidr.com/ ip2cidr] is a tool to convert IP address ranges to correctly structured CIDR specifications.}} | ||
{{Note|If the target export is a [[tmpfs]] filesystem, the {{ic|1=fsid=1}} option is required.}} | {{Note|If the target export is a [[tmpfs]] filesystem, the {{ic|1=fsid=1}} option is required.}} | ||
=== Starting the server === | |||
[[ | * To provide both NFSv3 and NFSv4 service, [[start]] and [[enable]] {{ic|nfs-server.service}}. | ||
* To provide NFSv4 service exclusively, [[start]] and [[enable]] {{ic|nfsv4-server.service}}. | |||
{{ | Users of protocol version 4 exports will probably want to [[mask]] at a minimum both {{ic|rpcbind.service}} and {{ic|rpcbind.socket}} to prevent superfluous services from running. See {{Bug|76453}}. Additionally, consider masking {{ic|nfs-server.service}} which pulled in for some reason as well. | ||
{{Note|If exporting ZFS shares, also [[start]]/[[enable]] {{ic|zfs-share.service}}. Without this, ZFS shares will no longer be exported after a reboot. See [[ZFS#NFS]].}} | {{Note|If exporting ZFS shares, also [[start]]/[[enable]] {{ic|zfs-share.service}}. Without this, ZFS shares will no longer be exported after a reboot. See [[ZFS#NFS]].}} | ||
=== Restricting NFS to interfaces/IPs === | |||
By default, starting {{ic|nfs-server.service}} will listen for connections on all network interfaces, regardless of {{ic|/etc/exports}}. This can be changed by defining which IPs and/or hostnames to listen on. | By default, starting {{ic|nfs-server.service}} will listen for connections on all network interfaces, regardless of {{ic|/etc/exports}}. This can be changed by defining which IPs and/or hostnames to listen on. | ||
Line 100: | Line 112: | ||
[[Restart]] {{ic|nfs-server.service}} to apply the changes immediately. | [[Restart]] {{ic|nfs-server.service}} to apply the changes immediately. | ||
=== Firewall configuration === | |||
To enable access of NFSv4-servers through a [[firewall]], TCP port {{ic|2049}} must be opened for incoming connections. (NFSv4 uses a static port number; it does not use any auxiliary services such as mountd or portmapper.) | |||
To enable access | To enable access of NFSv3 servers, you will additionally need to open TCP/UDP port {{ic|111}} for the portmapper (rpcbind), as well as the MOUNT (rpc.mountd) port. By default, rpc.mountd selects a port dynamically, so if you're behind a firewall you will want to edit {{ic|/etc/nfs.conf}} to set a static port instead. Use {{ic|rpcinfo -p}} to examine the exact ports in use on the NFSv3 server: | ||
{{hc|$ rpcinfo -p | {{hc|$ rpcinfo -p| | ||
100003 3 tcp 2049 nfs | 100003 3 tcp 2049 nfs | ||
100003 4 tcp 2049 nfs | 100003 4 tcp 2049 nfs | ||
100227 3 tcp 2049 nfs_acl | 100227 3 tcp 2049 nfs_acl | ||
... | |||
}} | }} | ||
=== Enabling NFSv4 idmapping === | |||
{{Expansion|Missing lookup information, static binding examples, etc.}} | {{Expansion|Missing lookup information, static binding examples, etc.}} | ||
{{Note|1=<nowiki | {{Note|1=<nowiki/> | ||
* NFSv4 idmapping does not work with the default {{ic|1=sec=sys}} mount option. [ | * NFSv4 idmapping does not work with the default {{ic|1=sec=sys}} mount option. [https://web.archive.org/web/20220602190451/https://dfusion.com.au/wiki/tiki-index.php?page=Why+NFSv4+UID+mapping+breaks+with+AUTH_UNIX] | ||
* NFSv4 idmapping needs to be enabled on '''both''' the client and server. | * NFSv4 idmapping needs to be enabled on '''both''' the client and server. | ||
* Another option is to make sure the user and group IDs (UID and GID) match on both the client and server. | * Another option is to make sure the user and group IDs (UID and GID) match on both the client and server. | ||
* [[Enabling]]/[[starting]] {{ic|nfs-idmapd.service}} should not be needed as it has been replaced with a new id mapper: | * [[Enabling]]/[[starting]] {{ic|nfs-idmapd.service}} should '''not''' be needed as it has been replaced with a new id mapper: | ||
{{hc|# dmesg | {{hc|# dmesg {{!}} grep id_resolver| | ||
[ 3238.356001] NFS: Registering the id_resolver key type | [ 3238.356001] NFS: Registering the id_resolver key type | ||
[ 3238.356009] Key type id_resolver registered | [ 3238.356009] Key type id_resolver registered | ||
}} | |||
}} | |||
{{ | The NFSv4 protocol represents the local system's UID and GID values on the wire as strings of the form {{ic|''user''@''domain''}}. The process of translating from UID to string and string to UID is referred to as ''ID mapping''. See {{man|8|nfsidmap}} for details. | ||
}} | |||
To fully use ''idmapping'', make sure the domain is configured in {{ic|/etc/idmapd.conf}} on '''both''' the server and the client: | To fully use ''idmapping'', make sure the domain is configured in {{ic|/etc/idmapd.conf}} on '''both''' the server and the client: | ||
Line 193: | Line 152: | ||
See [https://unix.stackexchange.com/a/464950] for details. | See [https://unix.stackexchange.com/a/464950] for details. | ||
== Client configuration == | |||
Users intending to use NFS4 with [[Kerberos]] need to [[start]] and [[enable]] {{ic|nfs-client.target}}. | Users intending to use NFS4 with [[Kerberos]] need to [[start]] and [[enable]] {{ic|nfs-client.target}}. | ||
=== Manual mounting === | |||
For NFSv3 use this command to show the server's exported file systems: | For NFSv3 use this command to show the server's exported file systems: | ||
$ showmount -e servername | $ showmount -e ''servername'' | ||
For NFSv4 mount the root NFS directory and look around for available mounts: | For NFSv4 mount the root NFS directory and look around for available mounts: | ||
# mount | # mount ''servername'':/ ''/mountpoint/on/client'' | ||
Then mount omitting the server's NFS export root: | Then mount omitting the server's NFS export root: | ||
# mount -t nfs -o vers=4 servername:/music /mountpoint/on/client | # mount -t nfs -o vers=4 ''servername'':/music ''/mountpoint/on/client'' | ||
If mount fails try including the server's export root (required for Debian/RHEL/SLES, some distributions need {{ic|-t nfs4}} instead of {{ic|-t nfs}}): | If mount fails try including the server's export root (required for Debian/RHEL/SLES, some distributions need {{ic|-t nfs4}} instead of {{ic|-t nfs}}): | ||
# mount -t nfs -o vers=4 servername:/srv/nfs/music /mountpoint/on/client | # mount -t nfs -o vers=4 ''servername'':/srv/nfs/music ''/mountpoint/on/client'' | ||
{{Note| | {{Note|{{ic|''servername''}} needs to be replaced with a valid hostname (not just IP address). Otherwise mounting of remote share will hang.}} | ||
=== Mount using /etc/fstab === | |||
Using [[fstab]] is useful for a server which is always on, and the NFS shares are available whenever the client boots up. Edit {{ic|/etc/fstab}} file, and add an appropriate line reflecting the setup. Again, the server's NFS export root is omitted. | Using [[fstab]] is useful for a server which is always on, and the NFS shares are available whenever the client boots up. Edit {{ic|/etc/fstab}} file, and add an appropriate line reflecting the setup. Again, the server's NFS export root is omitted. | ||
Line 230: | Line 189: | ||
; rsize and wsize: The {{ic|rsize}} value is the number of bytes used when reading from the server. The {{ic|wsize}} value is the number of bytes used when writing to the server. By default, if these options are not specified, the client and server negotiate the largest values they can both support (see {{man|5|nfs}} for details). After changing these values, it is recommended to test the performance (see [[#Performance tuning]]). | ; rsize and wsize: The {{ic|rsize}} value is the number of bytes used when reading from the server. The {{ic|wsize}} value is the number of bytes used when writing to the server. By default, if these options are not specified, the client and server negotiate the largest values they can both support (see {{man|5|nfs}} for details). After changing these values, it is recommended to test the performance (see [[#Performance tuning]]). | ||
; soft or hard: Determines the recovery behaviour of the NFS client after an NFS request times out. If neither option is specified (or if the {{ic|hard}} option is specified), NFS requests are retried indefinitely. If the {{ic|soft}} option is specified, then the NFS client fails an NFS request after ''retrans'' retransmissions have been sent, causing the NFS client to return an error to the calling application. | |||
; soft or hard: Determines the recovery behaviour of the NFS client after an NFS request times out. If neither option is specified (or if the {{ic|hard}} option is specified), NFS requests are retried indefinitely. If the {{ic|soft}} option is specified, then the NFS client fails | |||
{{Warning|A so-called {{ic|soft}} timeout can cause silent data corruption in certain cases. As such, use the {{ic|soft}} option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the {{ic|retrans}} option may mitigate some of the risks of using the {{ic|soft}} option.}} | {{Warning|A so-called {{ic|soft}} timeout can cause silent data corruption in certain cases. As such, use the {{ic|soft}} option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the {{ic|retrans}} option may mitigate some of the risks of using the {{ic|soft}} option.}} | ||
; timeo: The {{ic|timeo}} value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. The default value for NFS over TCP is 600 (60 seconds). After the first timeout, the timeout value is doubled for each retry for a maximum of 60 seconds or until a major timeout occurs. If connecting to a slow server or over a busy network, better stability can be achieved by increasing this timeout value. | ; timeo: The {{ic|timeo}} value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. The default value for NFS over TCP is 600 (60 seconds). After the first timeout, the timeout value is doubled for each retry for a maximum of 60 seconds or until a major timeout occurs. If connecting to a slow server or over a busy network, better stability can be achieved by increasing this timeout value. | ||
; retrans: The number of times the NFS client retries a request before it attempts further recovery action. If the {{ic|retrans}} option is not specified, the NFS client tries each request three times. The NFS client generates a "server not responding" message after ''retrans'' retries, then attempts further recovery (depending on whether the hard mount option is in effect). | ; retrans: The number of times the NFS client retries a request before it attempts further recovery action. If the {{ic|retrans}} option is not specified, the NFS client tries each request three times. The NFS client generates a "server not responding" message after ''retrans'' retries, then attempts further recovery (depending on whether the hard mount option is in effect). | ||
; _netdev: The {{ic|_netdev}} option tells the system to wait until the network is up before trying to mount the share - [[systemd]] assumes this for NFS. | ; _netdev: The {{ic|_netdev}} option tells the system to wait until the network is up before trying to mount the share - [[systemd]] assumes this for NFS. | ||
{{Note|Setting the sixth field ({{ic|fs_passno}}) to a nonzero value may lead to unexpected behaviour, e.g. hangs when the systemd automount waits for a check which will never happen.}} | {{Note|Setting the sixth field ({{ic|fs_passno}}) to a nonzero value may lead to unexpected behaviour, e.g. hangs when the systemd automount waits for a check which will never happen.}} | ||
=== Mount using /etc/fstab with systemd === | |||
Another method is using the [[Fstab#Remote | Another method is using the [[Fstab#Remote file system|x-systemd.automount]] option which mounts the filesystem upon access: | ||
{{hc|1=/etc/fstab|2= | {{hc|1=/etc/fstab|2= | ||
Line 252: | Line 208: | ||
To make systemd aware of the changes to fstab, [[reload]] systemd and restart {{ic|remote-fs.target}} [https://bbs.archlinux.org/viewtopic.php?pid=1515377#p1515377]. | To make systemd aware of the changes to fstab, [[reload]] systemd and restart {{ic|remote-fs.target}} [https://bbs.archlinux.org/viewtopic.php?pid=1515377#p1515377]. | ||
{{Accuracy|Not everyone uses NetworkManager. Refer to [[Systemd#Running services after the network is up]] instead?}} | |||
{{Tip| | {{Tip| | ||
Line 257: | Line 215: | ||
* The {{ic|users}} mount option would allow user mounts, but be aware it implies further options as {{ic|noexec}} for example. | * The {{ic|users}} mount option would allow user mounts, but be aware it implies further options as {{ic|noexec}} for example. | ||
* The {{ic|1=x-systemd.idle-timeout=1min}} option will unmount the NFS share automatically after 1 minute of non-use. Good for laptops which might suddenly disconnect from the network. | * The {{ic|1=x-systemd.idle-timeout=1min}} option will unmount the NFS share automatically after 1 minute of non-use. Good for laptops which might suddenly disconnect from the network. | ||
* If shutdown/reboot holds too long because of NFS, [[enable]] {{ic|NetworkManager-wait-online.service}} to ensure that NetworkManager is not exited before the NFS volumes are unmounted. | * If shutdown/reboot holds too long because of NFS, [[enable]] {{ic|NetworkManager-wait-online.service}} to ensure that NetworkManager is not exited before the NFS volumes are unmounted. | ||
* Do not add the {{ic|1=x-systemd.requires=network-online.target}} mount option as this can lead to ordering cycles within systemd [https://github.com/systemd/systemd-stable/issues/69]. systemd adds the {{ic|network-online.target}} dependency to the unit for {{ic|_netdev}} mount automatically. | |||
* Using the {{ic|nocto}} option may improve performance for read-only mounts, but should be used only if the data on the server changes only occasionally. | * Using the {{ic|nocto}} option may improve performance for read-only mounts, but should be used only if the data on the server changes only occasionally. | ||
}} | }} | ||
=== As systemd unit === | |||
Create a new {{ic|.mount}} file inside {{ic|/etc/systemd/system}}, e.g. {{ic|mnt- | Create a new {{ic|.mount}} file inside {{ic|/etc/systemd/system}}, e.g. {{ic|mnt-home.mount}}. See {{man|5|systemd.mount}} for details. | ||
{{Note|Make sure the filename corresponds to the mountpoint you want to use. | {{Note|Make sure the filename corresponds to the mountpoint you want to use. | ||
E.g. the unit name {{ic|mnt- | E.g. the unit name {{ic|mnt-home.mount}} can only be used if you are going to mount the share under {{ic|/mnt/home}}. Otherwise the following error might occur: {{ic|1=systemd[1]: mnt-home.mount: Where= setting does not match unit name. Refusing.}}. If the mountpoint contains non-ASCII characters, use [[Systemd#Writing unit files|systemd-escape]]).}} | ||
{{ic|1=What=}} path to share | {{ic|1=What=}} path to share | ||
Line 275: | Line 234: | ||
{{Note| | {{Note| | ||
* Network mount units automatically acquire {{ic|After}} dependencies on | * Network mount units automatically acquire {{ic|After}} dependencies on {{ic|remote-fs-pre.target}}, {{ic|network.target}} and {{ic|network-online.target}}, and gain a {{ic|Before}} dependency on {{ic|remote-fs.target}} unless {{ic|nofail}} mount option is set. Towards the latter a {{ic|Wants}} unit is added as well. | ||
* [[Append]] {{ic|noauto}} to {{ic|Options}} preventing automatically mount during boot (unless it is pulled in by some other unit). | * [[Append]] {{ic|noauto}} to {{ic|Options}} preventing automatically mount during boot (unless it is pulled in by some other unit). | ||
* If you want to use a hostname for the server you want to share (instead of an IP address), add {{ic|1=nss-lookup.target}} to {{ic|1=After | * If you want to use a hostname for the server you want to share (instead of an IP address), add {{ic|1=nss-lookup.target}} to {{ic|1=After}}. This might avoid mount errors at boot time that do not arise when testing the unit. | ||
}} | |||
{{hc|/etc/systemd/system/mnt- | {{hc|/etc/systemd/system/mnt-home.mount|2= | ||
[Unit] | [Unit] | ||
Description=Mount | Description=Mount home at boot | ||
[Mount] | [Mount] | ||
What=172.16.24.192:/ | What=172.16.24.192:/home | ||
Where=/mnt/ | Where=/mnt/home | ||
Options= | Options=vers=4 | ||
Type=nfs | Type=nfs | ||
TimeoutSec=30 | TimeoutSec=30 | ||
Line 294: | Line 254: | ||
}} | }} | ||
{{Tip|In case of an unreachable system, [[append]] {{ic|1=ForceUnmount=true}} to {{ic|[Mount]}}, allowing the | {{Tip|In case of an unreachable system, [[append]] {{ic|1=ForceUnmount=true}} to {{ic|[Mount]}}, allowing the export to be (force-)unmounted.}} | ||
To use {{ic|mnt- | To use {{ic|mnt-home.mount}}, [[start]] the unit and [[enable]] it to run on system boot. | ||
==== automount ==== | |||
To automatically mount a share, one may use the following automount unit: | To automatically mount a share, one may use the following automount unit: | ||
{{hc|/etc/systemd/system/mnt- | {{hc|/etc/systemd/system/mnt-home.automount|2= | ||
[Unit] | [Unit] | ||
Description=Automount | Description=Automount home | ||
[Automount] | [Automount] | ||
Where=/mnt/ | Where=/mnt/home | ||
[Install] | [Install] | ||
Line 313: | Line 273: | ||
}} | }} | ||
[[Disable]]/[[stop]] the {{ic|mnt- | [[Disable]]/[[stop]] the {{ic|mnt-home.mount}} unit, and [[enable]]/[[start]] {{ic|mnt-home.automount}} to automount the share when the mount path is being accessed. | ||
{{Tip|[[Append]] {{ic|TimeoutIdleSec}} to enable auto unmount. See {{man|5|systemd.automount}} for details.}} | {{Tip|[[Append]] {{ic|TimeoutIdleSec}} to enable auto unmount. See {{man|5|systemd.automount}} for details.}} | ||
=== Mount using autofs === | |||
Using [[autofs]] is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares. See [[autofs#NFS network mounts]] for details. | Using [[autofs]] is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares. See [[autofs#NFS network mounts]] for details. | ||
Line 324: | Line 284: | ||
=== Performance tuning === | === Performance tuning === | ||
{{Out of date|Mentions 32-bit and 2.6 Linux kernel...}} | |||
When using NFS on a network with a significant number of clients one may increase the default NFS threads from ''8'' to ''16'' or even a higher, depending on the server/network requirements: | When using NFS on a network with a significant number of clients one may increase the default NFS threads from ''8'' to ''16'' or even a higher, depending on the server/network requirements: | ||
Line 334: | Line 296: | ||
It may be necessary to tune the {{ic|rsize}} and {{ic|wsize}} mount options to meet the requirements of the network configuration. | It may be necessary to tune the {{ic|rsize}} and {{ic|wsize}} mount options to meet the requirements of the network configuration. | ||
In recent linux kernels (>2.6.18) the size of I/O operations allowed by the NFS server (default max block size) varies depending on RAM size, with a maximum of 1M (1048576 bytes), the max block size of the server will be used even if nfs clients requires bigger {{ic|rsize}} and {{ic|wsize}}. See https://access.redhat.com/documentation/en- | In recent linux kernels (>2.6.18) the size of I/O operations allowed by the NFS server (default max block size) varies depending on RAM size, with a maximum of 1M (1048576 bytes), the max block size of the server will be used even if nfs clients requires bigger {{ic|rsize}} and {{ic|wsize}}. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/5.8_technical_notes/known_issues-kernel | ||
It is possible to change the default max block size allowed by the server by writing to the {{ic|/proc/fs/nfsd/max_block_size}} before starting ''nfsd''. For example, the following command restores the previous default iosize of 32k: | It is possible to change the default max block size allowed by the server by writing to the {{ic|/proc/fs/nfsd/max_block_size}} before starting ''nfsd''. For example, the following command restores the previous default iosize of 32k: | ||
# echo 32768 > /proc/fs/nfsd/max_block_size | # echo 32768 > /proc/fs/nfsd/max_block_size | ||
To make the change permanent, create a [[ | {{Note|This is mainly useful for 32-bit servers when dealing with the large numbers of nfsd threads. Lowering the {{ic|max_block_size}} may decrease NFS performance on modern hardware.}} | ||
To make the change permanent, create a [[systemd-tmpfile]]: | |||
{{hc|/etc/tmpfiles.d/nfsd-block-size.conf| | {{hc|/etc/tmpfiles.d/nfsd-block-size.conf| | ||
Line 355: | Line 319: | ||
/srv/nfs/music 192.168.1.0/24(rw,async) | /srv/nfs/music 192.168.1.0/24(rw,async) | ||
}} | }} | ||
{{Warning|Using {{ic|async}} comes with a risk of possible data loss or corruption if the server crashes or restarts uncleanly.}} | |||
=== Automatic mount handling === | === Automatic mount handling === | ||
Line 363: | Line 329: | ||
{{hc|/etc/fstab|2= | {{hc|/etc/fstab|2= | ||
lithium:/mnt/data /mnt/data nfs noauto | lithium:/mnt/data /mnt/data nfs noauto 0 0 | ||
lithium:/var/cache/pacman /var/cache/pacman nfs noauto | lithium:/var/cache/pacman /var/cache/pacman nfs noauto 0 0 | ||
}} | }} | ||
Line 370: | Line 336: | ||
* Use hostnames in [[fstab]] for this to work, not IP addresses. | * Use hostnames in [[fstab]] for this to work, not IP addresses. | ||
* In order to mount NFS shares with non-root users the {{ic|users}} option has to be added. | * In order to mount NFS shares with non-root users the {{ic|users}} option has to be added. | ||
* The {{ic|noauto}} mount option tells [[systemd]] to not automatically [[mount]] the shares at boot, otherwise this may | * The {{ic|noauto}} mount option tells [[systemd]] to not automatically [[mount]] the shares at boot, otherwise this may cause the boot process to stall. | ||
}} | }} | ||
Line 429: | Line 395: | ||
in the {{ic|auto_share}} script above.}} | in the {{ic|auto_share}} script above.}} | ||
Make sure the script is [[executable]] | Make sure the script is [[executable]]. | ||
Next check configure the script to run every X, in the examples below this is every minute. | Next check configure the script to run every X, in the examples below this is every minute. | ||
Line 457: | Line 421: | ||
[Unit] | [Unit] | ||
Description=Automount NFS shares | Description=Automount NFS shares | ||
After= | After=network.target | ||
[Service] | [Service] | ||
Line 479: | Line 443: | ||
However, in that particular case unmounting will happen only after the network connection has already been disabled, which is unclean and may result in effects like freezing of KDE Plasma applets. | However, in that particular case unmounting will happen only after the network connection has already been disabled, which is unclean and may result in effects like freezing of KDE Plasma applets. | ||
The following script safely unmounts the NFS shares before the relevant network connection is disabled by listening for the {{ic|pre-down}} and {{ic|vpn-pre-down}} events, make the script is [[executable]]: | The following script safely unmounts the NFS shares before the relevant network connection is disabled by listening for the {{ic|down}}, {{ic|pre-down}} and {{ic|vpn-pre-down}} events, make sure the script is [[executable]]: | ||
{{hc|/etc/NetworkManager/dispatcher.d/30-nfs.sh|<nowiki> | {{hc|/etc/NetworkManager/dispatcher.d/30-nfs.sh|<nowiki> | ||
#!/bin/ | #!/bin/sh | ||
# Find the connection UUID with "nmcli con show" in terminal. | # Find the connection UUID with "nmcli con show" in terminal. | ||
Line 488: | Line 452: | ||
WANTED_CON_UUID="CHANGE-ME-NOW-9c7eff15-010a-4b1c-a786-9b4efa218ba9" | WANTED_CON_UUID="CHANGE-ME-NOW-9c7eff15-010a-4b1c-a786-9b4efa218ba9" | ||
if | if [ "$CONNECTION_UUID" = "$WANTED_CON_UUID" ]; then | ||
# Script parameter $1: | # Script parameter $1: network interface name, not used | ||
# Script parameter $2: dispatched event | # Script parameter $2: dispatched event | ||
Line 497: | Line 461: | ||
mount -a -t nfs4,nfs | mount -a -t nfs4,nfs | ||
;; | ;; | ||
"pre-down" | "down"|"pre-down"|"vpn-pre-down") | ||
umount -l -a -t nfs4,nfs -f >/dev/null | umount -l -a -t nfs4,nfs -f >/dev/null | ||
;; | ;; | ||
Line 510: | Line 473: | ||
# ln -s /etc/NetworkManager/dispatcher.d/30-nfs.sh /etc/NetworkManager/dispatcher.d/pre-down.d/30-nfs.sh | # ln -s /etc/NetworkManager/dispatcher.d/30-nfs.sh /etc/NetworkManager/dispatcher.d/pre-down.d/30-nfs.sh | ||
=== TLS encryption === | |||
NFS traffic can be encrypted using TLS as of Linux 6.5 using the {{ic|1=xprtsec=tls}} mount option. To begin, install the {{AUR|ktls-utils}} package on the client and server, and follow the below configuration steps for each. | |||
==== Server ==== | |||
Create a private key and obtain a certificate containing your server's DNS name (see [[Transport Layer Security#Obtaining a certificate|Transport Layer Security]] for more detail). These files do not need to be added to the system's trust store. | |||
{{Note|Using a self-signed certificate that has also been encrypted is currently not supported and will result in a mount failure.}} | |||
Edit {{ic|/etc/tlshd.conf}} to use these files, using your own values for {{ic|x509.certificate}} and {{ic|x509.private_key}} | |||
{{hc|/etc/tlshd.conf|2= | |||
[authenticate.server] | |||
x509.certificate= /etc/nfsd-certificate.pem | |||
x509.private_key= /etc/nfsd-private-key.pem | |||
}} | |||
Now [[start]] and [[enable]] {{ic|tlshd.service}}. | |||
==== Client ==== | |||
Add the server's TLS certificate generated in the previous step to the system's trust store (see [[Transport Layer Security#Add a certificate to a trust store|Transport Layer Security]] for more detail). | |||
[[Start]] and [[enable]] {{ic|tlshd.service}}. | |||
Now you should be able to mount the server using the server's DNS name: | |||
# mount -o xprtsec=tls ''servername.domain'':/ ''/mountpoint/on/client'' | |||
Checking journalctl on the client should show that the TLS handshake was successful: | |||
{{hc|$ journalctl -b -u tlshd.service| | |||
Sep 28 11:14:46 client tlshd[227]: Built from ktls-utils 0.10 on Sep 26 2023 14:24:03 | |||
Sep 28 11:15:37 client tlshd[571]: Handshake with servername.domain (192.168.122.100) was successful | |||
}} | |||
== Troubleshooting == | == Troubleshooting == | ||
Line 519: | Line 518: | ||
* See also [[Avahi]], a Zeroconf implementation which allows automatic discovery of NFS shares. | * See also [[Avahi]], a Zeroconf implementation which allows automatic discovery of NFS shares. | ||
* HOWTO: [[Diskless network boot NFS root]] | * HOWTO: [[Diskless network boot NFS root]] | ||
* [ | * [https://web.archive.org/web/20201111215940/https://docs.microsoft.com/en-us/archive/blogs/msdn/sfu/all-well-almost-about-client-for-nfs-configuration-and-performance/ Microsoft Services for Unix NFS Client info] | ||
* | * [https://web.archive.org/web/20151212160906/https://blogs.oracle.com/jag/entry/nfs_on_snow_leopard NFS on Snow Leopard] | ||
* http://chschneider.eu/linux/server/nfs.shtml | * http://chschneider.eu/linux/server/nfs.shtml | ||
* [https://www.slashroot.in/how-do-linux-nfs-performance-tuning-and-optimization How to do Linux NFS Performance Tuning and Optimization] | * [https://www.slashroot.in/how-do-linux-nfs-performance-tuning-and-optimization How to do Linux NFS Performance Tuning and Optimization] | ||
* [https://www.cyberciti.biz/faq/linux-unix-tuning-nfs-server-client-performance/ Linux: Tune NFS Performance] | * [https://www.cyberciti.biz/faq/linux-unix-tuning-nfs-server-client-performance/ Linux: Tune NFS Performance] | ||
* [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/nfs-serverconfig#nfs4-only Configuring an NFSv4-only Server] |
Latest revision as of 10:44, 3 April 2024
From Wikipedia:
- Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems in 1984, allowing a user on a client computer to access files over a network in a manner similar to how local storage is accessed.
- By default, NFS is not encrypted. Configure #TLS encryption, or configure Kerberos (
sec=krb5p
to provide Kerberos-based encryption), or tunnel NFS through an encrypted VPN (such as WireGuard) when dealing with sensitive data. - Unlike Samba, NFS does not have any user authentication by default, client access is restricted by their IP-address/hostname. Kerberos is available if stronger authentication is wanted.
- NFS expects the user and/or user group IDs are the same on both the client and server (unless Kerberos is used). Enable NFSv4 idmapping or overrule the UID/GID manually by using
anonuid
/anongid
together withall_squash
in/etc/exports
. - NFS does not support POSIX ACLs. The NFS server will still enforce ACLs, but clients will not be able to see or modify them.
Installation
Both client and server only require the installation of the nfs-utils package.
It is highly recommended to use a time synchronization daemon to keep client/server clocks in sync. Without accurate clocks on all nodes, NFS can introduce unwanted delays.
Server configuration
Global configuration options are set in /etc/nfs.conf
. Users of simple configurations should not need to edit this file.
The NFS server needs a list of directories to share, in the form of exports (see exports(5) for details) which one must define in /etc/exports
or /etc/exports.d/*.exports
. By default, the directories are exported with their paths as-is; for example:
/etc/exports
/data/music 192.168.1.0/24(rw)
The above will make the directory /data/music
mountable as MyServer:/data/music
for both NFSv3 and NFSv4.
Custom export root
Shares may be relative to the so-called NFS root. A good security practice is to define a NFS root in a discrete directory tree which will keep users limited to that mount point. Bind mounts are used to link the share mount point to the actual directory elsewhere on the filesystem. An NFS root used to be mandatory for NFSv4 in the past; it is now optional (as of kernel 2.6.33 and nfs-utils 1.2.2, which implement a virtual root).
Consider this following example wherein:
- The NFS root is
/srv/nfs
. - The export is
/srv/nfs/music
via a bind mount to the actual target/mnt/music
.
# mkdir -p /srv/nfs/music /mnt/music # mount --bind /mnt/music /srv/nfs/music
To make the bind mount persistent across reboots, add it to fstab:
/etc/fstab
/mnt/music /srv/nfs/music none bind 0 0
Add directories to be shared and limit them to a range of addresses via a CIDR or hostname(s) of client machines that will be allowed to mount them in /etc/exports
, e.g.:
/etc/exports
/srv/nfs 192.168.1.0/24(rw,fsid=root) /srv/nfs/music 192.168.1.0/24(rw,sync) /srv/nfs/home 192.168.1.0/24(rw,sync) /srv/nfs/public 192.168.1.0/24(ro,all_squash,insecure) desktop(rw,sync,all_squash,anonuid=99,anongid=99) # map to user/group - in this case nobody
When using NFSv4, the option fsid=root
or fsid=0
denotes the "root" export; if such an export is present, then all other directories must be below it. The rootdir
option in the /etc/nfs.conf
file has no effect on this. The default behavior, when there is no fsid=0
export, is to behave the same way as in NFSv3.
In the above example, because /srv/nfs
is designated as the root, the export /srv/nfs/music
is now mountable as MyServer:/music
via NFSv4 – note that the root prefix is omitted.
- For NFSv3 (not needed for NFSv4), the
crossmnt
option makes it possible for clients to access all filesystems mounted on a filesystem marked withcrossmnt
and clients will not be required to mount every child export separately. Note this may not be desirable if a child is shared with a different range of addresses. - Instead of
crossmnt
, one can also use thenohide
option on child exports so that they can be automatically mounted when a client mounts the root export. Being different fromcrossmnt
,nohide
still respects address ranges of child exports. Note that the option is also NFSv3-specific; NFSv4 always behaves as if nohide was enabled. - The
insecure
option allows clients to connect from ports above 1023. (Presumably only the root user can use low-numbered ports, so blocking other ports by default creates a superficial barrier to access. In practice neither omitting nor including theinsecure
option provides any meaningful improvement or detriment to security.) - Use an asterisk (
*
) to allow access from any interface.
It should be noted that modifying /etc/exports
while the server is running will require a re-export for changes to take effect:
# exportfs -arv
To view the current loaded exports state in more detail, use:
# exportfs -v
For more information about all available options see exports(5).
fsid=1
option is required.Starting the server
- To provide both NFSv3 and NFSv4 service, start and enable
nfs-server.service
. - To provide NFSv4 service exclusively, start and enable
nfsv4-server.service
.
Users of protocol version 4 exports will probably want to mask at a minimum both rpcbind.service
and rpcbind.socket
to prevent superfluous services from running. See FS#76453. Additionally, consider masking nfs-server.service
which pulled in for some reason as well.
zfs-share.service
. Without this, ZFS shares will no longer be exported after a reboot. See ZFS#NFS.Restricting NFS to interfaces/IPs
By default, starting nfs-server.service
will listen for connections on all network interfaces, regardless of /etc/exports
. This can be changed by defining which IPs and/or hostnames to listen on.
/etc/nfs.conf
[nfsd] host=192.168.1.123 # Alternatively, use the hostname. # host=myhostname
Restart nfs-server.service
to apply the changes immediately.
Firewall configuration
To enable access of NFSv4-servers through a firewall, TCP port 2049
must be opened for incoming connections. (NFSv4 uses a static port number; it does not use any auxiliary services such as mountd or portmapper.)
To enable access of NFSv3 servers, you will additionally need to open TCP/UDP port 111
for the portmapper (rpcbind), as well as the MOUNT (rpc.mountd) port. By default, rpc.mountd selects a port dynamically, so if you're behind a firewall you will want to edit /etc/nfs.conf
to set a static port instead. Use rpcinfo -p
to examine the exact ports in use on the NFSv3 server:
$ rpcinfo -p
100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl ...
Enabling NFSv4 idmapping
- NFSv4 idmapping does not work with the default
sec=sys
mount option. [1] - NFSv4 idmapping needs to be enabled on both the client and server.
- Another option is to make sure the user and group IDs (UID and GID) match on both the client and server.
- Enabling/starting
nfs-idmapd.service
should not be needed as it has been replaced with a new id mapper:
# dmesg | grep id_resolver
[ 3238.356001] NFS: Registering the id_resolver key type [ 3238.356009] Key type id_resolver registered
The NFSv4 protocol represents the local system's UID and GID values on the wire as strings of the form user@domain
. The process of translating from UID to string and string to UID is referred to as ID mapping. See nfsidmap(8) for details.
To fully use idmapping, make sure the domain is configured in /etc/idmapd.conf
on both the server and the client:
/etc/idmapd.conf
# The following should be set to the local NFSv4 domain name # The default is the host's DNS domain name. Domain = domain.tld
See [2] for details.
Client configuration
Users intending to use NFS4 with Kerberos need to start and enable nfs-client.target
.
Manual mounting
For NFSv3 use this command to show the server's exported file systems:
$ showmount -e servername
For NFSv4 mount the root NFS directory and look around for available mounts:
# mount servername:/ /mountpoint/on/client
Then mount omitting the server's NFS export root:
# mount -t nfs -o vers=4 servername:/music /mountpoint/on/client
If mount fails try including the server's export root (required for Debian/RHEL/SLES, some distributions need -t nfs4
instead of -t nfs
):
# mount -t nfs -o vers=4 servername:/srv/nfs/music /mountpoint/on/client
servername
needs to be replaced with a valid hostname (not just IP address). Otherwise mounting of remote share will hang.Mount using /etc/fstab
Using fstab is useful for a server which is always on, and the NFS shares are available whenever the client boots up. Edit /etc/fstab
file, and add an appropriate line reflecting the setup. Again, the server's NFS export root is omitted.
/etc/fstab
servername:/music /mountpoint/on/client nfs defaults,timeo=900,retrans=5,_netdev 0 0
Some additional mount options to consider:
- rsize and wsize
- The
rsize
value is the number of bytes used when reading from the server. Thewsize
value is the number of bytes used when writing to the server. By default, if these options are not specified, the client and server negotiate the largest values they can both support (see nfs(5) for details). After changing these values, it is recommended to test the performance (see #Performance tuning). - soft or hard
- Determines the recovery behaviour of the NFS client after an NFS request times out. If neither option is specified (or if the
hard
option is specified), NFS requests are retried indefinitely. If thesoft
option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return an error to the calling application.
soft
timeout can cause silent data corruption in certain cases. As such, use the soft
option only when client responsiveness is more important than data integrity. Using NFS over TCP or increasing the value of the retrans
option may mitigate some of the risks of using the soft
option.- timeo
- The
timeo
value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. The default value for NFS over TCP is 600 (60 seconds). After the first timeout, the timeout value is doubled for each retry for a maximum of 60 seconds or until a major timeout occurs. If connecting to a slow server or over a busy network, better stability can be achieved by increasing this timeout value. - retrans
- The number of times the NFS client retries a request before it attempts further recovery action. If the
retrans
option is not specified, the NFS client tries each request three times. The NFS client generates a "server not responding" message after retrans retries, then attempts further recovery (depending on whether the hard mount option is in effect). - _netdev
- The
_netdev
option tells the system to wait until the network is up before trying to mount the share - systemd assumes this for NFS.
fs_passno
) to a nonzero value may lead to unexpected behaviour, e.g. hangs when the systemd automount waits for a check which will never happen.Mount using /etc/fstab with systemd
Another method is using the x-systemd.automount option which mounts the filesystem upon access:
/etc/fstab
servername:/home /mountpoint/on/client nfs _netdev,noauto,x-systemd.automount,x-systemd.mount-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0
To make systemd aware of the changes to fstab, reload systemd and restart remote-fs.target
[3].
- The
noauto
mount option will not mount the NFS share until it is accessed: useauto
for it to be available immediately.
If experiencing any issues with the mount failing due to the network not being up/available, enableNetworkManager-wait-online.service
. It will ensure thatnetwork.target
has all the links available prior to being active. - The
users
mount option would allow user mounts, but be aware it implies further options asnoexec
for example. - The
x-systemd.idle-timeout=1min
option will unmount the NFS share automatically after 1 minute of non-use. Good for laptops which might suddenly disconnect from the network. - If shutdown/reboot holds too long because of NFS, enable
NetworkManager-wait-online.service
to ensure that NetworkManager is not exited before the NFS volumes are unmounted. - Do not add the
x-systemd.requires=network-online.target
mount option as this can lead to ordering cycles within systemd [4]. systemd adds thenetwork-online.target
dependency to the unit for_netdev
mount automatically. - Using the
nocto
option may improve performance for read-only mounts, but should be used only if the data on the server changes only occasionally.
As systemd unit
Create a new .mount
file inside /etc/systemd/system
, e.g. mnt-home.mount
. See systemd.mount(5) for details.
mnt-home.mount
can only be used if you are going to mount the share under /mnt/home
. Otherwise the following error might occur: systemd[1]: mnt-home.mount: Where= setting does not match unit name. Refusing.
. If the mountpoint contains non-ASCII characters, use systemd-escape).What=
path to share
Where=
path to mount the share
Options=
share mounting options
- Network mount units automatically acquire
After
dependencies onremote-fs-pre.target
,network.target
andnetwork-online.target
, and gain aBefore
dependency onremote-fs.target
unlessnofail
mount option is set. Towards the latter aWants
unit is added as well. - Append
noauto
toOptions
preventing automatically mount during boot (unless it is pulled in by some other unit). - If you want to use a hostname for the server you want to share (instead of an IP address), add
nss-lookup.target
toAfter
. This might avoid mount errors at boot time that do not arise when testing the unit.
/etc/systemd/system/mnt-home.mount
[Unit] Description=Mount home at boot [Mount] What=172.16.24.192:/home Where=/mnt/home Options=vers=4 Type=nfs TimeoutSec=30 [Install] WantedBy=multi-user.target
ForceUnmount=true
to [Mount]
, allowing the export to be (force-)unmounted.To use mnt-home.mount
, start the unit and enable it to run on system boot.
automount
To automatically mount a share, one may use the following automount unit:
/etc/systemd/system/mnt-home.automount
[Unit] Description=Automount home [Automount] Where=/mnt/home [Install] WantedBy=multi-user.target
Disable/stop the mnt-home.mount
unit, and enable/start mnt-home.automount
to automount the share when the mount path is being accessed.
Mount using autofs
Using autofs is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares. See autofs#NFS network mounts for details.
Tips and tricks
Performance tuning
When using NFS on a network with a significant number of clients one may increase the default NFS threads from 8 to 16 or even a higher, depending on the server/network requirements:
/etc/nfs.conf
[nfsd] threads=16
It may be necessary to tune the rsize
and wsize
mount options to meet the requirements of the network configuration.
In recent linux kernels (>2.6.18) the size of I/O operations allowed by the NFS server (default max block size) varies depending on RAM size, with a maximum of 1M (1048576 bytes), the max block size of the server will be used even if nfs clients requires bigger rsize
and wsize
. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/5.8_technical_notes/known_issues-kernel
It is possible to change the default max block size allowed by the server by writing to the /proc/fs/nfsd/max_block_size
before starting nfsd. For example, the following command restores the previous default iosize of 32k:
# echo 32768 > /proc/fs/nfsd/max_block_size
max_block_size
may decrease NFS performance on modern hardware.To make the change permanent, create a systemd-tmpfile:
/etc/tmpfiles.d/nfsd-block-size.conf
w /proc/fs/nfsd/max_block_size - - - - 32768
To mount with the increased rsize
and wsize
mount options:
# mount -t nfs -o rsize=32768,wsize=32768,vers=4 servername:/srv/nfs/music /mountpoint/on/client
Furthermore, despite the violation of NFS protocol, setting async
instead of sync
or sync,no_wdelay
may potentially achieve a significant performance gain especially on spinning disks. Configure exports with this option and then execute exportfs -arv
to apply.
/etc/exports
/srv/nfs 192.168.1.0/24(rw,async,crossmnt,fsid=0) /srv/nfs/music 192.168.1.0/24(rw,async)
async
comes with a risk of possible data loss or corruption if the server crashes or restarts uncleanly.Automatic mount handling
This trick is useful for NFS-shares on a wireless network and/or on a network that may be unreliable. If the NFS host becomes unreachable, the NFS share will be unmounted to hopefully prevent system hangs when using the hard
mount option [5].
Make sure that the NFS mount points are correctly indicated in fstab:
/etc/fstab
lithium:/mnt/data /mnt/data nfs noauto 0 0 lithium:/var/cache/pacman /var/cache/pacman nfs noauto 0 0
Create the auto_share
script that will be used by cron or systemd/Timers to use ICMP ping to check if the NFS host is reachable:
/usr/local/bin/auto_share
#!/bin/bash function net_umount { umount -l -f $1 &>/dev/null } function net_mount { mountpoint -q $1 || mount $1 } NET_MOUNTS=$(sed -e '/^.*#/d' -e '/^.*:/!d' -e 's/\t/ /g' /etc/fstab | tr -s " ")$'\n'b printf %s "$NET_MOUNTS" | while IFS= read -r line do SERVER=$(echo $line | cut -f1 -d":") MOUNT_POINT=$(echo $line | cut -f2 -d" ") # Check if server already tested if [[ "${server_ok[@]}" =~ "${SERVER}" ]]; then # The server is up, make sure the share are mounted net_mount $MOUNT_POINT elif [[ "${server_notok[@]}" =~ "${SERVER}" ]]; then # The server could not be reached, unmount the share net_umount $MOUNT_POINT else # Check if the server is reachable ping -c 1 "${SERVER}" &>/dev/null if [ $? -ne 0 ]; then server_notok[${#server_notok[@]}]=$SERVER # The server could not be reached, unmount the share net_umount $MOUNT_POINT else server_ok[${#server_ok[@]}]=$SERVER # The server is up, make sure the share are mounted net_mount $MOUNT_POINT fi fi done
# Check if the server is reachable ping -c 1 "${SERVER}" &>/dev/null
with:
# Check if the server is reachable timeout 1 bash -c ": < /dev/tcp/${SERVER}/2049"in the
auto_share
script above.Make sure the script is executable.
Next check configure the script to run every X, in the examples below this is every minute.
Cron
# crontab -e
* * * * * /usr/local/bin/auto_share
systemd/Timers
/etc/systemd/system/auto_share.timer
[Unit] Description=Automount NFS shares every minute [Timer] OnCalendar=*-*-* *:*:00 [Install] WantedBy=timers.target
/etc/systemd/system/auto_share.service
[Unit] Description=Automount NFS shares After=network.target [Service] Type=oneshot ExecStart=/usr/local/bin/auto_share [Install] WantedBy=multi-user.target
Finally, enable and start auto_share.timer
.
Using a NetworkManager dispatcher
NetworkManager can also be configured to run a script on network status change.
The easiest method for mount shares on network status change is to symlink the auto_share
script:
# ln -s /usr/local/bin/auto_share /etc/NetworkManager/dispatcher.d/30-nfs.sh
However, in that particular case unmounting will happen only after the network connection has already been disabled, which is unclean and may result in effects like freezing of KDE Plasma applets.
The following script safely unmounts the NFS shares before the relevant network connection is disabled by listening for the down
, pre-down
and vpn-pre-down
events, make sure the script is executable:
/etc/NetworkManager/dispatcher.d/30-nfs.sh
#!/bin/sh # Find the connection UUID with "nmcli con show" in terminal. # All NetworkManager connection types are supported: wireless, VPN, wired... WANTED_CON_UUID="CHANGE-ME-NOW-9c7eff15-010a-4b1c-a786-9b4efa218ba9" if [ "$CONNECTION_UUID" = "$WANTED_CON_UUID" ]; then # Script parameter $1: network interface name, not used # Script parameter $2: dispatched event case "$2" in "up") mount -a -t nfs4,nfs ;; "down"|"pre-down"|"vpn-pre-down") umount -l -a -t nfs4,nfs -f >/dev/null ;; esac fi
noauto
option, remove this mount option or use auto
to allow the dispatcher to manage these mounts.Create a symlink inside /etc/NetworkManager/dispatcher.d/pre-down
to catch the pre-down
events:
# ln -s /etc/NetworkManager/dispatcher.d/30-nfs.sh /etc/NetworkManager/dispatcher.d/pre-down.d/30-nfs.sh
TLS encryption
NFS traffic can be encrypted using TLS as of Linux 6.5 using the xprtsec=tls
mount option. To begin, install the ktls-utilsAUR package on the client and server, and follow the below configuration steps for each.
Server
Create a private key and obtain a certificate containing your server's DNS name (see Transport Layer Security for more detail). These files do not need to be added to the system's trust store.
Edit /etc/tlshd.conf
to use these files, using your own values for x509.certificate
and x509.private_key
/etc/tlshd.conf
[authenticate.server] x509.certificate= /etc/nfsd-certificate.pem x509.private_key= /etc/nfsd-private-key.pem
Now start and enable tlshd.service
.
Client
Add the server's TLS certificate generated in the previous step to the system's trust store (see Transport Layer Security for more detail).
Start and enable tlshd.service
.
Now you should be able to mount the server using the server's DNS name:
# mount -o xprtsec=tls servername.domain:/ /mountpoint/on/client
Checking journalctl on the client should show that the TLS handshake was successful:
$ journalctl -b -u tlshd.service
Sep 28 11:14:46 client tlshd[227]: Built from ktls-utils 0.10 on Sep 26 2023 14:24:03 Sep 28 11:15:37 client tlshd[571]: Handshake with servername.domain (192.168.122.100) was successful
Troubleshooting
There is a dedicated article NFS/Troubleshooting.
See also
- See also Avahi, a Zeroconf implementation which allows automatic discovery of NFS shares.
- HOWTO: Diskless network boot NFS root
- Microsoft Services for Unix NFS Client info
- NFS on Snow Leopard
- http://chschneider.eu/linux/server/nfs.shtml
- How to do Linux NFS Performance Tuning and Optimization
- Linux: Tune NFS Performance
- Configuring an NFSv4-only Server