Administrator Guide

• 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 specic le.
Cause An NFS client attempted a chmod or chgrp operation while not being the owner of the le.
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 modications on a read-only NFS export.
Cause An NFS export can be dened as a read-only NFS export. A client accessing a read-only NFS export
cannot perform write operations or modify included les.
Workaround This event, by itself, does not require any administrative intervention.
NFS 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 tries to modify a le by
mistake.
• The client accesses the wrong system due to similarity in name/IP address.
• The client is accessing 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.
NFS Write to Snapshot
Description
An NFS client tries to modify a le located in a snapshot.
Cause NAS volume snapshots cannot be modied by design.
Workaround Inform the client that snapshot data cannot be modied. A snapshot is an exact representation of the
NAS volume data at the time of its creation.
FluidFS Troubleshooting
493