Administrator Guide

SMB Write to Read Only NAS Volume
Description A client tries to modify a file 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 file 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 first 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 firewall 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 file 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.
Workaround If the issue is due to NFS/UDP and firewall, check whether the client mounts using UDP (this is usually the
default) and there is a firewall in the path. If a firewall exists, add an appropriate exception to the firewall.
If the issue is due to permissions:
• Verify the path you provided is correct.
• Check that you are trying to mount as root.
• Check that the system's IP address, IP range, domain name, or netgroup is in the NFS exports list.
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 file 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 file system.
462 FluidFS Administration