NFS Backend
-----------
include::attributes.txt[]
+ifdef::wiki[]
+:pve-toplevel:
+:title: Storage: NFS
+endif::wiki[]
Storage pool type: `nfs`
properties. The directory layout and the file naming conventions are
the same. The main advantage is that you can directly configure the
NFS server properties, so the backend can mount the share
-automatically. There is no need to modify '/etc/fstab'. The backend
+automatically. There is no need to modify `/etc/fstab`. The backend
can also test if the server is online, and provides a method to query
the server for exported shares.
server::
Server IP or DNS name. To avoid DNS lookup delays, it is usually
-preferrable to use an IP address instead of a DNS name - unless you
+preferable to use an IP address instead of a DNS name - unless you
have a very reliable DNS server, or list the server in the local
`/etc/hosts` file.
path::
-The local mount point (defaults to '/mnt/pve/`<STORAGE_ID>`/').
+The local mount point (defaults to `/mnt/pve/<STORAGE_ID>/`).
options::
NFS mount options (see `man nfs`).
-.Configuration Example ('/etc/pve/storage.cfg')
+.Configuration Example (`/etc/pve/storage.cfg`)
----
nfs: iso-templates
path /mnt/pve/iso-templates
Storage Features
~~~~~~~~~~~~~~~~
-NFS does not support snapshots, but the backend use `qcow2` features
+NFS does not support snapshots, but the backend uses `qcow2` features
to implement snapshots and cloning.
.Storage features for backend `nfs`
You can get a list of exported NFS shares with:
# pvesm nfsscan <server>
+
+ifdef::wiki[]
+
+See Also
+~~~~~~~~
+
+* link:/wiki/Storage[Storage]
+
+endif::wiki[]