Difference between revisions of "NFS"

From ArchWiki
Jump to: navigation, search
m (→‎Mounting From Linux)
(20 intermediate revisions by 10 users not shown)
Line 1: Line 1:
 
[[Category:Networking]]
 
[[Category:Networking]]
 +
[[de:Network File System]]
 
[[it:NFSv4]]
 
[[it:NFSv4]]
 
[[zh-CN:NFS]]
 
[[zh-CN:NFS]]
Line 5: Line 6:
 
{{Article summary text|Article covers configuration of NFSv4 which is an open standard network file sharing protocol.}}
 
{{Article summary text|Article covers configuration of NFSv4 which is an open standard network file sharing protocol.}}
 
{{Article summary heading|Related}}
 
{{Article summary heading|Related}}
 +
{{Article summary wiki|NFS Troubleshooting}} - Dedicated article for common problems and solutions.
 
{{Article summary wiki|NFSv3}} - Deprecated v3 format.
 
{{Article summary wiki|NFSv3}} - Deprecated v3 format.
 
{{Article summary end}}
 
{{Article summary end}}
 +
From [[Wikipedia: Network File System|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.
  
 +
This article covers the installation of NFSv4.
 
==Installing==
 
==Installing==
−
Both client and server only require the {{Pkg|nfs-utils}} package.
+
Both client and server only require the [[Pacman|installation]] of the {{Pkg|nfs-utils}} package.
  
 
{{Note|It is HIGHLY recommended to use a time sync daemon on ALL nodes of your network to keep client/server clocks in sync.  Without accurate clocks on all nodes, NFS can introduce unwanted delays!}}
 
{{Note|It is HIGHLY recommended to use a time sync daemon on ALL nodes of your network to keep client/server clocks in sync.  Without accurate clocks on all nodes, NFS can introduce unwanted delays!}}
Line 15: Line 19:
 
The [[NTP]] system is recommended to sync both the server and the clients to the highly accurate NTP servers available on the Internet.  
 
The [[NTP]] system is recommended to sync both the server and the clients to the highly accurate NTP servers available on the Internet.  
  
−
==Configuring==
+
==Configuration==
  
 
===Server===
 
===Server===
 
==== ID mapping ====
 
==== ID mapping ====
−
Edit {{ic|/etc/idmapd.conf}} and define a Domain.
+
Edit {{ic|/etc/idmapd.conf}} and set the {{ic|Domain}} field to your domain name.
  
−
Example:
+
{{hc|/etc/idmapd.conf|<nowiki>
−
[General]
+
[General]
 
   
 
   
−
Verbosity = 1
+
Verbosity = 1
−
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
+
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
−
'''Domain = atomic'''
+
Domain = atomic
−
+
 
−
[Mapping]
+
[Mapping]
−
 
−
Nobody-User = nobody
 
−
Nobody-Group = nobody
 
  
 +
Nobody-User = nobody
 +
Nobody-Group = nobody
 +
</nowiki>}}
 
==== File system ====
 
==== File system ====
 
{{Note|For security reasons, it is recommended to use an NFS export root which will keep users limited to that mount point only.  The following example illustrates this concept.}}
 
{{Note|For security reasons, it is recommended to use an NFS export root which will keep users limited to that mount point only.  The following example illustrates this concept.}}
Line 38: Line 42:
 
Define any NFS shares in {{ic|/etc/exports}} which are relative to the NFS root.  In this example, the NFS root will be {{ic|/srv/nfs4}} and we will be sharing {{ic|/mnt/music}}.
 
Define any NFS shares in {{ic|/etc/exports}} which are relative to the NFS root.  In this example, the NFS root will be {{ic|/srv/nfs4}} and we will be sharing {{ic|/mnt/music}}.
  
−
# mkdir -p /srv/nfs4/music
+
{{bc|# mkdir -p /srv/nfs4/music}}
 +
 
 +
Read/Write permissions must be set on the music directory so clients may write to it.
  
 
Now mount the actual target share, {{ic|/mnt/music}} to the NFS share via the mount command:
 
Now mount the actual target share, {{ic|/mnt/music}} to the NFS share via the mount command:
  
−
# mount --bind /mnt/music /srv/nfs4/music
+
{{bc|# mount --bind /mnt/music /srv/nfs4/music}}
  
−
To make it stick across server reboots, add the bind mount to {{ic|/etc/fstab}}:
+
To make it stick across server reboots, add the bind mount to {{ic|fstab}}:
−
/mnt/music /srv/nfs4/music  none  bind  0  0
+
{{hc|/etc/fstab|
 +
/mnt/music /srv/nfs4/music  none  bind  0  0
 +
}}
  
 
==== Exports ====
 
==== Exports ====
−
Add directories to be shared and an ip address or hostname(s) of client machines that will be allowed to mount them in {{ic|/etc/exports}}:
+
Add directories to be shared and an ip address or hostname(s) of client machines that will be allowed to mount them in {{ic|exports}}:
−
/srv/nfs4/ 192.168.0.1/24(rw,fsid=0,no_subtree_check)
+
{{hc|/etc/exports|<nowiki>
−
/srv/nfs4/music 192.168.0.1/24(rw,no_subtree_check,nohide) # note the nohide option which is applied to mounted directories on the filesystem
+
/srv/nfs4/ 192.168.0.1/24(rw,fsid=0,no_subtree_check)
 +
/srv/nfs4/music 192.168.0.1/24(rw,no_subtree_check,nohide) # note the nohide option which is applied to mounted directories on the file system.
 +
</nowiki>}}
  
 
Users need-not open the share to the entire subnet; one can specify a single IP address or hostname as well.
 
Users need-not open the share to the entire subnet; one can specify a single IP address or hostname as well.
  
−
{{Note|The {{ic|1=fsid=0}} is required for the root file system being exported. {{ic|/srv/nfs4}} is the NFS root here (due to the {{ic|1=fsid=0}} entry). Everything else that you want to be shared over NFS must be accessible under {{ic|/srv/nfs4}}. Setting an NFS root is required. For exporting directories outside the NFS root, see below.}}
+
See {{ic|man exports}} for detailed settings information.
 +
 
 +
{{Note|The {{ic|1=fsid=0}} is required for the root file system being exported. {{ic|/srv/nfs4}} is the NFS root here (due to the {{ic|1=fsid=0}} entry). Everything else that you want to be shared over NFS must be accessible under {{ic|/srv/nfs4}}. Setting an NFS root is required. For exporting directories outside the NFS root, see above.}}
 
For more information about all available options see {{ic|man 5 exports}}.
 
For more information about all available options see {{ic|man 5 exports}}.
 +
 +
If you modify {{ic|/etc/exports}} while the server is running, you must reexport them for changes to take effect:
 +
{{bc|# exportfs -ra}}
  
 
====Starting the server====
 
====Starting the server====
  
−
To start the NFS server, use:
+
The services for the NFS server are {{ic|rpc-idmapd.service}} and {{ic|rpc-mountd.service}}.
−
# systemctl start nfsd.service rpc-idmapd.service rpc-mountd.service rpcbind.service
+
 
 +
Start them and configure them to start at boot. Read [[Daemons]] for more details.
 +
 
 +
Note that these units require others, which are launched automatically by [[systemd]].
  
 
===Client===
 
===Client===
−
The client configuration only involves editing {{ic|/etc/idmapd.conf}} so that the '''Domain''' matches the one specified in the server's config:
+
Clients need {{Pkg|nfs-utils}} to connect, but no special setup is required when connecting to NFS 4 servers.
−
 
 
−
Example:
 
−
[General]
 
−
 
−
Verbosity = 1
 
−
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
 
−
'''Domain = atomic'''
 
−
 
−
[Mapping]
 
−
 
−
Nobody-User = nobody
 
−
Nobody-Group = nobody
 
−
 
−
[Translation]
 
−
Method = nsswitch
 
  
−
==Mounting From Linux==
+
====Mounting from Linux====
 
Show the server's exported filesystems:
 
Show the server's exported filesystems:
−
$ showmount -e servername
+
{{bc|$ showmount -e servername}}
  
 
Then just mount as normal:  
 
Then just mount as normal:  
−
# mount -t nfs4 servername:/music /mountpoint/on/client
+
{{bc|# mount -t nfs4 servername:/music /mountpoint/on/client}}
  
−
===Using fstab===
+
=====/etc/fstab Settings=====
−
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 setup.
+
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.
−
Example:
+
{{hc|/etc/fstab|<nowiki>
−
servername:/music  /mountpoint/on/client  nfs4  rsize=8192,wsize=8192,timeo=14,intr 0 0
+
servername:/music  /mountpoint/on/client  nfs4  rsize=8192,wsize=8192,timeo=14,intr 0 0
 +
</nowiki>}}
  
 
{{Note|Additional mount options can be specified here. Consult the NFS man page for further information.}}
 
{{Note|Additional mount options can be specified here. Consult the NFS man page for further information.}}
 
Some additional mount options to consider are include:
 
Some additional mount options to consider are include:
  
−
*rsize=8192 and wsize=8192
+
* {{ic|1=rsize=8192}} and {{ic|1=wsize=8192}}
−
*timeo=14
+
* {{ic|1=timeo=14}}
−
*intr
+
* {{ic|1=intr}}
  
−
The rsize value is the number of bytes used when reading from the server. The wsize value is the number of bytes used when writing to the server. The default for both is 1024, but using higher values such as 8192 can improve throughput.  This is not universal.  It is recommended to test after making this change.
+
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. The default for both is 1024, but using higher values such as 8192 can improve throughput.  This is not universal.  It is recommended to test after making this change.
  
−
The timeo value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. 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 performance can be achieved by increasing this timeout value.  
+
The {{ic|timeo}} value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. 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 performance can be achieved by increasing this timeout value.  
  
−
The intr option allows signals to interrupt the file operation if a major timeout occurs for a hard-mounted share.
+
The {{ic|intr}} option allows signals to interrupt the file operation if a major timeout occurs for a hard-mounted share.
  
−
===Using autofs===
+
=====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.
  
−
== Mounting from Windows ==
+
==== Mounting from Windows ====
 
{{Warning|Serious performance issues may occur (it randomly takes 30-60 seconds to display a folder, 2 MB/s file copy speed on gigabit LAN, ...) to which Microsoft does not have a solution yet.[https://social.technet.microsoft.com/Forums/en-CA/w7itpronetworking/thread/40cc01e3-65e4-4bb6-855e-cef1364a60ac]}}
 
{{Warning|Serious performance issues may occur (it randomly takes 30-60 seconds to display a folder, 2 MB/s file copy speed on gigabit LAN, ...) to which Microsoft does not have a solution yet.[https://social.technet.microsoft.com/Forums/en-CA/w7itpronetworking/thread/40cc01e3-65e4-4bb6-855e-cef1364a60ac]}}
−
{{note|Only the Enterprise and Ultimate versions of Windows 7 include "Client for NFS"}}
+
{{note|Only the Ultimate and Enterprise editions of Windows 7 and the Enterprise edition of Windows 8 include "Client for NFS"}}
 
NFS shares can be mounted from windows if the "Client for NFS" service is actived (which it is not by default).
 
NFS shares can be mounted from windows if the "Client for NFS" service is actived (which it is not by default).
 
To install the service go to "Programs and features" either through the control panel or by typing it in the search box from the start menu and click on "Turn Windows features on or off". Locate the "Services for NFS" and activate it as well as both subservices ("Administrative tools" and "Client for NFS").
 
To install the service go to "Programs and features" either through the control panel or by typing it in the search box from the start menu and click on "Turn Windows features on or off". Locate the "Services for NFS" and activate it as well as both subservices ("Administrative tools" and "Client for NFS").
Line 116: Line 120:
 
Some global options can be set by opening the "Services for Network File System" (locate it with the search box) and right clicking on the client->properties.  
 
Some global options can be set by opening the "Services for Network File System" (locate it with the search box) and right clicking on the client->properties.  
  
−
{{Warning|Under Windows the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run {{ic|showmount -e servername}} from cmd.exe}}
+
{{Warning|Under Windows the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run {{ic|showmount -e servername}} from '''cmd.exe'''}}
  
−
== Mounting from OS X ==
+
==== Mounting from OS X ====
−
{{note|OS X by default uses a insecure (>1024) port to mount a share.}}
+
{{note|OS X by default uses an insecure (>1024) port to mount a share.}}
 
Either export the share with the {{ic|insecure}} flag, and mount using Finder:
 
Either export the share with the {{ic|insecure}} flag, and mount using Finder:
−
: Go > Connect to Server > {{ic|nfs://servername/}}
+
 
 +
{{ic|Go}} > {{ic|Connect to Server}} > {{ic|nfs://servername/}}
  
 
Or, mount the share using a secure port using the terminal:
 
Or, mount the share using a secure port using the terminal:
−
# sudo mount -t nfs -o resvport servername:/ /Volumes/servername/
+
{{bc|# sudo mount -t nfs -o resvport servername:/ /Volumes/servername/}}
  
 
{{Warning|Under OS X the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run {{ic|showmount -e servername}} from the terminal}}
 
{{Warning|Under OS X the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run {{ic|showmount -e servername}} from the terminal}}
  
−
==Troubleshooting==
+
== Troubleshooting ==
−
===exportfs: /etc/exports:2: syntax error: bad option list===
+
''There is a dedicated article [[NFS Troubleshooting]].''
−
Delete all space from the option list in {{ic|/etc/exports}}
 
−
 
 
−
===mount.nfs4: No such device===
 
−
Check that you have loaded the {{ic|nfs}} module
 
−
lsmod | grep nfs
 
−
and if previous returns empty or only nfsd-stuff, do
 
−
modprobe nfs
 
−
 
 
−
===mount.nfs4: access denied by server while mounting===
 
−
Check that the permissions on your client's folder are correct. Try using 755.
 
−
 
 
−
=== Permissions issues ===
 
−
If you find that you cannot set the permissions on files properly, make sure the user/group you are chowning are on both the client and server.
 
−
If that does not help, try modifying these lines in {{ic|/etc/conf.d/nfs-common.conf}}
 
−
{{bc|<nowiki>
 
−
# /etc/conf.d/nfs-common.conf
 
−
 
 
−
# Do you want to start the statd daemon? It is not needed for NFSv4.
 
−
NEED_STATD="no"
 
−
 
 
−
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
 
−
NEED_IDMAPD="yes"
 
−
</nowiki>}}
 
−
Restart the nfs-common daemon for the changes to take effect.
 
−
I restarted all the other daemons as well, just to be sure.
 
−
 
 
−
=== Group/gid permissions issues ===
 
−
If NFS shares mount fine, and are fully accessible to the owner, but not to group members; check the number of groups that user belongs to. NFS has a limit of 16 on the number of groups a user can belong to. If you have users with more then this, you need to enable the {{ic|--manage-gids}} start-up flag for {{ic|rpc.mountd}} on the NFS server.
 
−
 
 
−
/etc/conf.d/nfs-server.conf
 
−
 
−
# Options for rpc.mountd.
 
−
# If you have a port-based firewall, you might want to set up
 
−
# a fixed port here using the --port option.
 
−
# See rpc.mountd(8) for more details.
 
−
 
−
MOUNTD_OPTS="--manage-gids"
 
−
 
 
−
=== Lock problems ===
 
−
If you got error such as this:
 
−
mount.nfs: rpc.statd is not running but is required for remote locking.
 
−
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
 
−
mount.nfs: an incorrect mount option was specified
 
−
 
 
−
To fix this, you need to change the "NEED_STATD" value in:
 
−
 
 
−
/etc/conf.d/nfs-common.conf
 
−
 
 
−
NEED_STATD="no"
 
−
 
 
−
Remember to start all the services - ''nfsd.service rpc-idmapd.service rpc-mountd.service rpcbind.service'', not just the nfsd.
 

Revision as of 17:58, 22 January 2013

zh-CN:NFS Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki - Dedicated article for common problems and solutions. Template:Article summary wiki - Deprecated v3 format. Template:Article summary end 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.

This article covers the installation of NFSv4.

Installing

Both client and server only require the installation of the nfs-utils package.

Note: It is HIGHLY recommended to use a time sync daemon on ALL nodes of your network to keep client/server clocks in sync. Without accurate clocks on all nodes, NFS can introduce unwanted delays!

The NTP system is recommended to sync both the server and the clients to the highly accurate NTP servers available on the Internet.

Configuration

Server

ID mapping

Edit /etc/idmapd.conf and set the Domain field to your domain name. 

/etc/idmapd.conf
[General]
 
Verbosity = 1
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = atomic

[Mapping]

Nobody-User = nobody
Nobody-Group = nobody

File system

Note: For security reasons, it is recommended to use an NFS export root which will keep users limited to that mount point only. The following example illustrates this concept.

Define any NFS shares in /etc/exports which are relative to the NFS root. In this example, the NFS root will be /srv/nfs4 and we will be sharing /mnt/music. 

# mkdir -p /srv/nfs4/music

Read/Write permissions must be set on the music directory so clients may write to it.

Now mount the actual target share, /mnt/music to the NFS share via the mount command: 

# mount --bind /mnt/music /srv/nfs4/music

To make it stick across server reboots, add the bind mount to fstab: 

/etc/fstab
/mnt/music /srv/nfs4/music  none   bind   0   0

Exports

Add directories to be shared and an ip address or hostname(s) of client machines that will be allowed to mount them in exports: 

/etc/exports
/srv/nfs4/ 192.168.0.1/24(rw,fsid=0,no_subtree_check)
/srv/nfs4/music 192.168.0.1/24(rw,no_subtree_check,nohide) # note the nohide option which is applied to mounted directories on the file system.

Users need-not open the share to the entire subnet; one can specify a single IP address or hostname as well.

See man exports for detailed settings information.

Note: The fsid=0 is required for the root file system being exported. /srv/nfs4 is the NFS root here (due to the fsid=0 entry). Everything else that you want to be shared over NFS must be accessible under /srv/nfs4. Setting an NFS root is required. For exporting directories outside the NFS root, see above.

For more information about all available options see man 5 exports.

If you modify /etc/exports while the server is running, you must reexport them for changes to take effect: 

# exportfs -ra

Starting the server

The services for the NFS server are rpc-idmapd.service and rpc-mountd.service.

Start them and configure them to start at boot. Read Daemons for more details.

Note that these units require others, which are launched automatically by systemd.

Client

Clients need nfs-utils to connect, but no special setup is required when connecting to NFS 4 servers.

Mounting from Linux

Show the server's exported filesystems: 

$ showmount -e servername

Then just mount as normal: 

# mount -t nfs4 servername:/music /mountpoint/on/client
/etc/fstab Settings

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. 

/etc/fstab
servername:/music   /mountpoint/on/client   nfs4   rsize=8192,wsize=8192,timeo=14,intr	0 0
Note: Additional mount options can be specified here. Consult the NFS man page for further information.

Some additional mount options to consider are include:

  • rsize=8192 and wsize=8192
  • timeo=14
  • intr

The rsize value is the number of bytes used when reading from the server. The wsize value is the number of bytes used when writing to the server. The default for both is 1024, but using higher values such as 8192 can improve throughput. This is not universal. It is recommended to test after making this change.

The timeo value is the amount of time, in tenths of a second, to wait before resending a transmission after an RPC timeout. 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 performance can be achieved by increasing this timeout value.

The intr option allows signals to interrupt the file operation if a major timeout occurs for a hard-mounted share.

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.

Mounting from Windows

Warning: Serious performance issues may occur (it randomly takes 30-60 seconds to display a folder, 2 MB/s file copy speed on gigabit LAN, ...) to which Microsoft does not have a solution yet.[1]
Note: Only the Ultimate and Enterprise editions of Windows 7 and the Enterprise edition of Windows 8 include "Client for NFS"

NFS shares can be mounted from windows if the "Client for NFS" service is actived (which it is not by default). To install the service go to "Programs and features" either through the control panel or by typing it in the search box from the start menu and click on "Turn Windows features on or off". Locate the "Services for NFS" and activate it as well as both subservices ("Administrative tools" and "Client for NFS").

Some global options can be set by opening the "Services for Network File System" (locate it with the search box) and right clicking on the client->properties.

Warning: Under Windows the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run showmount -e servername from cmd.exe

Mounting from OS X

Note: OS X by default uses an insecure (>1024) port to mount a share.

Either export the share with the insecure flag, and mount using Finder:

Go > Connect to Server > nfs://servername/

Or, mount the share using a secure port using the terminal: 

# sudo mount -t nfs -o resvport servername:/ /Volumes/servername/
Warning: Under OS X the share is addressed by its full path on the server, not just the path relative to the nfsroot! If in doubt run showmount -e servername from the terminal

Troubleshooting

There is a dedicated article NFS Troubleshooting.

Retrieved from "https://wiki.archlinux.org/index.php?title=NFS&oldid=244831"