Storage pool type: nfs
The NFS backend is based on the directory backend, so it shares most
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
can also test if the server is online, and provides a method to query
the server for exported shares.
The backend supports all common storage properties, except the shared flag, which is always set. Additionally, the following properties are used to configure the NFS server:
/etc/hosts
file.
pvesm nfsscan
).
You can also set NFS mount options:
/mnt/pve/<STORAGE_ID>/
).
man nfs
).
Configuration Example (/etc/pve/storage.cfg
).
nfs: iso-templates path /mnt/pve/iso-templates server 10.0.0.10 export /space/iso-templates options vers=3,soft content iso,vztmpl
After an NFS request times out, NFS request are retried
indefinitely by default. This can lead to unexpected hangs on the
client side. For read-only content, it is worth to consider the NFS
soft
option, which limits the number of retries to three.
NFS does not support snapshots, but the backend uses qcow2
features
to implement snapshots and cloning.