Adding a Managed Volume
Adding a Share
CLI Storage-Management Guide 9-43
The following changes were made to replicate nested shares and their
attributes to the new share:
Added share “CELEBS$” to the following filer:
Filer Name: fs1
IP Address: 192.168.25.20
Path: d:\exports\histories\VIP_wing
Added share “Y2004” to the following filer:
Filer Name: fs1
IP Address: 192.168.25.20
Path: d:\exports\histories\2004
Added share “Y2005” to the following filer:
Filer Name: fs1
IP Address: 192.168.25.20
Path: d:\exports\histories\2005
**** Total processed: 3
**** Elapsed time: 00:00:03
**** Share Enable Filer-Subshare Inconsistency Report: DONE at Wed Dec 20 14:46:53 2006
****
bstnA6k(gbl-ns-vol-shr[medarcv~/rcrds~charts])# ...
This sample report shows that the volume successfully replicated three subshares.
Later, all three subshares can be exported from a front-end CIFS service.
For a volume that supports filer subshares but does not replicate them, the report
would have shown which subshares and ACLs were discovered on the filer. All
subshares must match in terms of their directory paths (relative to the share root),
share names, and ACLs. If a subshare definition is inconsistent at the share, this report
describes the inconsistency. The inconsistent subshare is unusable by the managed
volume. You can access the filer directly to make the subshare/ACL consistent. Then
you can use the priv-exec
sync shares command to add the subshare(s) into the
managed volume. For details on the
sync shares command, see “Adding and
Synchronizing Filer Subshares (CIFS)” on page 5-30 of the CLI Maintenance Guide.
Comentarios a estos manuales