Administrator Guide
Workaround This is an informative event. The administrator may contact the locking client and request to close the
application referencing this le.
It could be that the application that opened the le did not shut down gracefully. It is recommended to
reboot the client if possible.
SMB Locking Inconsistency
Description The SMB service is interrupted due to SMB interlocking issues.
Cause There are various SMB client interlocking scenarios.
Workaround The system recovers itself automatically, an event is issued when recovered.
SMB Maximum Connections Reached
Description The maximum number of SMB connections per NAS controller has been reached.
Cause Each NAS appliance is limited to a certain number of connections.
Workaround
• If the system is in an optimal state (all NAS controllers are online) and the number of SMB clients
accessing one of the NAS controllers reaches the maximum, consider adding another NAS appliance.
• If the system is in optimal state (all NAS controllers are online) but the clients are signicantly
unbalanced between NAS controllers, rebalance the clients using Storage Manager.
• If the system is in a degraded state (one or more NAS controllers are down) and the SMB clients are
connected to the remaining NAS controller, wait until the system returns to optimal or decrease the
number of SMB clients using the system.
SMB Share Does Not Exist
Description
Client attempts to connect to a nonexistent SMB share.
Cause
• Spelling mistake on client side.
• Client is accessing the wrong server.
Workaround List the available SMB shares and verify that all SMB shares are displayed and nothing has changed
unintentionally.
Verify that you can access the problematic SMB share using a Windows client:
1. Click Run.
2. Enter the client access VIP and share name: \\<client_VIP_or_name>
\<SMB_share_name>
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:
FluidFS Troubleshooting
489