Dell PowerVault MD3260i CLI Guide - Page 37

Example of Creating Virtual Disks with Software-Assigned Physical Disks

Page 37 highlights

The command in this example automatically creates a new disk group and a virtual disk with the name Engineering_1. The disk group has a RAID level of 5 (RAID 5). The command uses three physical disks to construct the disk group. The virtual disk created has a capacity of 20 GB. If each physical disk has a capacity of 73 GB, the total capacity of the disk group is 219 GB. Because only 20 GB are assigned to the virtual disk, 199 GB remain available for other virtual disks that you can later add to this disk group. The segment size for each virtual disk is 64 KB. Hot spares have not been created for this new disk group. You must create hot spares after running this command. Creating Virtual Disks with Software-Assigned Physical Disks You can let the MD Storage Manager software assign the physical disks when you create the virtual disk. To have the software assign the physical disks, you need only specify the number of physical disks to use. The MD Storage Manager software then chooses the physical disks on which the virtual disk is created. The RAID controller module firmware assigns a disk group number to the new disk group. The following syntax is the general form for the command: create virtualDisk physicalDiskCount= numberOfPhysicalDisks raidLevel=(0 | 1 | 5 | 6) userLabel="virtualDiskName" [physicalDiskType= (SAS)] [capacity=virtualDiskCapacity | owner=(0 | 1) | segmentSize=segmentSizeValue] [enclosureLossProtect=(TRUE | FALSE)]) NOTE: The physicalDiskType, capacity, owner, segmentSize, and enclosureLossProtect parameters are optional. You can use one or all of the optional parameters as needed to help define your configuration. You do not, however, need to use any optional parameters. This command is similar to the previous create virtualDisk command, which allows the user to assign the physical disks. This version of the command requires only the number and the type of physical disks to use in the disk group. You do not need to enter a list of physical disks. All other parameters are the same. Enclosure loss protection is performed differently when MD Storage Manager assigns the physical disks as opposed to when a user assigns the physical disks. (For an explanation of the difference, see Enclosure Loss Protection.) Example of Creating Virtual Disks with Software-Assigned Physical Disks client>smcli 123.45.67.89 -c "create virtualDisk physicalDiskCount=3 raidLevel=5 userLabel= \"Engineering_1"\ capacity=20 GB owner=0 segmentSize=64;" The command in this example creates the same virtual disk as the previous create virtualDisk command, however, in this case the user does not know which physical disks are assigned to this disk group. Creating Virtual Disks in an Existing Disk Group To add a new virtual disk to an existing disk group, use the following command: create virtualDisk DiskGroup=diskGroupNumber userLabel="virtualDiskName" [freeCapacityArea= freeCapacityIndexNumber | capacity= virtualDiskCapacity | owner=(0 | 1) | segmentSize= segmentSizeValue] NOTE: The freeCapacityArea, capacity, owner, and segmentSize parameters are optional. You can use one or all optional parameters as needed to help define your configuration, though you do not need to use any of them. The diskGroup parameter is the number of the disk group in which you want to create a new virtual disk. If you do not know the disk group numbers on the storage array, you can use the show allVirtualDisks summary command. This command displays a list of the virtual disks and the disk groups to which the virtual disks belong. The userLabel parameter is the name you want to give to the virtual disk. The virtual disk name can be any combination of alphanumeric characters, hyphens, and underscores. The maximum length of the virtual disk name is 30 characters. You must enclose the virtual disk name with quotation marks (" "). 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

The command in this example automatically creates a new disk group and a virtual disk with the name
Engineering_1
.
The disk group has a RAID level of 5 (RAID 5). The command uses three physical disks to construct the disk group. The
virtual disk created has a capacity of 20 GB. If each physical disk has a capacity of 73 GB, the total capacity of the disk
group is 219 GB.
Because only 20 GB are assigned to the virtual disk, 199 GB remain available for other virtual disks that you can later add
to this disk group. The segment size for each virtual disk is 64 KB. Hot spares have not been created for this new disk
group. You must create hot spares after running this command.
Creating Virtual Disks with Software-Assigned Physical Disks
You can let the MD Storage Manager software assign the physical disks when you create the virtual disk. To have the
software assign the physical disks, you need only specify the number of physical disks to use. The MD Storage Manager
software then chooses the physical disks on which the virtual disk is created. The RAID controller module firmware
assigns a disk group number to the new disk group. The following syntax is the general form for the command:
create virtualDisk physicalDiskCount=
numberOfPhysicalDisks raidLevel=(0 | 1 | 5 | 6)
userLabel="virtualDiskName" [physicalDiskType=
(SAS)] [capacity=virtualDiskCapacity | owner=(0 |
1) | segmentSize=segmentSizeValue]
[enclosureLossProtect=(TRUE | FALSE)])
NOTE:
The
physicalDiskType
,
capacity
,
owner
,
segmentSize
, and
enclosureLossProtect
parameters are optional. You can use one or all of the optional parameters as needed to help define your
configuration. You do not, however, need to use any optional parameters.
This command is similar to the previous
create virtualDisk
command, which allows the user to assign the
physical disks. This version of the command requires only the number and the type of physical disks to use in the disk
group. You do not need to enter a list of physical disks. All other parameters are the same. Enclosure loss protection is
performed differently when MD Storage Manager assigns the physical disks as opposed to when a user assigns the
physical disks. (For an explanation of the difference, see Enclosure Loss Protection.)
Example of Creating Virtual Disks with Software-Assigned Physical Disks
client>smcli 123.45.67.89 -c "create virtualDisk
physicalDiskCount=3 raidLevel=5 userLabel=
\"Engineering_1"\ capacity=20 GB owner=0
segmentSize=64;"
The command in this example creates the same virtual disk as the previous
create virtualDisk
command,
however, in this case the user does not know which physical disks are assigned to this disk group.
Creating Virtual Disks in an Existing Disk Group
To add a new virtual disk to an existing disk group, use the following command:
create virtualDisk DiskGroup=diskGroupNumber
userLabel="virtualDiskName" [freeCapacityArea=
freeCapacityIndexNumber | capacity=
virtualDiskCapacity | owner=(0 | 1) | segmentSize=
segmentSizeValue]
NOTE:
The
freeCapacityArea
,
capacity
,
owner
, and
segmentSize
parameters are optional. You can
use one or all optional parameters as needed to help define your configuration, though you do not need to use any
of them.
The
diskGroup
parameter is the number of the disk group in which you want to create a new virtual disk. If you do not
know the disk group numbers on the storage array, you can use the
show allVirtualDisks summary
command. This command displays a list of the virtual disks and the disk groups to which the virtual disks belong.
The
userLabel
parameter is the name you want to give to the virtual disk. The virtual disk name can be any
combination of alphanumeric characters, hyphens, and underscores. The maximum length of the virtual disk name is 30
characters. You must enclose the virtual disk name with quotation marks (" ").
37