topic Re: NFS4 issue in Active IQ Unified Manager Discussions

NFS4 issue

ASHERFAROOQ — Thu, 05 Jun 2025 06:12:33 GMT

We have NetApp 2240-2. We are using NFS4 at Filer end and following is output of various file.

exportfs

netapp40> exportfs

/vol/VMOS_vol -sec=sys,rw,root=10.0.0.100,nosuid

/vol/vol0/home -sec=sys,rw,root=10.0.0.100,nosuid

/vol/vol_sas/pksunews -sec=sys,rw=10.0.0.114,root=10.0.0.114

/vol/vol_sas -sec=sys,rw,root=10.0.0.100,nosuid

/vol/vol0 -sec=sys,ro,rw=10.0.0.100,root=10.0.0.100,nosuid

/vol/vol_sas/pksundev -sec=sys,rw=10.0.0.110,root=10.0.0.110

Sun Server

# ps -ef |grep nfs

daemon 504 1 0 Dec 20 ? 0:40 /usr/lib/nfs/nfsmapid

daemon 503 1 0 Dec 20 ? 0:00 /usr/lib/nfs/nfs4cbd

daemon 505 1 0 Dec 20 ? 0:00 /usr/lib/nfs/statd

root 752 1 0 Dec 20 ? 708:36 /usr/lib/nfs/nfsd

daemon 539 1 0 Dec 20 ? 0:00 /usr/lib/nfs/lockd

root 750 1 0 Dec 20 ? 0:04 /usr/lib/nfs/mountd

root 9848 5529 0 11:42:02 pts/3 0:00 grep nfs

ERROR:

# mount -F nfs -o vers=4 <filer>:/vol/vol_sas/pksundev /nfsfiler

nfs mount: mount: /nfsfiler: Permission denied

Kindly advice.

Re: NFS4 issue

bondbhola — Thu, 10 Jan 2013 09:17:15 GMT

Hi Farooq,

Please check the security style of volume and qtree, it must me unix, if it is ntfs then you have to do user mapping.

If your qtree and volume security style is ntfs then change it to unix and then try

Thanks,

Bhola Gond

Re: NFS4 issue

ASHERFAROOQ — Thu, 10 Jan 2013 09:24:18 GMT

It is already unix

netapp40> qtree status

Volume Tree Style Oplocks Status

-------- -------- ----- -------- ---------

vol_sas pksunews unix enabled normal

netapp40> options wafl.default_security_style

wafl.default_security_style unix

Re: NFS4 issue

bondbhola — Thu, 10 Jan 2013 09:30:06 GMT

Please try to mount this with nfs version 2 and 3.

Pleae let me know the result.

Re: NFS4 issue

ASHERFAROOQ — Thu, 10 Jan 2013 09:33:08 GMT

it work with nfs version 3

Re: NFS4 issue

bondbhola — Thu, 10 Jan 2013 09:39:17 GMT

Hi Farooq,

This is the bug of netapp, i have the same issue. i will share with you the bug number later.

Thanks,

Bhola Gond