4 Storage pool type: `nfs`
6 The NFS backend is based on the directory backend, so it shares most
7 properties. The directory layout and the file naming conventions are
8 the same. The main advantage is that you can directly configure the
9 NFS server properties, so the backend can mount the share
10 automatically. There is no need to modify '/etc/fstab'. The backend
11 can also test if the server is online, and provides a method to query
12 the server for exported shares.
17 The backend supports all common storage properties, except the shared
18 flag, which is always set. Additionally, the following properties are
19 used to configure the NFS server:
23 Server IP or DNS name. To avoid DNS lookup delays, it is usually
24 preferrable to use an IP address instead of a DNS name - unless you
25 have a very reliable DNS server, or list the server in the local
30 NFS export path (as listed by `pvesm nfsscan`).
32 You can also set NFS mount options:
36 The local mount point (defaults to '/mnt/pve/`<STORAGE_ID>`/').
40 NFS mount options (see `man nfs`).
42 .Configuration Example ('/etc/pve/storage.cfg')
45 path /mnt/pve/iso-templates
47 export /space/iso-templates
52 TIP: After an NFS request times out, NFS request are retried
53 indefinitely by default. This can lead to unexpected hangs on the
54 client side. For read-only content, it is worth to consider the NFS
55 `soft` option, which limits the number of retries to three.
61 NFS does not support snapshots, but the backend use `qcow2` features
62 to implement snapshots and cloning.
64 .Storage features for backend `nfs`
65 [width="100%",cols="m,m,3*d",options="header"]
66 |==============================================================================
67 |Content types |Image formats |Shared |Snapshots |Clones
68 |images rootdir vztempl iso backup |raw qcow2 vmdk subvol |yes |qcow2 |qcow2
69 |==============================================================================
74 You can get a list of exported NFS shares with:
76 # pvesm nfsscan <server>