Filter
Top Products
2. Manually create the missing directories. Set permissions to control access as
required.
3. Remove the share and communicate to the client.
CIFS Write To Read Only Volume
Description Client tries to modify a file on read-only 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 user meant to access the target system for read purposes, but also tries to
modify a file by mistake.
• The user accesses the incorrect system due to similarity in name/IP.
• The user is accessing a NAS container, which was made a replication target
without his knowledge.
Workaround In order to write to this volume, replication must be detached first. Refer the user to
the correct location.
Troubleshooting NFS Issues
Cannot Mount NFS Export
Description When attempting to mount an NFS export, the mount command fails due to various
reasons such as:
• Permission denied.
• Appliance not responding due to port mapper failure - RPC timed out or input/
output error.
• Appliance 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 export list, the appliance could not recognize the client
system through NIS, or the appliance does not accept the identity you provided.
• The NAS cluster solution 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.
• Client system’s IP address, IP range, domain name or netgroup is not in the export
list for the volume it is trying to mount from the NAS appliance.
• 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 if 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.
175