Difference between revisions of "NFS"
|Line 64:||Line 64:|
No special setup is required on the client-side.
No special setup is required on the client-side
==Mounting from Linux==
==Mounting from Linux==
Revision as of 05:04, 29 November 2012
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
Both client and server only require thepackage.
The NTP system is recommended to sync both the server and the clients to the highly accurate NTP servers available on the Internet.
/etc/idmapd.conf and define a Domain.
[General] Verbosity = 1 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = atomic [Mapping] Nobody-User = nobody Nobody-Group = nobody
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
# mkdir -p /srv/nfs4/music
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
/mnt/music /srv/nfs4/music none bind 0 0
Add directories to be shared and an ip address or hostname(s) of client machines that will be allowed to mount them in
/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 filesystem
Users need-not open the share to the entire subnet; one can specify a single IP address or hostname as well.
fsid=0is required for the root file system being exported.
/srv/nfs4is the NFS root here (due to the
fsid=0entry). 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 below.
For more information about all available options see
man 5 exports.
Starting the server
To start the NFS server, use:
# systemctl start nfsd.service rpc-idmapd.service rpc-mountd.service rpcbind.service
No special setup is required on the client-side when connecting to NFS 4 servers.
For NFS 2 or 3 servers see the NFSv3 article.
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
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 setup.
servername:/music /mountpoint/on/client nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0
Some additional mount options to consider are include:
- rsize=8192 and wsize=8192
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 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
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.
showmount -e servernamefrom cmd.exe
Mounting from OS X
Either export the share with the
insecure flag, and mount using Finder:
- Go > Connect to Server >
Or, mount the share using a secure port using the terminal:
# sudo mount -t nfs -o resvport servername:/ /Volumes/servername/
showmount -e servernamefrom the terminal