NFS Export Permission for Unix

[tumma]

Hi,

We hava Netapp Simulator with Data ONTAP 8.2.1 and trying to creata NFS export and mount on Unix system but geting permission denied error.

Here is the configuration

exportfs cofiguration

NetApp3> exportfs
/vol/DEST_NFS -sec=sys,rw
/vol/CLI -sec=sys,rw
/vol/new -sec=sys,rw
/vol/new2 -sec=sys,rw
NetApp3>

Mounting NFS on Linux

from the above exports, mounted /vol/DEST_NFS in Linux

[root@localhost /]# mount -t nfs 192.168.4.59:/vol/DEST_NFS /nfsshare/

[root@localhost /]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 50G 6.6G 44G 14% /
devtmpfs 895M 0 895M 0% /dev
tmpfs 904M 728K 903M 1% /dev/shm
tmpfs 904M 8.8M 895M 1% /run
tmpfs 904M 0 904M 0% /sys/fs/cgroup
/dev/mapper/centos-home 246G 76G 170G 31% /home
/dev/sda1 497M 160M 338M 33% /boot
192.168.4.59:/vol/DEST_NFS 973M 192K 973M 1% /nfsshare

[root@localhost /]# cd nfsshare/

[root@localhost nfsshare]# mkdir test
mkdir: cannot create directory ‘test’: Permission denied

[root@localhost nfsshare]#

If we create a qtree under the /vol/DEST_NFS volume and export the NFS, we are able to read and write the filers and folders.

Please suggest, whether the above procedure is correct or we missing someting.

Regards,

Sunil Tumma

[JGPSHNTAP]

Did you turn NFS on?

[tumma]

Yes.

Here is the output

NetApp3> nfs status
NFS server is running.

[rwelshman]

try

exportfs -p rw=<server ip>,root=<server ip> /vol/DEST_NFS

[tumma]

Hi,

We dont want to give root permission, can we access volume the with default RW permission.

Regards,

Sunil Tumma

[tumma]

OK.

The query is, Can i mount NFS export on Linux systems without Qtree?

If i create Qrtree under a Volume, i can able to mount and access NFS on linux systems with default permisson(rw=hstname, no root aceess), but in my case if i directly mount a volume without qtree, i am able to mount but unable to access with (rw=hostname, no root access) permissions.

Regards,

Sunil Tumma

[asdfjkl]

exportfs -c should be used to ascertain whether or not the client has the correct permissions, but in your case I would guess that you haven't given yourself root access, so the root user is treated as nobody.