HP XP20000/XP24000 HP StorageWorks MPX200 Multifunction Router User Guide (569 - Page 82

Unmounting file systems, Presenting EVA storage for Linux, iSCSI Initiator setup for VMware

Page 82 highlights

Unmounting file systems You must unmount all file systems on iSCSI devices before the iSCSI driver stops. If the iSCSI driver stops while iSCSI devices are mounted, buffered writes may not be committed to disk, and file system corruption may occur. Linux does not unmount file systems that are being used by a process; therefore, any process using those devices must be stopped (see the man page for fuser(1)) before iSCSI devices can be unmounted. To prevent file system corruption, the iSCSI shutdown script automatically stops all processes using devices in /etc/fstab.iscsi. The script sends a SIGTERM signal to stop the processes, followed by a SIGKILL signal to stop any remaining processes. It then unmounts all iSCSI file systems and stops the iSCSI daemon, terminating all connections to iSCSI devices. CAUTION: File systems not listed in /etc/fstab.iscsi cannot be unmounted automatically. Presenting EVA storage for Linux To present EVA storage for Linux: 1. Set up the LUNs by using HP Command View EVA, as described in Step 2 on page 63. 2. Set up the iSCSI drive on the iSCSI initiator. a. Restart the iSCSI services: /etc/rc.d/initd/iscsi restart b. Verify that the iSCSI LUNs are presented to the operating system: fdisk -l iSCSI Initiator setup for VMware The software iSCSI Initiator is built into the ESX server VMkernel and uses standard 10GigE/GigE NICs to connect to the MPX200. To set up software-based iSCSI storage connectivity: 1. Install the appropriate license from VMware to enable iSCSI software driver using the VMware instructions. 82 MPX200 iSCSI configuration rules and guidelines

  • 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
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282

Unmounting file systems
You must unmount all file systems on iSCSI devices before the iSCSI driver stops. If the iSCSI driver
stops while iSCSI devices are mounted, buffered writes may not be committed to disk, and file system
corruption may occur.
Linux does not unmount file systems that are being used by a process; therefore, any process using
those devices must be stopped (see the man page for
fuser(1)
) before iSCSI devices can be
unmounted.
To prevent file system corruption, the iSCSI shutdown script automatically stops all processes using
devices in
/etc/fstab.iscsi
. The script sends a SIGTERM signal to stop the processes, followed
by a SIGKILL signal to stop any remaining processes. It then unmounts all iSCSI file systems and stops
the iSCSI daemon, terminating all connections to iSCSI devices.
CAUTION:
File systems not listed in
/etc/fstab.iscsi
cannot be unmounted automatically.
Presenting EVA storage for Linux
To present EVA storage for Linux:
1.
Set up the LUNs by using HP Command View EVA, as described in
Step 2
on page 63.
2.
Set up the iSCSI drive on the iSCSI initiator.
a.
Restart the iSCSI services:
/etc/rc.d/initd/iscsi restart
b.
Verify that the iSCSI LUNs are presented to the operating system:
fdisk -l
iSCSI Initiator setup for VMware
The software iSCSI Initiator is built into the ESX server VMkernel and uses standard 10GigE/GigE
NICs to connect to the MPX200.
To set up software-based iSCSI storage connectivity:
1.
Install the appropriate license from VMware to enable iSCSI software driver using the VMware
instructions.
MPX200 iSCSI configuration rules and guidelines
82