Dell PowerVault MD3200 Owner's Manual - Page 169

Device Mapper Configuration Steps, Scan for Newly Added Virtual Disks

Page 169 highlights

Device Mapper Configuration Steps To complete the DM multipathing configuration and make the storage available to the Linux host server: 1 Scan for virtual disks. See "Scan for Newly Added Virtual Disks" on page 169. 2 Display the multipath device topology. See "Display the Multipath Device Topology Using the Multipath Command" on page 169. 3 Create a partition on a multipath device node. See "Create a New fdisk Partition on a Multipath Device Node" on page 171. 4 Add a partition to DM. See "Add a New Partition to Device Mapper" on page 171. 5 Create a file system on a DM partition. See "Create a File System on a Device Mapper Partition" on page 172. 6 Mount a DM partition. See "Mount a Device Mapper Partition" on page 172. The following instructions show how to complete each of these steps. In the following command descriptions is used to indicate where a substitution should be made. On RHEL systems is the number assigned to the device. On SLES systems is the letter(s) assigned to the device. Scan for Newly Added Virtual Disks The rescan_dm_devs command scans the host server system looking for existing and newly added virtual disks mapped to the host server. # rescan_dm_devs If an array virtual disk (VD) is mapped to the host server at a later time the rescan_dm_devices command must be run again to make the VD a visible LUN to the operating system. Display the Multipath Device Topology Using the Multipath Command The multipath command adds newly scanned and mapped virtual disks to the Device Mapper tables and creates entries for them in the /dev/mapper directory on the host server. These devices are the same as any other block devices in the host. To list all the multipath devices run the following command. Configuration: Device Mapper Multipath for Linux 169

  • 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
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260

Configuration: Device Mapper Multipath for Linux
169
Device Mapper Configuration Steps
To complete the DM multipathing configuration and make the storage
available to the Linux host server:
1
Scan for virtual disks. See "Scan for Newly Added Virtual Disks" on
page 169.
2
Display the multipath device topology. See "Display the Multipath Device
Topology Using the Multipath Command" on page 169.
3
Create a partition on a multipath device node. See "Create a New fdisk
Partition on a Multipath Device Node" on page 171.
4
Add a partition to DM. See "Add a New Partition to Device Mapper" on
page 171.
5
Create a file system on a DM partition. See "Create a File System on a
Device Mapper Partition" on page 172.
6
Mount a DM partition. See "Mount a Device Mapper Partition" on
page 172.
The following instructions show how to complete each of these steps.
In the following command descriptions <x> is used to indicate where a
substitution should be made. On RHEL systems <x> is the number assigned
to the device. On SLES systems <x> is the letter(s) assigned to the device.
Scan for Newly Added Virtual Disks
The rescan_dm_devs command scans the host server system looking for
existing and newly added virtual disks mapped to the host server.
# rescan_dm_devs
If an array virtual disk (VD) is mapped to the host server at a later time the
rescan_dm_devices
command must be run again to make the VD a
visible LUN to the operating system.
Display the Multipath Device Topology Using the Multipath Command
The multipath command adds newly scanned and mapped virtual disks to the
Device Mapper tables and creates entries for them in the /dev/mapper
directory on the host server. These devices are the same as any other block
devices in the host.
To list all the multipath devices run the following command.