Scribd
Upload
492 views

NetApp NFS Troubleshooting

Most "Permission denied" errors when mounting an NFS file system on a NetApp filer can be resolved by flushing the access cache or DNS cache. It is important to first confirm the filer's exported file system list is correct before trying these methods. The example shows adding a reverse DNS record for an IP address and then flushing the access cache allowed the filer to grant read/write access to a volume.

Uploaded by

Avinash Hiwarale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
492 views

NetApp NFS Troubleshooting

Most "Permission denied" errors when mounting an NFS file system on a NetApp filer can be resolved by flushing the access cache or DNS cache. It is important to first confirm the filer's exported file system list is correct before trying these methods. The example shows adding a reverse DNS record for an IP address and then flushing the access cache allowed the filer to grant read/write access to a volume.

Uploaded by

Avinash Hiwarale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

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
! Flushing the "NS cache with dns flush
#f course$ first confirm the NetApp%s list of exported file systems is correct using exportfs
before attempting the method&s' abo(e
)n the following example$ the filer%s access list has to be flushed after adding a re(erse "NS
record for 1*!1+1,+- .he filer allows read/write access of
/vol/tcp_data0/tcp_data0 to tcplewb801$ and has a search domain containing
example.com Pre(iously$ no re(erse "NS record existed for 1*!1+1,+-
# dig -x 10.215.16.57 +short
tcplewb801.example.com.
nvplenf601> exportfs -c 10.215.16.57 /vol/tcp_data0/tcp_data0
exportfs: 10.1!.16.!" 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.1!.16.!" has mount access to
/vol/tcp_data0/tcp_data0

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy