You are prompted for the Storwize V7000 superuser password.
5. Log on to the Storwize V7000 Unified management CLI as admin via the
management IP and run the following command to register the new NAS SSH
key:
chstoragesystem --sonasprivkey /tmp/NAS.ppk
Working with NFS clients that fail to mount NFS shares after a
client IP change
Use this information to resolve a refused mount or Stale NFS file handle
response to an attempt to mount Network File System (NFS) shares after a client IP
change.
About this task
After a client IP change, a df -h command can return no results, as shown in the
following example:
Filesystem Size Used Avail Use% Mounted on
machinename: filename: - - - - /sharename
The ls command can return the following error:
ls: .: Stale NFS file handle
The Storwize V7000 Unified system hosting file module might display the
following error:
mgmt002st001 mountd[3055867]: refused mount
request from hostname for sharename (/): not exported
Note: The following steps do not apply if you are using NFSv4.0 server.
If one of these errors occurs, complete the following steps.
Procedure
1. Access the file module CLI as a privileged user.
2. Issue the sc onnode all /usr/sbin/exportfs -a command to flush the NFS
cache in each file module.
3. Verify that the NFS mount is successful. If the problem persists, restart the NFS
service on the file module that is refusing the mount requests from that client.
4. Verify that the NFS share mount is successful.
Working with file modules that report a stale NFS file handle
To recover from the “Stale NFS file handle” file system state on a file module, you
must suspend, reboot, and resume the file module.
About this task
Note: If the “Stale NFS file handle” message was displayed after a client IP
change, refer to “Working with NFS clients that fail to mount NFS shares after a
client IP change.”
Because of errors or conditions related to this file module, the file module
disconnected itself from the file system that was shared with the other nodes. All
of the file descriptors that were opened to the file system through this file module
have become "stale", as indicated by command output or a Stale NFS file handle
Chapter 7. Recovery procedures 403