Filter
Top Products
156 Troubleshooting
CIFS ACL Corruption
CIFS Client Clock Skew
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 3rd 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. In case you cannot redefine your ACLs since you
currently do not have permissions, perform the following steps:
a
Restore the files from snapshots or backup.
b
In the case you have migrated the data from 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.
c
In case all file system ACLs' are corrupted you can restore all
data from the NAS replication partner.
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.