release notes | Book: 2.16, 3.0, 3.1, 3.2, 4.0, 4.1, 4.2 | Wiki | Q&A black_bg
Web: Multi-page, Single page | PDF: A4-size, Letter-size | eBook: epub black_bg

Setting up

To allow file transfers in and out of dCache using NFSv4.1/pNFS, a new NFSv4.1 door must be started. This door acts then as the mount point for NFS clients.

To enable the NFSv4.1 door, you have to change the layout file corresponding to your dCache-instance. Enable the nfs within the domain that you want to run it by adding the following line

..
[<domainName>/nfs]
nfs.version = 4.1
..

Example:

You can just add the following lines to the layout file:

..
[nfs-${host.name}Domain]
[nfs-${host.name}Domain/nfs]
nfs.version = 4.1
..

In addition to run an NFSv4.1 door you need to add exports to the /etc/exports file. The format of /etc/exports is similar to the one which is provided by Linux:

#
<path> [host [(options)]]

Where <options> is a comma separated combination of:

ro

matching clients can access this export only in read-only mode

rw

matching clients can access this export only in read-write mode

sec=krb5

matching clients must access NFS using RPCSEC_GSS authentication. The Quality of Protection (QOP) is NONE, e.g., the data is neither encrypted nor signed when sent over the network. Nevertheless the RPC packets header still protected by checksum.

sec=krb5i

matching clients have to access NFS using RPCSEC_GSS authentication. The Quality of Protection (QOP) is INTEGRITY. The RPC requests and response are protected by checksum.

sec=krb5p

matching clients have to access NFS using RPCSEC_GSS authentication. The Quality of Protection (QOP) is PRIVACY. The RPC requests and response are protected by encryption.

For example:

Example:

#
/pnfs/dcache.org/data *.dcache.org (rw,sec=krb5i)

Notice, that security flavour used at mount time will be used for client - pool comminication as well.