Administrator Guide

If the FluidFS cluster is not responding due to a port mapper failure:
• Check the FluidFS cluster status.
• Check the network connection by trying to NFS mount from some other system.
• Verify whether other clients experience the same problem.
If the FluidFS cluster is not responding due to the program not being registered, check if the port mapper
on your client is up.
If the issue is due to access denied:
• Get a list of the FluidFS cluster exported le systems using the command:
showmount -e <client_VIP_or_name>
• Check the system name or netgroup name is not in the user list for the le system.
• Check the le systems related to the NFS export through Storage Manager.
If the issue is due to the directory, check the spelling in your command and try to run the mount
command on both directories.
NFS Export Does Not Exist
Description Attempted to mount an export that does not exist.
Cause This failure is commonly caused by spelling mistakes on the client system or when accessing the wrong
server.
Workaround
1. Check the available NFS exports on the FluidFS cluster; verify that all the required exports exist.
2. On the problematic client, verify that the relevant export is available to this client:
% showmount -e <client_VIP_or_name>
Export list for <client_VIP_or_name>:
/abc 10.10.10.0
/xyz 10.10.10.0
If the NFS export is available, review the NFS export name spelling in the relevant mount command
on the client. It is recommended to copy and paste the NFS export name from the showmount
output to the mount command.
NFS File Access Denied
Description
This event is issued when an NFS client does not have enough permissions for the le on a NAS volume.
Cause File ownership is UID/UNIX and the user is not privileged to access the le, or, le ownership is SID/ACL
and after translation to UID/UNIX the permissions do not allow access to the le.
Workaround
• For native access (when a SMB client accesses SID/ACL le or NFS client accesses UID/UNIX le)
change the permissions to allow access.
• For non-native access, translation rules are involved and it is recommended to contact Dell Technical
Support.
NFS Insecure Access to Secure Export
Description
A client tries to access a secure export from an insecure port.
Cause The secure NFS export requirement means that the accessing clients must use a well-known port (below
1024), which usually means that they must be root (uid=0) on the client.
Workaround Identify the relevant NFS export and verify that it is set as secure (requires secure client port).
• If the NFS export must remain secure, see the NFS client documentation in order to issue the mount
request from a well-known port (below 1024).
FluidFS Troubleshooting
653