Installation manual

Adding a Direct Volume
Manually Setting the Volume’s Free Space (optional)
CLI Storage-Management Guide 8-3
Reverting to a Managed Volume
If a direct volume has no attach points configured, you can use no direct to revert the
volume back to a managed volume:
no direct
For example, this command sequence ensures that “wwmed~/acct” is a managed
volume:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# no direct
bstnA6k(gbl-ns-vol[wwmed~/acct])# ...
Manually Setting the Volume’s Free Space
(optional)
The next step in creating a volume is to choose an algorithm for calculating its free
space. This is the free-space calculation that is passed onto the client: whenever a user
mounts a volume (NFS) or maps a network drive to it (CIFS), this total is the free
space that they see.
By default, the namespace volume’s free space is the sum of the free space on all of its
back-end shares except shares from the same storage volume. If two or more shares
report the same ID for their backing volume, only the first share is counted. (For NFS
shares, the volume uses the file system ID (FSID); for CIFS shares, it uses the Volume
Serial Number). If this default is acceptable, you can skip this section.
You may wish to manually control the free space calculation on a share-by-share
basis. This means counting all free space on all shares, regardless of duplicate
back-end-volume IDs, then ignoring certain shares manually or adjusting their
freespace reporting. You can use the
freespace ignore and freespace adjust
commands, described later, to ignore the freespace from a share or change the
reported value for the freespace.
From gbl-ns-vol mode, use the
freespace calculation manual command to override the
default free-space calculation:
freespace calculation manual