volume offline


Take an existing volume offline

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.


The volume offline command takes the volume offline. If the volume is already in restricted or iron_restricted state, then it is already unavailable for data access, and much of the following description does not apply. The current root volume might not be taken offline. Several operations being performed on the volume in question can prevent the volume offline command from succeeding for various lengths of time. If such operations are required, the command might take additional time to complete. If you set the volume junction path, it is unmounted when the volume is taken offline. The junction path is not restored when the volume is brought online again. When the volume offline command fails, the command is aborted. The -force flag can be used to forcibly offline a volume.


-vserver <vserver name> - Vserver Name

This specifies the name of the Vserver from which the volume is to be taken offline. If only one data Vserver exists, you do not need to specify this parameter.

-volume <volume name> - Volume Name

This specifies the name of the volume that is to be taken offline.

[-f, -force <true>] - Force Offline

This specifies whether the offline operation is forced. Using this option to force a volume offline can potentially disrupt access to other volumes. The default setting is false .

[-foreground {true|false}] - Foreground Process

This specifies whether the operation runs in the foreground. The default setting is true (the operation runs in the foreground). When set to true, the command will not return until the operation completes. This parameter applies only to FlexGroups. For FlexVol volumes, the command always runs in the foreground.

[-disable-block-storage-check <true>] - Disable Check for Existing LUNs and NVMe Namespaces

Taking the volume offline will make all associated LUNs and NVMe over Fabrics (NVMe-oF) namespaces unavailable, which normally requires a user confirmation. If this parameter is specified, the command proceeds without a confirmation. The default setting is false


The following example takes the volume named vol1 offline:

cluster1::> volume offline vol1
Volume 'vs1:vol1' is now offline.