Administrator Guide

Cause This error is usually the outcome of a communication error between the FluidFS cluster and the
NIS/LDAP server. It can be a result of a network issue, directory server overload, or a software
malfunction.
Workaround Repeat the below process for each configured NIS/LDAP server, each time leaving just a single
NIS/LDAP used, starting with the problematic server.
1. Inspect the NIS/LDAP server logs and see whether the reason for the error is reported in the
logs.
2. Network tests: Try pinging the FluidFS cluster from a client located in the same subnet as the
NIS/LDAP server. Try pinging the NIS/LDAP server from a client located in the same subnet as
the FluidFS cluster.
If packet loss is evident on one of the above network tests, resolve the network issues in the
environment.
3. Using a Linux client located in the same subnet as the FluidFS cluster and configured to use the
same directory server, query the netgroup details from the NIS/LDAP server using the relevant
commands. Ensure that the reply is received in a timely manner (up to 3 seconds).
You can temporarily work around the problem by removing the netgroup restriction on the NFS
export and/or by defining an alternative directory server. Identify the relevant NFS export and the
options defined for it, while focusing on the netgroup definition. Document the used netgroup in
order to restore it once the issue is solved and remove the netgroup limitation.
NFS Mount Path Does Not Exist
Description A client tries to mount a mount path that does not exists on a NAS volume.
Cause This error usually occurs in one of the following scenarios:
● The FluidFS cluster is restored from a backup or remote replication. During restore time, the
directory structure is not complete and a few directories might not exist.
● When a client with an authorization to access a higher directory in the same path deletes or alters
a directory that is being mounted by another client. When multiple clients are accessing the same
data set, it is recommended to apply a strict permission scheme to avoid this scenario.
Workaround 1. If the FluidFS cluster is being restored, communicate the current status to the client and instruct
the client to wait for the restore process to complete.
2. In the case of another client deleting or altering a directory, there are three options:
● Restore the problematic path from a backup.
● Manually create the missing directories to enable the mount. Clients receive errors when trying
to access existing data in a deleted path.
● Remove the NFS export and communicate this to the client.
3. List all available NFS exports on the FluidFS cluster and identify the problematic NFS export. It
must have an indication that it is not accessible.
NFS Owner Restricted Operation
Description
An NFS client is not permitted to perform the requested action to the specific file.
Cause An NFS client attempted a chmod or chgrp operation while not being the owner of the file.
Workaround This is a minor, user-level issue. Frequent events of this type might indicate a malicious attempt to
access restricted data.
NFS Write to Read-Only Export
Description
An NFS client tries to perform modifications on a read-only NFS export.
Cause An NFS export can be defined as a read-only NFS export. A client accessing a read-only NFS export
cannot perform write operations or modify included files.
Workaround This event, by itself, does not require any administrative intervention.
FluidFS Administration 487