Dell PowerVault MD3260i CLI Guide - Page 166

For configurations with more than 32 virtual disks

Page 166 highlights

Parameter diskGroup addPhysicalDisks raidLevel owner Description Sequence number of the disk group for which to set properties. You must put brackets ([ ]) around the disk group number. Identifies the physical disk by enclosure and slot location to include in the disk group. Enclosure ID values are 0 to 99. Slot ID values are 0 to 31. You must put parentheses around the enclosure ID values and the slot ID values. The RAID level for the disk group. Valid values are 0, 1, 5, or 6. The RAID controller module that owns the disk group. Valid RAID controller module identifier values are 0 and 1. The identifier value is 0 for the RAID controller module on the top and 1 for the RAID controller module on the bottom when viewed from the rear of the enclosure. Use this parameter only if you want to change the disk group owner. NOTE: When using this command, you can specify one or more of the parameters. You do not, however, need to use all of the parameters. Using too many parameters can cause host I/O errors or result in internal controller reboots because the time period ends before the disk group definition is set. NOTE: For configurations with more than 32 virtual disks, it is recommended you quiesce host I/O operations when executing this command. Troubleshooting Attempting to expand large disk groups by adding physical disks, also called Dynamic Capacity Expansion (DCE), may fail with the one of the following messages: • Return code: Error 26-The modification operation cannot complete because of the number of physical disks in the disk group and the segment size of the associated virtual disks. Reduce the segment size of all virtual disks in the disk group to 128 KB or below using the Change Segment Size option. Then, retry the operation. • Return code: Error 462-A SYMbol procedure could not be carried out because the firmware could not allocate sufficient cache memory. Operation when error occurred: PROC_startVolum. In addition, a Major Event Log (MEL) event indicating insufficient cache available to complete the DCE operation may occur. DCE requires enough memory to buffer the data read from the original virtual disk and the data to be written to the expanded virtual disk. Some combination of number of physical disks in the expansion operation, stripe size, and whether mirroring is enabled may result in less memory being available to complete the DCE operation. In such a scenario, try each of the options below and retry the operation: • Create the required disk group size using other unassigned physical disks. • Delete the current disk group and then recreate the disk group with the desired number of physical disks. • Reduce the segment size being used and then retry the operation. 166

  • 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

Parameter
Description
diskGroup
Sequence number of the disk group for which to set
properties. You must put brackets ([ ]) around the disk
group number.
addPhysicalDisks
Identifies the physical disk by enclosure and slot location
to include in the disk group. Enclosure ID values are
0
to
99
. Slot ID values are
0
to
31
. You must put parentheses
around the enclosure ID values and the slot ID values.
raidLevel
The RAID level for the disk group. Valid values are
0
,
1
,
5
,
or
6
.
owner
The RAID controller module that owns the disk group.
Valid RAID controller module identifier values are
0
and
1
.
The identifier value is
0
for the RAID controller module on
the top and
1
for the RAID controller module on the
bottom when viewed from the rear of the enclosure. Use
this parameter only if you want to change the disk group
owner.
NOTE:
When using this command, you can specify one or more of the parameters. You do not, however, need to
use all of the parameters. Using too many parameters can cause host I/O errors or result in internal controller
reboots because the time period ends before the disk group definition is set.
NOTE:
For configurations with more than 32 virtual disks, it is recommended you quiesce host I/O operations when
executing this command.
Troubleshooting
Attempting to expand large disk groups by adding physical disks, also called Dynamic Capacity Expansion (DCE), may
fail with the one of the following messages:
Return code: Error 26—The modification operation cannot complete because
of the number of physical disks in the disk group and the segment size of
the associated virtual disks. Reduce the segment size of all virtual disks
in the disk group to 128 KB or below using the Change Segment Size option.
Then, retry the operation.
Return code: Error 462—A SYMbol procedure could not be carried out because
the firmware could not allocate sufficient cache memory. Operation when
error occurred: PROC_startVolum
.
In addition, a Major Event Log (MEL) event indicating insufficient cache available to complete the DCE operation
may occur.
DCE requires enough memory to buffer the data read from the original virtual disk and the data to be written to the
expanded virtual disk. Some combination of number of physical disks in the expansion operation, stripe size, and
whether mirroring is enabled may result in less memory being available to complete the DCE operation. In such a
scenario, try each of the options below and retry the operation:
Create the required disk group size using other unassigned physical disks.
Delete the current disk group and then recreate the disk group with the desired number of physical disks.
Reduce the segment size being used and then retry the operation.
166