Installation manual

Policy for Balancing Capacity
Adding a Share Farm
12-24 CLI Storage-Management Guide
bstnA6k(gbl)# namespace ns2
bstnA6k(gbl-ns[ns2])# volume /usr
bstnA6k(gbl-ns-vol[ns2~/usr])# share-farm fm4
bstnA6k(gbl-ns-vol-sfarm[ns2~/usr~fm4])# constrain-directories
bstnA6k(gbl-ns-vol-sfarm[ns2~/usr~fm4])# ...
Constraining Directories Below a Certain Depth
You can apply the directory constraint to any level in the volume’s directory tree. For
example, consider a volume called /var that gets three new child directories, /usr, /log,
and /bin: if you constrain all directories below the first level of this tree, the share
farm can distribute those directories to any share with available space (as guided by
the
balance rule). The constraint applies to directories below that first level: any
directory created inside /usr, /log, or /var is constrained to the same share as its parent
directory.
To constrain directories below a certain depth, add the optional
below-depth argument
to the
constrain-directories command:
constrain-directories below depth
where depth (0-100) is the highest level in the volume’s directory tree where
balance is still enforced. The directory trees below that level are constrained to
the same share as their parent directories. This defaults to 0, which constrains all
directories in the volume.
For example, the following command sequence causes all new directories in the
ns2~/usr~fm4 share farm to be constrained to their parent directories when the new
directory is below the first subdirectory level.
bstnA6k(gbl)# namespace ns2
bstnA6k(gbl-ns[ns2])# volume /usr
bstnA6k(gbl-ns-vol[ns2~/usr])# share-farm fm4
bstnA6k(gbl-ns-vol-sfarm[ns2~/usr~fm4])# constrain-directories below 1
bstnA6k(gbl-ns-vol-sfarm[ns2~/usr~fm4])# ...
Given a depth of ‘below 1’, if the ns2~/usr~fm4 share farm has shares s1, s2, and s3
with the same free space and capacity, and you have created root directories /a, /b, and
/c, these directories are spread evenly across shares s1, s2, and s3 one share at a time.
Any directory created in /a, /b, or /c is placed on the same share as its parent directory.