Dell PowerVault NX3610 User Manual - Page 94

NAS Container Security Violation, Multiple Errors Received During File System Format

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

Page 94 highlights

Workaround • Powering down the NAS cluster solution controllers The file system may take a long time to clean the cache to the storage either due to lot of data, or due to an intermittent connection to the storage. During the powering down stage, the issue could be due to the OS kernel hanging on the controller or failing to sync its state to the local drive. If the file system has stopped and if one of the controllers are still up, you can physically power down the controller using the power button. If file system has not stopped, you must let it continue working. The file system reaches a 10 minute timeout, flushes its cache to the local controllers, and continues the shutdown process. 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 must 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. Multiple Errors Received During File System Format Description Cause You receive multiple errors during a file system format. Probable causes may be: • Wrong SAN IPs are used in the Dell NAS Initial Deployment Utility (IDU). • Wrong IQNs used while defining hosts in the MDSM. 94

  • 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
•
Powering down the NAS cluster solution
controllers
The file system may take a long time to clean the cache to
the storage either due to lot of data, or due to an
intermittent connection to the storage.
During the powering down stage, the issue could be due
to the OS kernel hanging on the controller or failing to
sync its state to the local drive.
Workaround
If the file system has stopped and if one of the controllers
are still up, you can physically power down the controller
using the power button.
If file system has not stopped, you must let it continue
working. The file system reaches a 10 minute timeout,
flushes its cache to the local controllers, and continues
the shutdown process.
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 must 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.
Multiple Errors Received During File System Format
Description
You receive multiple errors during a file system format.
Cause
Probable causes may be:
•
Wrong SAN IPs are used in the Dell NAS Initial
Deployment Utility (IDU).
•
Wrong IQNs used while defining hosts in the
MDSM.
94