Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 110 / 324

Metadata Utilities: nsck and sync
Adding and Synchronizing Filer Subshares (CIFS)
5-30 CLI Maintenance Guide
Adding and Synchronizing Filer Subshares (CIFS)
This section only pertains to volumes that support CIFS. Skip to the next section for
NFS-only volumes.
A filer subshare is a shared directory that is under another shared directory. A CIFS
service and its managed volume can pass clients from a front-end subshare through to
the corresponding subshare on a back-end filer. When clients access subshares this
way, the filer can enforce the subshare’s share-level ACL. For example, clients that
connect to the “Y2005” share (below) use ACL3; by default, when subshares are not
supported, the volume connects to the filer’s top-level share (through ACL1 in this
illustration) and descends to the directory from there.
Two sections of the CLI Storage-Management Guide have instructions for providing
this CIFS-subshare support: “Supporting Subshares and their ACLs” on page 9-20
explains how to set up managed volumes, and “Exporting a Filer Subshare (and Using
its ACL)” on page 11-15 describes the commands to set up a CIFS service. These
instructions explain how to work with subshares that exist on the filers before the
managed volume imports them.
The supported method for adding new subshares is to directly access a back-end filer,
add the subshare there, then synchronize the metadata with the new subshare.
Filer fs4
d:\exports
volume /rcrds
prescriptions
ACL1
Y2005
ACL3
Y2005
This is contrary to the standard best practice. Share definitions and ACLs are not
managed by the volume, so this does not cause any metadata corruption. You can also
create the underlying directory for the new subshare.