Network Storage Protocols Discussions
Hello, NetApp community.
I am trying to solve following issue: I administer FAS 3020c cluster pair. I want to mount vol0 from filer and edit some files by hand.
I have both NFS and CIFS licenses. I've added my host, from which i'm trying to mount vol0, to /etc/hosts.equiv using wrfile(1). I also
added it to `options trusted.hosts 172.20.21.17' and created NFS export using command: exportfs -io rw=172.20.21.17,root=172.20.21.17 /vol/vol0
I can mount vol0, but i cannot access any files on it. Just get `Permission denied'.
But cluster partners vol0 is accessible from this host. It has exactly same settings.
How things look:
fas1> exportfs -io rw=172.20.21.17,root=172.20.21.17 /vol/vol0
fas1> options trusted.hosts 172.20.21.17
fas1> wrfile -a /etc/hosts.equiv 172.20.21.17
fas2> exportfs -io rw=172.20.21.17,root=172.20.21.17 /vol/vol0
fas2> options trusted.hosts 172.20.21.17
fas2> wrfile -a /etc/hosts.equiv 172.20.21.17
On 172.20.21.17 i see the follwoing:
$ mkdir -p /tmp/fas1
$ mkdir -p /tmp/fas2
$ ls -l /tmp
drwxr-xr-x 2 zinovik wheel 512 Mar 15 15:18 fas1/drwxr-xr-x 2 zinovik wheel 512 Mar 15 15:37 fas2/
$ sudo mount fas1:/vol/vol0 /tmp/fas1
$ sudo mount fas2:/vol/vol0 /tmp/fas2
$ ls /tmp/fas1
ls: /tmp/fas1: Permission denied
$ sudo ls /tmp/fas1
ls: fas1: Permission denied$ ls /tmp/fas2
drwxrwxrwx 6 root wheel 4096 Jan 27 18:21 fas1/drwxr-xr-x 6 root wheel 4096 Oct 2 2007 fas2/
$ mount | grep fas
fas1:/vol/vol0 on /tmp/fas1 type nfs (v3, udp, timeo=100, retrans=101)fas2:/vol/vol0 on /tmp/fas2 type nfs (v3, udp, timeo=100, retrans=101)
I've read chapter in Data ONTAP Administration Guide about how to add
administrative hosts, but it does not solve my issue. I've also searched
community forum, but found nothing related to this.
More than that i cannot also mount ETC$ share to my workstation.
I found on forum that someone was solve the issue when there was a
NAT box between filer and host, but this is not my case.
See The Solution
Check your qtree permissions. For NFS root access, the volume should have unix permissions;
View solution in original post
fas1> qtree security /vol/vol0 unix
Solved my problem.