Dell PowerVault MD3260 Administrator's Guide - Page 124

Add A New Partition To Device Mapper, Create A File System On A Device Mapper Partition

Page 124 highlights

Add A New Partition To Device Mapper The kpartx command adds the new fdisk partition to the Device Mapper list of usable partitions. See examples below, where mpath is the device node on which the partition was created. # kpartx -a /dev/mapper/mpath If successful, the command does not display an output. To verify success and view exact partition naming, you can use these commands to see the full partition names assigned. # cd /dev/mapper# ls The following are some examples of the general mapping formats: • On Red Hat Enterprise Linux (RHEL) hosts, a partition node has the format:/dev/mapper/mpathp Where is the alphabetic number for the multipathing device, is the partition number for this device. • On SUSE Linux Enterprise Server (SLES) 11.x hosts, a partition node has the format:/dev/mapper/mpathpart Where is letter(s) assigned to the multipathing device and is the partition number. • On SLES 10.3 hosts, a partition node has the format: /dev/mapper/mpath_part Where is the letter(s) assigned to the multipathing device and is the partition number. NOTE: After creating a partition on a device capable of multipathing, all I/O operations, including file system creation, raw I/O and file system I/O, must be done through the partition node, and not through the multipathing device nodes. Create A File System On A Device Mapper Partition Use the standard mkfs command to create the file system on the newly created Device Mapper partition. For example: # mkfs -t /dev/mapper/ where is the partition on which the file system is created. Mount A Device Mapper Partition Use the standard mount command to mount the Device Mapper partition, as shown below: # mount /dev/mapper/ Ready For Use The newly created virtual disks created on the MD Series Dense storage array are now setup and ready to be used. Future reboots automatically find multipathing devices along with their partitions. NOTE: To ensure data integrity protection, reboot a Linux host server attached to an MD Series storage array using the procedure given below. Linux Host Server Reboot Best Practices Its is recommended that you follow the procedures given below when you reboot your Linux host server using Device Mapper multipathing with an MD Series Dense storage array. 124

  • 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

Add A New Partition To Device Mapper
The
kpartx
command adds the new fdisk partition to the Device Mapper list of usable partitions. See examples below,
where
mpath<x>
is the device node on which the partition was created.
# kpartx –a /dev/mapper/mpath<x>
If successful, the command does not display an output. To verify success and view exact partition naming, you can use
these commands to see the full partition names assigned.
# cd /dev/mapper# ls
The following are some examples of the general mapping formats:
On Red Hat Enterprise Linux (RHEL) hosts, a partition node has the format:
/dev/mapper/mpath<x>p<y>
Where <x> is the alphabetic number for the multipathing device, <y> is the partition number for this device.
On SUSE Linux Enterprise Server (SLES) 11.x hosts, a partition node has the format:
/dev/mapper/mpath<x>-
part<y>
Where <x> is letter(s) assigned to the multipathing device and <y> is the partition number.
On SLES 10.3 hosts, a partition node has the format:
/dev/mapper/mpath<x>_part<y>
Where <x> is the letter(s) assigned to the multipathing device and <y> is the partition number.
NOTE:
After creating a partition on a device capable of multipathing, all I/O operations, including file system
creation, raw I/O and file system I/O, must be done through the partition node, and not through the multipathing
device nodes.
Create A File System On A Device Mapper Partition
Use the standard
mkfs
command to create the file system on the newly created Device Mapper partition.
For example:
# mkfs –t <filesystem type> /dev/mapper/<partition node>
where
<partition node>
is the partition on which the file system is created.
Mount A Device Mapper Partition
Use the standard mount command to mount the Device Mapper partition, as shown below:
# mount /dev/mapper/<partition_node> <mounting point>
Ready For Use
The newly created virtual disks created on the MD Series Dense storage array are now setup and ready to be used.
Future reboots automatically find multipathing devices along with their partitions.
NOTE:
To ensure data integrity protection, reboot a Linux host server attached to an MD Series storage array using
the procedure given below.
Linux Host Server Reboot Best Practices
Its is recommended that you follow the procedures given below when you reboot your Linux host server using Device
Mapper multipathing with an MD Series Dense storage array.
124