Adding a Direct Volume
Setting CIFS Options
8-4 CLI Storage-Management Guide
You can set this any time, even after the volume is enabled.
For example, this command sequence makes the ‘access~/G’ volume count the free
space in all back-end shares, even multiple shares that draw from the same back-end
storage:
prtlndA1k(gbl)# namespace access
prtlndA1k(gbl-ns[access])# volume /G
prtlndA1k(gbl-ns-vol[access~/G])# freespace calculation manual
prtlndA1k(gbl-ns-vol[access~/G])# ...
Using Automatic Free-Space Calculation
By default, free space is calculated based on the IDs of the volumes behind the
back-end shares. If any of these shares report the same volume ID, their free space is
counted only once. To return to this default, use
no freespace calculation manual:
no freespace calculation manual
For example:
bstnA6k(gbl)# namespace medco
bstnA6k(gbl-ns[medco])# volume /vol
bstnA6k(gbl-ns-vol[medco~/vol])# no freespace calculation manual
bstnA6k(gbl-ns-vol[medco~/vol])# ...
Setting CIFS Options
The next step in configuring a volume is addressing its CIFS options, if necessary:
This section does not apply to volumes in NFS-only namespaces; skip to the next
section if this namespace does not support CIFS.
There are five CIFS-volume attributes that back-end filers may or may not support.
They are named streams, compressed files, persistent ACLs, Unicode file names on
disk, and sparse files. Each volume can support any and all of these capabilities.
However, all filer shares used in a volume must support the capabilities advertised in
the volume. For example: if your volume is going to support compressed files, then
all of its back-end filer shares must also support compressed files.
Kommentare zu diesen Handbüchern