HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 87

Disk partition alignment, Import SAN disks

Page 87 highlights

Disk partition alignment Many disk arrays are sensitive to misaligned I/O operations and require I/O to be aligned on block boundaries for performance reasons. For example, an array may "prefer" to have I/O operations occur on natural block boundaries, such as 4-KB blocks. If a partition starts at a non-block boundary, a single logical write can span more physical blocks that it would on a partition starting on a block boundary, resulting in additional I/O operations. The exact alignment characteristics vary by manufacturer and model; consult your storage vendor for alignment recommendations. This issue occurs because the partition table causes space to be reserved at the start of the LUN, which can cause a misalignment with the array's storage. If your storage array is affected by this issue, the simplest way to avoid the situation is to create an unused partition at the start of the LUN and then ensure that the second partition starts on an aligned boundary. Utilities such as fdisk can be used to create the partitions. NOTE: HP Scalable NAS supports unpartitioned disks. There are no alignment issues when using unpartitioned disks. Import SAN disks SAN disks to be used for PSFS filesystems must be imported into the cluster. This step gives the cluster control over access to the disks. Before importing disks, you should be aware of the following: • If servers from multiple clusters can access the SAN via a shared FC fabric, avoid importing the same disk into more than one cluster. Filesystem corruption can occur when different clusters attempt to share the same filesystem. • If you want to change the partition table on a disk after it has been imported, you will need to deport the disk, make the changes, and then import the disk again. • Disks containing an active membership partition cannot be imported. You will need to use mprepair to inactivate the partition (see The mprepair utility, page 365). After the partition is inactivated, you can import the disk into the cluster. • If you import a large number of disks sequentially, it can take several minutes to complete the imports. The imports will be faster if you specify all of the disks in HP Scalable NAS File Serving Software administration guide 87

  • 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
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435

Disk partition alignment
Many disk arrays are sensitive to misaligned I/O operations and require I/O to be
aligned on block boundaries for performance reasons. For example, an array may
prefer
to have I/O operations occur on natural block boundaries, such as 4-KB
blocks. If a partition starts at a non-block boundary, a single logical write can span
more physical blocks that it would on a partition starting on a block boundary,
resulting in additional I/O operations. The exact alignment characteristics vary by
manufacturer and model; consult your storage vendor for alignment recommendations.
This issue occurs because the partition table causes space to be reserved at the start
of the LUN, which can cause a misalignment with the array
s storage. If your storage
array is affected by this issue, the simplest way to avoid the situation is to create an
unused partition at the start of the LUN and then ensure that the second partition
starts on an aligned boundary. Utilities such as
fdisk
can be used to create the
partitions.
NOTE:
HP Scalable NAS supports unpartitioned disks. There are no alignment issues when
using unpartitioned disks.
Import SAN disks
SAN disks to be used for PSFS filesystems must be imported into the cluster. This step
gives the cluster control over access to the disks. Before importing disks, you should
be aware of the following:
If servers from multiple clusters can access the SAN via a shared FC fabric, avoid
importing the same disk into more than one cluster. Filesystem corruption can
occur when different clusters attempt to share the same filesystem.
If you want to change the partition table on a disk after it has been imported,
you will need to deport the disk, make the changes, and then import the disk
again.
Disks containing an active membership partition cannot be imported. You will
need to use
mprepair
to inactivate the partition (see
The mprepair util-
ity
, page 365). After the partition is inactivated, you can import the disk into the
cluster.
If you import a large number of disks sequentially, it can take several minutes to
complete the imports. The imports will be faster if you specify all of the disks in
HP Scalable NAS File Serving Software administration guide
87