Over in Latest - pNFS Admin Documentation, Lisa Week has a wiki entry which tells you how to configure a pNFS community for testing our bits. I do things a little different when I'm testing bits to put out on OpenSolaris.

The primary difference is that I need a NFSv4 share and I also need to configure the exports to support the NFS cthon tests. I.e., I need root access.

Configuring the mds

[root@pnfs-9-10 ~]> zpool create -f data /dev/dsk/c1t0d0s7
[root@pnfs-9-10 ~]> zfs create data/nfs4
[root@pnfs-9-10 ~]> zfs set sharenfs=rw,anon=0 data/nfs4
[root@pnfs-9-10 ~]> mdsadm -o add -t auth -a ip=10.1.233.50
adding: IP Addr - 10.1.233.50

This has the hidden effect of making sure the NFS server module is loaded in memory. The act of sharing will do that. I also have anon=0 which effectively allows root from any machine.

Configuring the ds

[root@pnfs-9-08 ~]> zpool create -f data /dev/dsk/c2t0d0s7
[root@pnfs-9-08 ~]> zfs create data/nfs4
[root@pnfs-9-08 ~]> zfs set sharenfs=rw,anon=0 data/nfs4
[root@pnfs-9-08 ~]> zfs create -t pnfsdata data/pnfs
[root@pnfs-9-08 ~]> dservadm addstor data/pnfs
[root@pnfs-9-08 ~]> dservadm addmds 10.1.233.52.8.1
[root@pnfs-9-08 ~]> dservadm enable

Again, while I appear to skip some steps from the Latest - pNFS Admin Documentation, they are being done implicitly. The zfs set sharenfs takes place of the share commands in the wiki. But please follow the wiki if you are unsure about what to do.

So I've set up the DS and also enabled it such that I can test NFSv4 against it as well.