Administrator Guide

• Check the file 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 file on a NAS volume.
Cause File ownership is UID/UNIX and the user is not privileged to access the file, or, file ownership is SID/ACL and
after translation to UID/UNIX the permissions do not allow access to the file.
Workaround
• For native access (when a SMB client accesses SID/ACL file or NFS client accesses UID/UNIX file)
change the permissions to allow access.
• For non-native access, translation rules are involved and it is recommended to contact 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).
• If a secure NFS export is not required (for example, the network is not public), ensure that the export is
insecure and retry accessing it.
NFS Mount Fails Due to Export Options
Description
This event is issued when an NFS mount fails due to export options.
Cause The export list filters client access by IP address, network, or netgroup, and screens the accessing client.
Workaround
1. Verify the relevant NFS export details. Write down all existing options so that you are able to revert to
them.
2. Remove IP address/client restrictions on the NFS export and retry the mount. If the mount succeeds,
verify that the IP address or domain is explicitly specified, or that it is part of the defined network or
netgroups. Once the mount succeeds, adjust the original options accordingly.
Pay attention to pitfall scenarios, where the network netmask is not intuitive, for example,
192.175.255.254 is part of 192.168.0.0/12 but not of 192.168.0.0/16.
FluidFS Administration 463