Volumes may either be mirrored or unmirrored. A plex is a physical copy of a WAFL filesystem. A mirrored volume consists of two plexes; unmirrored volumes contain a single plex. In order to create a mirrored volume, you must have a filer configuration that supports mirroring. When mirroring is enabled on the filer, the spare disks are divided into two pools. When a volume is created, all of the disks in a single plex must come from the same pool, and the two plexes of a mirrored volume must consist of disks from separate pools, as this maximizes fault isolation. This policy can be overridden with the -f option to vol create, vol add, and vol mirror, but it is not recommended.
A 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 200 volumes on each filer.
A plex may be online or offline. If it is offline, it is not available for read or write access. Plexes can be in combinations of the following states:
normal All RAID groups in the plex are functional.
failed One or more of the RAID groups in the plex has failed.
empty The plex is part of a volume that is being created, and one or more of the disks targeted to the volume need to be zeroed before being added to the plex.
active The plex is available for use.
inactive
The plex is not available for use.
resyncing
The plex's contents are currently out of date and
are in the process of being resynchronized with the
contents of the other plex of the volume (applies
to mirrored volumes only).
adding disks
Disks are being added to the RAID group(s) of the
plex.
out-of-date
This state only occurs in mirrored volumes where
one of the plexes has failed. The non-failed plex
will be in this state if it needed to be resynchronized
at the time the other plex failed.
A plex is named using the name of the volume, a slash character delimiter, and the name of the plex. The system automatically selects plex names at creation time. For example, the first plex created in volume /vol0 would be /vol0/plex0.
A volume may be online, restricted, or offline. When a volume is offline, no read or write access is allowed. When a volume is restricted, certain operations are allowed (such as vol copy, parity reconstruction) but data access is not allowed. Volumes can be in combinations of the following states:
raid4 The volume consists of RAID-4 RAID groups.
raid_dp
The volume consists of RAID-DP (Double Parity) RAID
groups.
raid0 The volume consists of RAID-0 (no parity) RAID groups (gFiler and NetCache only).
mirrored
The volume is mirrored and all of its RAID groups
are functional.
degraded
The volume contains at least one degraded RAID
group that is not being reconstructed.
mirror degraded
The volume is a mirrored volume, and one of its
plexes is offline or resyncing.
foreign
The disks that the volume contains were moved to
the current filer from another filer.
reconstruct
At least one RAID group in the volume is being
reconstructed.
partial
At least one disk was found for the volume, but two
or more disks are missing.
growing
Disks are in the process of being added to the volume.
initializing
The volume is in the process of being initialized.
needs check
A WAFL consistency check needs to be performed on
the volume.
resyncing
One of the plexes of a mirrored volume is being
resynchronized.
ironing
A WAFL consistency check is being performed on this
volume.
copying
The volume is currently the target of active vol
copy or snapmirror operations.
snapmirrored
The volume is a snapmirrored replica of another
volume.
verifying
A mirror verification operation is currently being
run on the volume.
wafl inconsistent
The volume has been marked corrupted. Please contact
customer support if you see a volume in this
state.
invalid
The volume does not contain a valid file system.
Typically this happens only after an aborted vol
copy operation.
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 200 volumes on each filer.
The -t raidtype argument specifies the RAID type used when creating raidgroups for this volume. The valid types are `raid4' (one parity disk per raidgroup) and `raid_dp' (two parity disks per raidgroup).
The -r raidsize argument specifies the maximum number of disks in each RAID group in the volume. The maximum and default values of raidsize are plat_form-dependent, based on performance and reliabil_ity considerations.
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 that are within 10% of the specified size will be selected for use in the volume.
The -m option can be used to specify that the new volume be mirrored (have two plexes) upon creation. If this option is given, then the indicated disks will be split across the two plexes. By default, the new volume will not be mirrored.
The -L option can be used to specify that the new volume be a SnapLock volume upon creation. If this option is given, then the newly created volume will be a SnapLock volume. SnapLock volumes behave differently from regular volumes and are not usable as regular volumes. SnapLock volumes should only ever be created for use by applications that are specifically designed to operate correctly with these types of volumes.
The -n option can be used to display the command that the system will execute, without actually making any changes. This is useful for displaying the automatically selected disks, for example.
If you use the -d disk1 [ disk2 ... ] argument, the filer creates the volume with the specified spare disks disk1, disk2, and so on. You can specify a space-separated list of disk names. Two separate lists must be specified if the new volume is mirrored. In the case that the new volume is mirrored, the indicated disks must result in an equal number of disks on each new plex.
The disks in a plex are not permitted to span spare pools. This behavior can be overridden with the -f option.
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))
ko (Korean)
no (Norwegian)
nl (Dutch)
pt (Portuguese)
sv (Swedish)
zh (Simplified Chinese)
zh.GBK (Simplified Chinese (GBK))
zh_TW (Traditional Chinese euc-tw)
zh_TW.BIG5 (Traditional Chinese Big 5)
To use UTF-8 as the NFS character set append '.UTF-8'
vol add volname
[ -f ]
[ -n ]
[ -g raidgroup ]
{ ndisks[@size]
| -d disk1 [ disk2 ... ]
[ -d disk1 [ disk2 ... ] ] }
Adds disks to the volume with the name volname. Specify the disks in the same way as for the vol create command. If the volume is mirrored, then the -d argument must be used twice (if at all).
The -g option allows specification of a RAID group (for example rg0) to which the indicated disks should be added.
When -g is used to add disks to a RAID group other than the last RAID group, the volume can no longer be reverted to a version of Data ONTAP prior to 6.2. In such a case, the -f flag must be specified as well.
The -n option can be used to display the command that the system will execute, without actually making any changes. This is useful for displaying the automatically selected disks, for example.
By default, 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.
You cannot add disks to a mirrored volume if one of the plexes is offline.
The disks in a plex are not permitted to span disk pools. This behavior can be overridden with the -f option.
vol mirror volname
[ -n ]
[ -v victim_volname ]
[ -f ]
[ -d disk1 [ disk2 ... ] ]
Turns an unmirrored volume into a mirrored volume by adding a plex to it. The plex is either newlyformed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored volume. volname must be currently unmirrored. Use vol create to make a new, mirrored volume from scratch.
Disks may be specified explicitly using -d in the same way as with the vol create and vol add commands. The number of disks indicated must match the number present on the existing volume. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option.
If disks are not specified explicitly, then disks are automatically selected to match those in the volume's existing plex.
The -v option can be used to join victim_volname back into volname to form a mirrored volume. The result is a mirrored volume named volname which is otherwise identical to volname before the operation. Victim_volname is effectively destroyed. Victim_volname must have been previously mirrored with volname, then separated via the vol split command. Victim_volname must be offline. Combined with the -v option, the -f option can be used to join volname and victim_volname without prompting.
The -n option can be used to display the command that the system will execute, without actually making any changes. This is useful for displaying the automatically selected disks, for example.
vol destroy { volname | plexname } [ -f ]
Destroys the volume with the name volname or the plex with name plexname. If a volume is specified, all plexes in the volume are destroyed. If a plex is specified, the plex is destroyed, leaving an unmirrored volume containing the remaining plex. Before destroying the volume or plex, the user is prompted to confirm the operation. The -f flag can be used to destroy a volume or plex without prompting.
The disks originally in the destroyed object become spare disks. Only offline volumes and plexes can be destroyed.
vol lang [ volname [ language_code ] ]
Displays or changes the character mapping on vol_name.
If no arguments are given, it displays the list of supported languages and their language codes.
If only volname is given, it displays the language of the specified volume.
If volname and language-code are given, it sets the language of the specified volume to the specified language.
vol rename volname newname
Renames the volume named volname to the name new_name. 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 | plexname } [ -f ]
Brings the volume named volname (or the plex named plexname) online. This command takes effect immediately. If there are CIFS shares associated with the volume, they are enabled.
If a volname is specified, it must be currently offline, restricted, 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.''
If the volume is inconsistent, but has not lost data, the user will be cautioned and prompted before bringing the volume online. The -f flag can be used to override this behavior. It is advisable to run WAFL_check (or do a snapmirror initialize in case of a replica volume) prior to bringing an inconsistent volume online. Bringing an inconsistent volume online increases the risk of further file system corruption. If the volume is inconsistent and has experienced possible loss of data, it cannot be brought online unless WAFL_check (or snapmirror initialize) has been run on the volume.
If a plexname is specified, the plex must be part of an online mirrored volume. The system will initiate resynchronization of the plex as part of online processing.
vol offline { volname | plexname } [ -t cifsdelaytime ]
Takes the volume named volname (or the plex named plexname) offline. The command takes effect before returning. If the volume is already in restricted state then it is already unavailable for data access, and much of the following description does not apply.
Except in maintenance mode, the current root volume may not be taken offline. Neither may a volume marked to become root (by using vol options volname root) be taken offline.
If a volume contains CIFS shares, users should be warned before taking the volume offline. Use the -t option for this. The cifsdelaytime argument specifies the number of seconds to delay before taking the volume offline, during which time CIFS users are warned of the pending loss of service. A time of 0 means take the volume offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
If a plexname is specified, the plex must be part of a mirrored volume and both plexes must be online. Prior to offlining a plex, the system will flush all internally buffered data associated with the plex and create a snapshot that is written out to both plexes. The snapshot allows for efficient resynchronization when the plex is subsequently brought back online.
A number of operations being performed on the volume in question can prevent vol offline from succeeding, for various lengths of time. If such operations are found, there will be a one-second wait for such operations to finish. If they do not, the command is aborted.
A check is also made for files on the volume opened by internal ONTAP processes. The command is aborted if any are found.
vol restrict volname [ -t cifsdelaytime ]
Put the volume volname in restricted state, starting from either online or offline state. If the volume is online then it will be made unavailable for data access as described below under vol offline.
If a volume contains CIFS shares, users should be warned before taking the volume offline. Use the -t option for this. The cifsdelaytime argument specifies the number of seconds to delay before taking the volume offline, during which time CIFS users are warned of the pending loss of service. A time of 0 means take the volume offline immediately with no warnings given. CIFS users can lose data if they are not given a chance to terminate applications gracefully.
vol split plexname volname
Removes plexname from a mirrored volume and creates a new unmirrored volume named volname that contains the plex. The original mirrored volume becomes unmirrored. The plex to be split from the original volume must be functional (not partial), but it could be inactive, resyncing, or out-of-date. Vol split can therefore be used to gain access to a plex that is not up to date with respect to its partner plex, if its partner plex is currently failed.
If the plex is offline at the time of the split, the resulting volume will be offline. Otherwise, the resulting volume will be in the same online/offline/restricted state as the original volume.
A split mirror can be joined back together via the -v option to vol mirror.
vol options volname [ optname optval ]
Displays the options that have been set for volume volname, or 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 vol status command displays the options that are set per volume. 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.
Until the system is rebooted, the original volume will continue to show root as one of its options, and the new root volume will show diskroot as an option. In general, the volume that has the diskroot option is the one that will be the root volume following the next reboot.
The only way to remove the root status of a volume is to set the root option on another volume.
The act of setting the root status on a volume will also move the HA mailbox disk information to disks on that volume. When the system is in maintenance mode, the act of setting the root status on a volume will have the additional side effect of clearing any HA mailbox error condition that may be preventing the system from booting. This side effect will occur even if the volume in question is already in root status.
Because of the above side effect, setting root status on a volume that is already in root status when the system is in maintenance mode is the normal method of recovery from HA mailbox conditions that prevent the system from booting after failures of certain disks.
raidtype raid4 | raid_dp
Sets the type of RAID used to protect against disk failures. Raid4 provides one parity disk per raidgroup, while raid_dp provides two. Changing this option immediately changes the raid type of all raidgroups within the volume. When upgrading raidgroups from raid4 to raid_dp, each raidgroup begins a reconstruction onto a spare disk allocated for the second `dparity' parity disk.
Changing this option also causes change of raidsize to a more suitable value for new raidtype. When upgrading from raid4 to raid_dp, raidsize will be increased to the default value for raid_dp. When downgrading from raid_dp to raid4, raidsize will be decreased to the size of the largest existing raidgroup if it is between the default value and the limit for raid4. If the largest raid group is above the limit for raid4, new raidsize will be that limit. If the largest raid group is below the default value for raid4, new raidsize will be that default value. If raidsize is already below the default value for raid4, it will be reduced by 1.
raidsize number
The value of this option is the maximum size of a RAID group that can be created in 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.
Allowed values for this option depend on raidtype. Raid_dp allows larger raidgroups than raid4. Limits and default values are also different for different types of filer appliances. Those values may change in future releases of Data ONTAP.
maxdirsize number
Sets the maximum size (in K-Bytes) to which a directory can grow. This is set to 1% of the total system memory by default. Most users should not need to change this setting. If this setting is changed to be above the default size, a notice message will be printed to the console explaining that this may impact performance. This option is useful for environments in which system users may grow a directory to a size that starts impacting system performance. When a user tries to create a file in a directory that is at the limit, the system returns a ENOSPC error and fails the create.
create_ucode on | off
Setting this option to on forces Unicode format directories to be created by default, both from NFS and CIFS. By default it is set to off, in which case all directories are created in pre-4.0 format and the first CIFS access will convert it to Unicode format.
convert_ucode on | off
Setting this option to on forces conversion of all directories to Unicode format when accessed from both NFS and CIFS. By default it is set to off, in which case access from CIFS causes conversion of pre-4.0 and 4.0 format directories; access from NFS causes conversion of 4.0 format directories.
fs_size_fixed on | off
This option causes the filesystem to remain the same size and not grow when a snapmirrored volume is broken, or when a vol add is performed on it. This option is automatically set to be on when a volume becomes a snapmirrored volume. It will remain on after the snapmirror break command is issued for the volume. This allows a volume to be snapmirrored back to the source without needing to add disks to the source volume. If the volume size is larger than the filesystem size, turning off this option will force the filesystem to grow to the size of the volume.
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 from 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.
ignore_inconsistent on | off
This command can only be used in maintenance mode. If this option is set, it allows the root volume to be brought online on booting, even though it is inconsistent. The user is cautioned that bringing it online prior to running WAFL_check may result in further file system inconsistency.
resyncsnaptime number
This option is used to set the mirror resynchronization snapshot frequency (in minutes). The default value is 60 minutes.
create_reserved on | off
This option, if on, makes space reservation the default for newly created files in the volume. The default value can be changed by using the file command for any given file. Reserving space for files ensures that the entire file can be written up to its current size, without running out of disk space. Without reservations, this is not necessarily the case as there may not be sufficient disk space to fill holes in the file, or to overwrite blocks of the file that are already stored in a snapshot.
snaplock
This option, if present, indicates that the volume is a SnapLock volume. The SnapLock option can only be set at volume creation time and cannot be set or unset on an existing volume.
For new volumes, options create_ucode, convert_ucode and maxdirsize get their values from the root volume. If root volume does not exist, they get the default values.
vol status [ volname ]
[ -r | -v | -d | -l | -c | -b | -s | -f ]
Displays the status of one or all volumes. If vol_name 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 oneline synopsis of the volume, which includes the volume name, whether it is online or offline, other states (for example, partial, degraded, wafl inconsistent and so on) and per-volume options. Pervolume options are displayed only if the options have been turned on using the vol options command. If the wafl inconsistent state is displayed, please contact customer support.
The -v flag shows the on/off state of all per-volume options and displays information about each plex and RAID group within the volume.
The -r flag displays a list of the RAID information for that volume. If no volname is specified, it prints RAID information about all volumes, information about file system disks, spare disks, and failed disks. For more information about failed disks, see -f option description below.
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.
The -c flag displays the upgrade status of the Block Checksums data integrity protection feature.
The -b is used to get the size of source and destination volumes for use with SnapMirror and vol copy. The output contains the size of the volume and the size of the filesystem in the volume. SnapMirror and vol copy use these numbers to determine if the source and destination volume sizes are compatible. The filesystem size of the source must be equal or smaller than the volume size of the destination. These numbers can be different if using SnapMirror between volumes of dissimilar geometry.
The -s flag displays a listing of the spare disks on the system.
The -f flag displays a list of the failed disks on the system. The command output includes the disk failure reason which can be any of following:
unknown Failure reason unknown.
failed Data ONTAP failed disk, due to a
fatal disk error.
admin failed User issued a 'disk fail' command
for this disk.
labeled broken Disk was failed under Data ONTAP
6.1.X or an earlier version.
init failed Disk initialization sequence failed.
admin removed User issued a 'disk remove' command
for this disk.
not responding Disk not responding to requests.
pulled Disk was physically pulled or no
data path exists on which to access
the disk.
bypassed Disk was bypassed by ESH.
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:vol_ume_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 | all
Terminates volume copy operations. The opera_tion_number parameter in the vol copy abort command specifies which operation to terminate. If you specify all, 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. In particular, the throttle is designed to help limit the CPU usage of the volume copy operation. It cannot be used to fine-tune network bandwidth consumption patterns.
The vol copy throttle command only enables you to set the speed of 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 [ -f ] [ -s snapshot ]
Reverts a volume to a specified snapshot. This command is being deprecated in favor of the snap restore command. Please refer to the na_snap(1) man page.
vol verify start [ volname ] [ -n ]
Start mirror verification on the named online mirrored volume. If no name is given then mirror verification is started on all online mirrored volumes. Verification compares the data in both plexes of a mirrored volume. In the default case, verify corrects any blocks that differ from the correct value. If the -n flag is given, errors are logged but no changes are made to the volume.
vol verify suspend [ volname ]
Suspend mirror verification on the named volume, or if no volume name is given, on all volumes currently undergoing mirror verification.
vol verify resume [ volname ]
Resume mirror verification on the named volume, or if no volume name is given, on all volumes currently undergoing a mirror verification that has been suspended.
vol verify stop [ volname ]
Stop mirror verification on the named volume, or if no volume name is given, on all volumes currently undergoing a mirror verification.
vol verify status [ volname ]
Print the status of mirror verification on the named volume, or on all volumes currently undergoing mirror verification if no volume name is given. The status includes a percent-complete, and the verification's suspended status.
vol media_scrub status [ volname | plexname | groupname ] [ -v ]
Print the status of media_scrub on the named volume, plex, or group; all RAID groups currently running media_scrub if no name is given. The status includes a percent-complete, and the media_scrub's suspended status.
The -v flag displays the date and time at which the last full media_scrub completed, the date and time at which the current instance of media_scrub started and the current status on the named volume, plex, or group; all RAID groups if no name is given.
vol scrub start [ volname | plexname | groupname ]
Start parity scrubbing on the named online volume. Parity scrubbing compares the data disks to the parity disk in a RAID group, correcting the parity disk's contents as necessary. If no name is given then parity scrubbing is started on all online volumes. If a volume name is given, scrubbing is started on all RAID groups contained in the volume. If a plex name is given, scrubbing is started on all RAID groups contained in the plex.
vol scrub suspend [ volname | plexname | groupname ]
Suspend parity scrubbing on the named volume, plex, or group; if no name is given, on all RAID groups currently undergoing parity scrubbing.
vol scrub resume [ volname | plexname | groupname ]
Resume parity scrubbing on the named volume, plex, or group; if no name is given, on all RAID groups currently undergoing a parity scrubbing that has been suspended.
vol scrub stop [ volname | plexname | groupname ]
Stop parity scrubbing on the named volume, plex, or group; if no name is given, on all RAID groups currently undergoing a parity scrubbing.
vol scrub status [ volname | plexname | groupname ] [ -v ]
Print the status of parity scrubbing on the named volume, plex, or group; all RAID groups currently undergoing parity scrubbing if no name is given. The status includes a percent-complete, and the scrub's suspended status.
The -v flag displays the date and time at which the last full scrub completed along with the current status on the named volume, plex, or group; all RAID groups if no name is given.
However, having unique volume names in a cluster makes it easier for you to migrate volumes between the filers in the cluster.
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 (8 disks) is used. The newly created volume contains two RAID groups with 8 disks and a third group with four 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 vol1 -r
Displays the RAID information about the volume named vol1:
Volume vol0 (online, raid4) (zoned checksums)
Plex /vol0/plex0 (online, normal, active)
RAID group /vol0/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks)
--------- ------ --------------- ---- -------------- --------------
parity 3a.0 3a 0 0 FC:A 34500/70656000 35239/72170880
data 3a.1 3a 0 1 FC:A 34500/70656000 35239/72170880
Copies the nightly snapshot named nightly.1 on the vol0 volume on the local filer to the vol0 volume on a remote filer named toaster1.
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 5
Changes volume copy operation 1 to half (50%) of its full speed.