vol create volname [ -r raidsize ]
ndisks[@size] | [ -l language_code ] -d diskname... creates a new
volume with the name volname. The volume name can contain letters,
numbers, and the underscore character(_), but the first character must
be a letter or underscore. You can create up to 23 volumes on each
filer.
The -r raidsize argument specifies the maximum number of disks in each RAID group in the volume. The maximum value of raidsize is 28. The default value is 14. ndisks is the number of disks in the volume, including the parity disks. The disks in this newly created volume come from the pool of spare disks. The smallest disks in this pool join the volume first, unless you specify the @size argument. size is the disk size in GB, and disks within 1 GB of the specified size are used in this volume.
If you use the -d diskname argument, the filer creates the volume with the specified spare disks. You can specify a space-separated list of disk names.
If you use the -l language_code argument, the filer creates the volume with the language specified by the language code. The default is the language of the root volume of the filer. Language codes are:
C (POSIX)
da (Danish)
de (German)
en (English)
en_US (English (US))
es (Spanish)
fi (Finnish )
fr (French)
he (Hebrew)
it (Italian)
ja (Japanese euc-j)
ja_JP.PCK (Japanese PCK(sjis))
no (Norwegian)
nl (Dutch)
pt (Portuguese)
sv (Swedish )
To use UTF-8 as the NFS character set append '.UTF-8'
vol add volname ndisks[@size] | -d diskname... adds disks to the volume with the name volname. Specify the disks in the same way as for the vol create command.
When adding disks to a volume, the filer fills up one RAID group with disks before starting another RAID group. Suppose a volume currently has one RAID group of 12 disks and its RAID group size is 14. If you add 5 disks to this volume, it will have one RAID group with 14 disks and another RAID group with 3 disks. The filer does not evenly distribute disks among RAID groups.
vol destroy volname
destroys the volume with the name volname. The disks originally in
the volume become spare disks. Only offline volumes can be destroyed.
vol lang [ volname [ language_code ]
displays or changes character mapping on volname.
vol lang
by itself displays a list of supported languages.
vol lang volname
displays the language of the specified volume.
vol lang volname language_code
sets the language of volume volname to the language specified by
language_code.
vol rename volname newname
renames the volume named volname to the name newname. If the volume
named volname is referenced in the /etc/exports file, remember to make
the name change in /etc/exports also so that the affected file system
can be exported by the filer after the filer reboots. The vol rename
command does not automatically update the /etc/exports file.
vol online volname
brings the volume named volname online. This command takes effect
immediately. The volume specified in this command must be currently
offline or foreign. If the volume is foreign, it will be made native
before being brought online. A ``foreign'' volume is a volume that
consists of disks moved from another filer and that has never been
brought online on the current filer. Volumes that are not foreign are
considered ``native.'' You can also use this command to cancel a vol
offline command.
vol offline volname
takes the volume named volname offline. This command takes effect when
the filer is rebooted. If you change your mind after entering this
command, you can enter vol online volname before the reboot.
vol options volname optname optval
sets the option named optname of the volume named volname to the value
optval. The command remains effective after the filer is rebooted, so
there is no need to add vol options commands to the /etc/rc file.
Some options have values that are numbers. Some options have values
that may be on (which can also be expressed as yes, true, or 1) or off
(which can also be expressed as no, false, or 0). You can use a mixture
of uppercase and lowercase characters when typing the value of an
option. The root option is special in that it does not have a value.
To set the root option, use this syntax:
vol options volname root
The following describes the options and their possible values:
root
The volume named volname will become the root volume for the filer
on the next reboot. This option can be used on one volume only at
any given time. The existing root volume will become a non-root
volume after the reboot. The only way to remove the root status of
a volume is to set the root option on another volume.
raidsize number
The value of this option is the maximum size of a RAID group within
the volume. Changing the value of this option will not cause existing
RAID groups to grow or shrink; it will only affect whether more
disks will be added to the last existing RAID group and how large
new RAID groups will be.
minra on | off
If this option is on, the filer performs minimal read-ahead on the
volume. By default, this option is off, causing the filer to perform
very aggressive read-ahead on the volume.
no_atime_update on | off
If this option is on, it prevents the update of the access time on
an inode when a file is read. This option is useful for volumes
with extremely high read traffic, since it prevents writes to the
inode file for the volume rom contending with reads from other
files. It should be used carefully. That is, use this option when
you know in advance that the correct access time for inodes will not
be needed for files on that volume.
nosnap on | off
If this option is on, it disables automatic snapshots on the volume.
nosnapdir on | off
If this option is on, it disables the visible .snapshot directory
that is normally present at client mount points, and turns off
access to all other .snapshot directories in the volume.
nvfail on | off
If this option is on, the filer performs additional status checking
at boot time to verify that the NVRAM is in a valid state. This
option is useful when storing database files. If the filer finds any
problems, database instances hang or shut down, and the filer sends
error messages to the console to alert you to check the state of the
database.
snapmirrored off
If SnapMirror is enabled, the filer automatically sets this option
to on. Set this option to off if you no longer want to use SnapMirror
to update the mirror. After you set this option to off, the
mirror becomes a regular writable volume. You can set this option
only to off; only the filer can change the value of this option from
off to on.
vol status [ -r | -v | -d | -l ] [ volname ] displays the status of one or all volumes. If volname is used, the status of the specified volume is printed; otherwise the status of all volumes in the filer are printed. By default, it prints a one-line synopsis of the volume, which includes the volume name, whether it is online or offline, other states (for example, partial, degraded, and so on) and per-volume options.
The -v flag displays information about each RAID group within the volume.
The -r flag displays a listing of the RAID information for that volume.
The -d flag displays information about the disks in the specified volume. The types of disk information are the same as those from the sysconfig -d command. The -l flag displays, for each volume on a filer, the name of the volume, the language code, and language being used by the volume.
vol copy start [ -S | -s snapshot ] source destination copies all data, including the snapshots, from one volume to another. If you use the -S flag, the command copies all snapshots in the source volume to the destination volume. To specify a particular snapshot to copy, use the -s flag followed by the name of the snapshot. If you use neither the -S nor -s flag in the command, the filer creates a snapshot at the time when the vol copy start command is executed and copies only that snapshot to the destination volume.
The source volume and destination volume can be on the same filer or different filers. If the source or destination volume is on a filer other than the one on which you enter the vol copy start command, specify the volume name in the filer_name:volume_name format.
The filers involved in a volume copy must meet the following requirements for the vol copy start command to be completed successfully:
The source volume must be on-line and the destination volume must be off-line.
If data is copied between two filers, each filer must be defined as a trusted host of the other filer. That is, the filer's name must be in the /etc/hosts.equiv file of the other filer.
If data is copied on the same filer, localhost must be included in the filer's /etc/hosts.equiv file. Also, the loopback address must be in the filer's /etc/hosts file. Otherwise, the filer cannot send packets to itself through the loopback address when trying to copy data.
The usable disk space of the destination volume must be greater than or equal to the usable disk space of the source volume. Use the df pathname command to see the amount of usable disk space of a particular volume.
Each vol copy start command generates two volume copy operations: one for reading data from the source volume and one for writing data to the destination volume. Each filer supports up to four simultaneous volume copy operations.
vol copy abort [ operation_number ]
terminates a volume copy operation. The operation_number parameter in
the vol copy abort command specifies which operation to terminate. If
you don't specify an operation number, all volume copy operations are
terminated.
vol copy status [ operation_number ]
displays the progress of one or all volume copy operations. The
operations are numbered from 0 through 3.
vol copy throttle [ operation_number ] value controls the performance of the volume copy operation. The value ranges from 10 (full speed) to 1 (one-tenth of full speed). You can apply the performance value to an operation specified by the operation_number parameter. If you do not specify an operation number in the vol copy throttle command, the command applies to all volume copy operations. Use this command to limit the speed of the volume copy operation if you suspect that the volume copy operation is causing performance problems on your filer.
The vol copy throttle command enables you to set the volume copy speed for a volume copy operation that is in progress. To set the default volume copy speed to be used by future volume copy operations, use the options command to set the vol.copy.throttle option.
vol snaprestore volname [-s snapshot] [volname [-s snapshot]...] reverts a volume to a specified snapshot. If you do not specify a snapshot, the filer prompts you for the snapshot. You can use one command to revert multiple volumes. The volume to be reverted must be on-line and must not be a mirror.
After the reversion, the volume is in the same state as it was when the snapshot was taken.
vol snapmirror on | off
enables and disables SnapMirror. If SnapMirror is enabled, you can
replicate one volume to another according to the specifications in the
/etc/snapmirror.conf file.
vol snapmirror status
displays whether SnapMirror is enabled. If so, the command displays
whether the filer is copying data between the source volume and the
mirror, and the percentage of data that has been copied.
However, having unique volume names in a cluster makes it easier for you to migrate volumes between the filers in the cluster.
vol create vol1 -r 10 20
creates a volume named vol1 with 20 disks. The RAID groups in this
volume can contain up to 10 disks, so this volume has two RAID groups.
The filer adds the current spare disks to the new volume, starting
with the smallest disk.
vol create vol1 20@9
creates a volume named vol1 with 20 9-GB disks. Because no RAID group
size is specified, the default size (14 disks) is used. The newly
created volume contains one RAID group with 14 disks and another group
with six disks.
vol create vol1 -d 8a.1 8a.2 8a.3
creates a volume named vol1 with the specified disks.
vol create vol1 10
vol options vol1 raidsize 5
The first command creates a volume named vol1 with 10 disks, which
belong to one RAID group. The second command specifies that if any
disks are subsequently added to this volume, they will not cause any
current RAID group to have more than five disks. Each existing RAID
group will continue to have 10 disks and no more disks will be added
to that RAID group. When new RAID groups are created, they will have
a maximum size of five disks.
vol options vol1 root
The volume named vol1 becomes the root volume after the next filer
reboot.
vol options vol1 nosnapdir on
In the volume named vol1, the snapshot directory is invisible at the
client mount point or at the root of a share. Also, for UNIX clients,
the .snapshot directories that are normally accessible in all the
directories become inaccessible.
vol status -r vol1
displays the RAID information about the volume named vol1:
RAID group 0 RAID Disk HA.DISK_ID Used (MB/blks) Phys (MB/blks) --------- -------- -------------- -------------- parity 0.3 4000/8192000 4095/8386728 data 0.2 4000/8192000 4095/8386728
vol copy status
displays the status of all the volume copy operations.
vol copy abort 1
terminates volume copy operation 1.
vol copy throttle 1 10
changes volume copy operation 1 to one-tenth of its full speed.
_FI_FI_