NetApp NFS Troubleshooting

Most "Permission denied" problems when mounting an NFS file system on a NetApp "filer" can be fixed using one of the following two methods:

1. Flushing the access cache with exportfs -f
2. Flushing the DNS cache with dns flush

Of course, first confirm the NetApp's list of exported file systems is correct using exportfs before attempting the method(s) above.

In the following example, the filer's access list has to be flushed after adding a reverse DNS record for 10.215.16.57. The filer allows read-write access of /vol/tcp_data0/tcp_data0 to tcplewb801, and has a search domain containing example.com. Previously, no reverse DNS record existed for 10.215.16.57.

# dig -x 10.215.16.57 +short
tcplewb801.example.com.

nvplenf601> exportfs -c 10.215.16.57 /vol/tcp_data0/tcp_data0
exportfs: 10.215.16.57 does not have mount access to /vol/tcp_data0/tcp_data0
nvplenf601> exportfs -f /vol/tcp_data0/tcp_data0
nvplenf601> exportfs -c 10.215.16.57 /vol/tcp_data0/tcp_data0
exportfs: 10.215.16.57 has mount access to /vol/tcp_data0/tcp_data0

Back to brandonhutchinson.com.
Last modified: 2007/06/22