Dell PowerVault MD 32XX/36XX Series Storage Arrays CLI Guide

PDF

Create RAID Virtual Disk On A Disk Pool

Description

This command creates a new RAID virtual disk on an existing disk pool.

Syntax

create virtualDisk diskPool="diskPoolName" userLabel="virtual diskName" capacity=virtualDiskCapacity [thinProvisioned=(TRUE
                                 | FALSE)] [owner=(0|1)] [mapping=(none|default)] [dataAssurance=(none|enabled)] [(existingRepositoryLabel=existingRepositoryName
                                 | [newRepositoryCapacity=newRepositoryCapacityValue (KB | MB | GB | TB | Bytes))] [repositoryMaxCapacity=repositoryMaxCapacityValue
                                 (KB|MB|GB|TB|Bytes)] [warningThresholdPercent=warningThresholdPercentValue] 
                                 [repositoryExpansionPolicy=(automatic|manual)] [cacheReadPrefetch=(TRUE | FALSE)]

Parameters

Parameter	Description
`capacity`	The size of the virtual disk that you are creating. Size is defined in units of `MB`, `GB`, or `TB`. The following are examples of the syntax: `capacity=500MB` `capacity=2GB`
`thinProvisioned`	This parameter enables thin provisioning for the new virtual disk. To use thin provisioning, set this parameter to `TRUE`. For no thin provisioning, set this parameter to `FALSE`.
`owner`	The RAID controller module that owns the virtual disk. Valid RAID controller module identifiers are `0` or `1`, where `0` is the RAID controller module in slot 0, and `1` is the RAID controller module in slot 1. If you do not specify an owner, the RAID controller module firmware determines the owner.
`mapping`	This parameter enables you to map the virtual disk to a host. If you want to map later, set this parameter to `none`. If you want to map the virtual disk now, set this parameter to `default`, and the virtual disk is mapped to all hosts that have access to the storage pool. The default option is `none`.
`warningThreshold`	Valid values are from `1` to `100`. The default value is determined by the RAID controller module firmware. Setting this parameter to `100` disables warning alerts.
`repositoryExpansionPolicy`	Valid values are `automatic` and `manual`.
`cacheReadPrefetch`	The setting to turn on or turn off cache read prefetch. To turn off cache read prefetch, set this parameter to `FALSE`. To turn on cache read prefetch, set this parameter to `TRUE`.
securityType	The setting to specify the security level when creating the disk groups and all associated virtual disks. `none`—The disk group and virtual disks are not secure. `capable`—The disk group and virtual disks are capable of having security set, but security has not been enabled. `enabled`—The disk group and virtual disks have security enabled. NOTE: This option is only valid for enablement, if the drives support DA. Use the `securityType` parameter to specify the security settings for the disk group and associated virtual disks. Before you can set the `securityType` parameter to `capable` or `enabled`, you must create a storage array security key. Use the create `storageArray` `securityKey` command to create a storage array security key. These commands are related to the security key: `create storageArray securityKey` `enable virtualDiskGroup [diskGroupName] security` `export storageArray securityKey` `import storageArray securityKey` `set storageArray securityKey` `start secureErase (drive \| drives)` `set PhysicalDisk securityID`
securePhysicalDisks	Secure-capable drives can be either Self-Encrypting Disk (SED) drives or Federal Information Processing Standard (FIPS) drives. Use the `securePhysicalDisks` parameter to specify the type of secure physical disks to use. The values you can use are `fips` and `sed`. NOTE: The controller firmware does not support a mix of SED and FIPS drives within disk groups or disk pools. Example command `create virtualDisk physicalDiskCount=2` `diskGroupUserLabel=”FIPS_VG” raidLevel=1 userLabel=”FIPS_V”` `physicalDiskMediaType=HDD securityType=capable` `securePhysicalDisks=fips;`
`segmentSize`	Amount of data (in kilobytes) that the RAID controller module writes on a single physical disk in a virtual disk before writing data on the next physical disk. Valid values are `8`, `16`, `32`, `64`, `128`, `256`, or `512`. For information about the `segmentSize` parameter, see Using the Auto Configure Command.
`usageHint`	Valid values are `multiMedia`, `database` or `fileSystem`.