Administrator Guide

• 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 level 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 access. Clients receive errors when trying to
access existing data in a deleted path.
• Remove the SMB share and communicate this to the client.
3. List all available SMB shares on the FluidFS cluster and identify the problematic SMB share. It must
have an indication that it is not accessible.
SMB Write to Read Only NAS Volume
Description A client tries to modify a le on a read-only NAS volume.
Cause A NAS volume is set to read-only when it is the target of a replication.
The most frequent reason for this event is either:
• The client meant to access the target system for read purposes, but also tried to modify a le by
mistake.
• The client accessed the wrong system due to similarity in name/IP address.
• The client accessed a NAS volume that was made a replication target without the client’s knowledge.
Workaround
• Refer the client to the correct NAS volume.
• In order to write to the NAS volume, replication must be terminated rst so the NAS volume becomes
standalone.
Troubleshoot NFS Issues
This section contains probable causes of and solutions to common NFS problems.
Cannot Mount NFS Export
Description
When attempting to mount an NFS export, the mount command fails due to various reasons such as:
• Permission denied.
• FluidFS cluster is not responding due to port mapper failure - RPC timed out or input/output error.
• FluidFS cluster is not responding due to program not registered.
• Access denied.
• Not a directory.
Cause
• The client connects using NFS/UDP and there is a rewall in the way.
• The client is not in the NFS export list, the FluidFS cluster could not recognize the client system
through NIS, or the FluidFS cluster does not accept the identity the client provided.
• The FluidFS cluster is down or has internal le system problems.
• The mount command got through to the port mapper, but the rpc.mountd NFS mount daemon was
not registered.
• The client system’s IP address, IP range, domain name, or netgroup is not in the NFS export list for
the NAS volume it is trying to mount from the FluidFS cluster.
• Either the remote path or the local path is not a directory.
• The client does not have root authority or is not a member of the system group. NFS mounts and
unmounts are only allowed for root users and members of the system group.
490
FluidFS Troubleshooting