Administrator Guide

• ACLs are corrupted after an anti-virus application accidentally quarantined corresponding les.
• ACLs got corrupted after data recovery by a backup application due to compatibility issues.
• ACLs got corrupted after migrating data from a dierent location by using a third-party application, for
example, RoboCopy.
Workaround Check the current ACL setting in the Windows client. Redene the ACLs for the les by using a Windows
client the same way you initially dened it. Verify that you set the ACLs as the owner of the les, directories,
and SMB shares. If you cannot redene your ACLs because you currently do not have permissions, perform
the following steps:
1 Restore the les from snapshots or a backup.
2 If you have migrated the data from a dierent location, for example, using the RoboCopy application,
there is a good chance you can restore ACLs by copying only ACLs metadata, instead of re-copying the
whole data.
3 If all le system ACLs are corrupted you can restore all data from a NAS replication partner.
SMB Client Clock Skew
Description SMB client clock skew errors.
Cause The client clock must be within 5 minutes of the Active Directory clock.
Workaround Congure the client to clock-synch with the Active Directory server (as an NTP server) to avoid clock skews
errors.
SMB Client Disconnect on File Read
Description
The SMB client is disconnected on le read.
Cause Extreme SMB workload during NAS controller failover.
Workaround The client needs to reconnect and open the le again.
SMB Client Incorrect Password Login Failure
Description
An SMB client fails to log in.
Cause The client supplied the wrong password upon connection.
Workaround
1 Interactive clients can retry with the correct password.
2 Applications and servers might need special attention as the user/password, which is usually set in a
script or conguration le, has probably expired.
SMB Delete On Close Denial
Description
Files are deleted while they are in use.
Cause If multiple users are working on the same le and one user deletes the opened le, it is marked for deletion,
and is deleted after it is closed. Until then, the le appears in its original location but the system denies any
attempt to open it.
Workaround Notify the client who tried to open the le that the le has been deleted.
498 FluidFS Administration