Dell PowerVault NX3500 Administrator's Guide - Page 162

NAS Container Security Violation

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 162 highlights

NAS Container Security Violation Description Cause Workaround NAS container security violation. Selecting security style for a NAS container dictates the dominant protocol to be used to set permissions on files in this volume. NFS for UNIX security style volumes and CIFS for NTFS security style volumes. Consequently, this makes some operations invalid: • Setting UNIX permissions for a file in an NTFS Security style container. • Setting UID/GID ownership for a file in an NTFS Security style container. • Setting ACL for a file in a UNIX Security style container. • Changing read-only flag for a file in a UNIX Security style container. • Setting SID/GSID ownership for a file on UNIX Security style container. The NAS container security style should reflect the main protocol used to access its files. If a user frequently needs to perform a cross-protocol security related activity, split the data into separate NAS containers based on the main access protocol. 162 Troubleshooting

  • 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
162
Troubleshooting
NAS Container Security Violation
Description
NAS container security violation.
Cause
Selecting security style for a NAS container dictates the dominant
protocol to be used to set permissions on files in this volume. NFS
for UNIX security style volumes and CIFS for NTFS security style
volumes.
Consequently, this makes some operations invalid:
•
Setting UNIX permissions for a file in an NTFS Security style
container.
•
Setting UID/GID ownership for a file in an NTFS Security style
container.
•
Setting ACL for a file in a UNIX Security style container.
•
Changing read-only flag for a file in a UNIX Security style
container.
•
Setting SID/GSID ownership for a file on UNIX Security style
container.
The NAS container security style should reflect the main protocol
used to access its files.
Workaround
If a user frequently needs to perform a cross-protocol security
related activity, split the data into separate NAS containers based
on the main access protocol.