Installation manual

Adding a Managed Volume
Adding a Share
9-36 CLI Storage-Management Guide
The output displays the translation at each share. For example, the following
command sequence discovers that the shares behind the ‘medarcv~/rcrds’ volume
have different SIDs for the ‘pharmacists’ group:
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# volume /rcrds
bstnA6k(gbl-ns-vol[medarcv~/rcrds])# show sid-translation pharmacists
SID Translations:
Share rx
SID: S-1-5-21-1454471165-492894223-682003330-1006
Name: MEDARCH\pharmacists (group)
Share charts
SID: S-1-5-21-1454471165-492894223-682003330-1006
Name: MEDARCH\pharmacists (group)
Share bulk
SID: S-1-5-21-2006398761-1897008245-3502739112-1007
Name: PV770N\pharmacists (alias)
bstnA6k(gbl-ns-vol[medarcv~/rcrds])# ...
Ignoring SID Errors from the Filer (CIFS)
If the share does not perform SID translation, or if SID translation fails, the share
copies the binary version of the SID to the destination filer. It is possible that the SID
is unknown at the destination filer. Typically, the back-end filer returns an error and
rejects the file, or silently accepts the unknown SID: an error indicates that the file
was rejected. The share therefore aborts the migration if it receives any of the
following errors in response to the CIFS ‘set security descriptor’ command:
STATUS_INVALID_SID, STATUS_INVALID_OWNER, or
STATUS_INVALID_PRIMARY_GROUP.