Veritas File System 5.0 AdministratorÆs Guide, HP-UX 11i v3, First Edition, May 2008

Forcibly removing a volume
If you must forcibly remove a volume from a file system, such as if a volume is
permanently destroyed and you want to clean up the dangling pointers to the lost
volume, use the fsck -o zapvol=volname command. The zapvol option performs
a full file system check and zaps all inodes that refer to the specified volume. The
fsck command prints the inode numbers of all files that the command destroys;
the file names are not printed. The zapvol option only affects regular files if used
on a dataonly volume. However, it could destroy structural files if used on a
metadataok volume, which can make the file system unrecoverable. Therefore,
the zapvol option should be used with caution on metadataok volumes.
Moving volume 0
You can remove volume 0 from a volume in a multi-volume file system and move
volume 0 to another volume with the vxassist move command. The vxassist
command creates any necessary temporary mirrors and cleans up the mirrors at
the end of the operation.
To move volume 0
Move volume 0:
# vxassist move vol1 !mydg
About allocation policies
To make full use of multi-volume support features, VxFS provides support for
allocation policies that allow files or groups of files to be assigned to specified
volumes within the volume set.
A policy specifies a list of volumes and the order in which to attempt allocations.
A policy can be assigned to a file, a file system, or a Storage Checkpoint created
from a file system. When policies are assigned to objects in the file system, you
must specify how the policy maps to both metadata and file data. For example, if
a policy is assigned to a single file, the file system must know where to place both
the file data and metadata. If no policies are specified, the file system places data
randomly.
Assigning allocation policies
The following example shows how to assign allocation policies. The example
volume set contains two volumes from different classes of storage.
121Multi-volume file systems
About allocation policies