Administrator Guide

SMB Share Name Truncated In Event After Mapping SMB Share
Description After a client maps a SMB share, the following event is generated and the SMB share name is truncated in the
event. In this example, the SMB share name is share1_av.
SMB client connection failure. Un-available share \\172.22.151.106\share1_a
Cause This is a known issue with Windows. Windows attempts to map the SMB share by its name and also by the
name truncated by one character.
Workaround This event can be safely ignored.
SMB Path Share Not Found
Description Client accessed a share that refers to a nonexistent directory in the 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 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.
500 FluidFS Administration