nfs permission denied

[Brian Lee_4]

I configure /etc/exports file and export with exportfs -a but nfs client server cannot mount those directories in /etc/exports.
I got "Permission denied" message.
In client, nfsd and rpc daemons are running.
I check nfs server with showmount -e and check /etc/xtab file but I can not find any problem with nfs server.

seauxcp1 => nfs server
seauxcp2 => nfs client

seauxcp1:/etc#cat xtab
/export/usr/sap/trans -root=seauxcp1:seauxcd1:crm_dbprd:CRM_DBPRD:seacrmap:seauxcp2,access=seauxcp1:
seauxcd1:crm_dbprd:CRM_DBPRD:seacrmap:seauxcp2
/sapmnt/NCP -root=seacrmap:seauxcp2,access=seacrmap:seauxcp2
/interface -root=seacrmap:seauxcp2,access=seacrmap:seauxcp2
seauxcp1:/etc#showmount -e
export list for seauxcp1:
/export/usr/sap/trans seauxcp1,seauxcd1,crm_dbprd,CRM_DBPRD,seacrmap,seauxcp2
/sapmnt/NCP seacrmap,seauxcp2
/interface seacrmap,seauxcp2

[RAC_1]

Post /etc/exports file on server.

are you mounting the file system as root.
By default root is teeated as unknown user.

If you want to mount with root, you have to have root=server_name option in /etc/exports file on server side.

[Steven E. Protter]

The best I can do is upload a working limited access /etc/exports file for you.

For context, this servers hostname is tzfat, there are three others, jufprod, hebron and moriah.

See attachment as a working reference.

The /images directory is exported for Ignite recoveries.

SEP

[Todd McDaniel_1]

You didnt say if you have nfs and rpc running on your CLIENT system?




Also, I had a situation where the hostname was different that the nslookup name... the hostname was merely an alias of the real name b/c there was an "hostnamea" and "hostnameb" b/c we had to cards for splitting data from the OS traffic...

make sure the hostname is the same as the nslookup says.

Also,

[Helen French]

Well, permission denied message can come becuase of lot of reasons. Try restarting all daemons on the server and client side and see it will work. Check if you can mount the exported directories from any other client. Try exporting another directory without any special options and see if it's working. If yes, then apply special options one by one.

This document will be helpful too (TKB #TFKBRC00004818):

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062921651

[Brian Lee_4]

Other NFS clients can mount those directories but only seauxcp2 can not.

exports file is like the following.

/export/usr/sap/trans -root=seauxcp1:seauxcd1:crm_dbprd:CRM_DBPRD:seacrmap:seauxcp2,access=seauxcp1:
\
seauxcd1:crm_dbprd:CRM_DBPRD:seacrmap:seauxcp2
/sapmnt/NCP -root=seacrmap:seauxcp2,access=seacrmap:seauxcp2
/interface -root=seacrmap:seauxcp2,access=seacrmap:seauxcp2

[Todd McDaniel_1]

Brian,

Running out of ideas here, I would stop and restart the procs on the client as stated above.

Also, I would check the mountpoint again. Does it have the right permissions?

Additionally, Can you please post what rpc processes are running on the client along with nfs procs?

[Helen French]

If other clients can mount those directories, then it's not an issue with server side, but client side. Your exports file should be fine in this case. Check your nfs configuration on the client side and compare with others. Check the NFS version on both server and client side. It should be same in order to mount it on client side. Also apply latest NFS cumulative patches on client system.

[Kevin Wright]

make sure dns is resolving correctly, both forward and the reverse records. If so, I would run mountd in debug mode on your server,

kill -SIGUSR2

This is a toggle, so issue the same command to turn it off.

log file is /var/adm/mountd.log