Unsolved

This post is more than 5 years old

2 Posts

1714

October 29th, 2015 02:00

pNFS NFSv4.1

We're trying to setup pNFS (NFSv4.1) on our VNX5400. We've followed the instructions in docu48461 starting on page 132:

1) Opened /nas/server/slot_2/config and hivers=4 was already present

2) Opened /nas/server/slot_3/config, hivers=4 was not present so added it.

3) The next step indicates to reboot the data mover but given that server_2 is active and it already has hivers=4 we skipped this step as it would be disruptive and seems unnecessary given hivers=4 was already present on slot_2 which is the active data mover.

4) Started the NFS v4 service:

server_nfs server_2 -v4 -service -start

server_nfs server_3 -v4 -service -start

5) Started the pNFS service:

server_nfs server_2 -pnfs -service -start

server_nfs server_4 -pnfs -service -start

6) I run: server_nfs server_2 -v4

And confirm both nfsv4 and pNFS are started:

server_2 :

-------------- nfsv4 server status ---------------

             *   Service Started   *

             *   pNFS service Started   *

             *   (yet operating)   *

6) Mounted our file system:

server_mount server_2 -option pnfs test_website /test_website

(I'm a little unclear if we should be mounting this to the vdm or server_2 - the instructions say server_2 but I'd assume its preferably to use vdm0?)

7) Exported the file system

server_export server_2 -Protocol nfs -option root=10.10.10.60 /test_website

8) I also set the nfs v4 domain:

server_param server_2 -facility nfsv4 -modify domain -value domain.local

server_param server_3 -facility nfsv4 -modify domain -value domain.local

9) Then I go over to my client system and edit /etc/idmapd.conf adding:

Domain = domain.local

10) Next I run rpcinfo -u 10.10.10.20 nfs which produces the following result:

program 100003 version 2 ready and waiting

program 100003 version 3 ready and waiting

rpcinfo: RPC: Program not registered

program 100003 version 4 is not available

Note you'll see it says version 4 is not available. ????

9) Despite doing that I try to mount the export from my client:

# mount -v -t nfs4 -o minorversion=1 10.10.10.20:/test_website /mnt/test/

mount.nfs4: timeout set for Thu Oct 29 04:34:31 2015

mount.nfs4: trying text-based options 'minorversion=1,addr=10.10.10.20,clientaddr=10.10.11.60'

mount.nfs4: mount(2): No such file or directory

mount.nfs4: mounting 10.10.10.20:/test_website failed, reason given by server: No such file or directory

So why is rpcinfo showing version 4 is not running and why can't I mount my export?

I do have NFSv4.1 loaded into my kernel:

# lsmod | grep nfs_layout_nfsv41_files

nfs_layout_nfsv41_files    29070  0

nfsv4                 474429  2 blocklayoutdriver,nfs_layout_nfsv41_files

nfs                   246411  3 nfsv4,blocklayoutdriver,nfs_layout_nfsv41_files

sunrpc                295293  7 nfs,rpcsec_gss_krb5,auth_rpcgss,lockd,nfsv4,blocklayoutdriver,nfs_layout_nfsv41_files

I can also mount NFSv4.1 exports on a test server I setup:

# mount.nfs4 -v -o minorversion=1 10.10.11.61:/ /mnt/test/

mount.nfs4: timeout set for Thu Oct 29 05:00:14 2015

mount.nfs4: trying text-based options 'minorversion=1,addr=10.10.11.61,clientaddr=10.10.11.60'

# ls /mnt/test/

1  2  22  23  24  25  26  27  28  3  4  bar  dmesg.file  foo  locale-archive  testfile  xinetd.d


So the problem is NOT with my client. My client is able to mount NFSv4.1 no issues.

Something is wrong on the VNX side but I can't figure out what I've missed or why its not working. I'm tempted to reboot the datamovers but that would cause us some disruption so I'd rather not have to do that.

Is there something I've missed?

Thanks,

Brad

No Responses!
No Events found!

Top