Dell PowerVault NX3500 Administrator's Guide - Page 155

CIFS ACL Corruption, CIFS Client Clock Skew

Get Dell PowerVault NX3500 PDF manuals and user guides View all Dell PowerVault NX3500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 155 highlights

CIFS ACL Corruption Description Cause Workaround CIFS ACL corruption. • 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. Check the current ACL setting in the Windows client. Redefine the ACLs for the files by using 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 recopying the whole data. c In case all file system ACLs' are corrupted you can restore all data from the NAS replication partner. CIFS Client Clock Skew Description Cause Workaround CIFS client clock skew. The client clock must be within 5 minutes range from the Kerberos server (that is Active Directory) clock. Configure the client to clock-synch with the Active Directory (as an NTP server) to avoid clock skews errors. Troubleshooting 155

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
Troubleshooting
155
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 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.