Filter
Top Products
CIFS ACL Corruption
Description CIFS ACL corruption.
Cause
• ACLs were accidently changed by a user or script.
• ACL is corrupted after an antivirus application accidently quarantined
corresponding files.
• ACL got corrupted after data recovery by backup application due to compatibility
issues.
• ACL got corrupted after migrating data from different location by using third party
application. For example, RoboCopy.
Workaround Check the current ACL setting in the Windows client. Redefine the ACLs for the files
by using a Windows client the same way you initially defined it. Verify that you set the
ACLs as the owner of the files, directories, and shares. In case you cannot redefine
your ACLs since you currently do not have permissions, perform the following steps:
1. Restore the files from snapshots or backup.
2. In the case you have migrated the data from a different location using RoboCopy
application, there is a good chance you can restore ACLs by copying only ACLs
metadata, instead of re-copying the whole data.
3. In case all file system ACLs are corrupted, you can restore all data from the NAS
replication partner.
CIFS Client Clock Skew
Description CIFS client clock skew.
Cause The client clock must be within 5 minutes range from the Kerberos server (that is
Active Directory) clock.
Workaround Configure the client to clock-synch with the Active Directory (as an NTP server) to
avoid clock skews errors.
CIFS Client Disconnection On File Read
Description CIFS client disconnection on file read.
Cause Extreme CIFS workload during controller failover.
Workaround Client needs to reconnect and open the file again.
CIFS Client General Disconnection
Description CIFS client disconnection.
Cause In case the system identified a general issue with the CIFS service, it automatically
recovers but the failure causes all users to be disconnected and the above event to be
triggered.
Workaround If this issue repeats frequently, contact Dell.
CIFS Client Login Failure
Description CIFS client login failure.
Cause User supplied incorrect password upon connection.
172