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

Journaling filesystem, Server registry, Filesystem management and integrity

Page 122 highlights

Journaling filesystem When you initiate certain filesystem operations such as creating, opening, or moving a file or modifying its size, the filesystem writes the metadata, or structural information, for that event to a transaction journal. The filesystem then performs the operation. If a server using the filesystem should crash during an operation, the journal is replayed and any journaled operations in progress at the time of the crash are completed. This procedure ensures that the structure of the filesystem is consistent. Users on other servers will experience only a slight delay in filesystem operations during the recovery. Server registry HP Scalable NAS uses a registry to control server access to PSFS filesystems on the SAN disks imported into the cluster. A server is added to the registry when it mounts its first PSFS filesystem. Under normal operations, a server remains in the registry until it either unmounts its last PSFS filesystem or leaves the cluster. However, if a server crashes or loses communication with the cluster and that server is in the registry (indicating that it had active PSFS mounts), HP Scalable NAS will remove the server's access to the filesystems. When this situation occurs, an alert will appear on the Management Console and a message will be written to the cluster log. You will need to reboot the server to restore its access. After the server is rebooted and rejoins the cluster, it is deleted from the registry. When the server again mounts a PSFS filesystem, it will be added back into the registry. Filesystem management and integrity HP Scalable NAS uses the SANPulse daemon to manage PSFS filesystems. SANPulse performs the following tasks: • Coordinates filesystem mounts, unmounts, and crash recovery operations. • Checks for cluster partitioning, which can occur when cluster network communic- ations are lost but the affected servers can still access the SAN. If this situation occurs, HP Scalable NAS determines which servers should continue to have SAN access and excludes the other servers from the SAN. This step prevents data corruption from occurring. • Communicates filesystem status to the Management Console. It reports both the global status of a filesystem (for example, whether it is up or going through a 122 Configure PSFS filesystems

  • 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

Journaling filesystem
When you initiate certain filesystem operations such as creating, opening, or moving
a file or modifying its size, the filesystem writes the metadata, or structural information,
for that event to a transaction journal. The filesystem then performs the operation.
If a server using the filesystem should crash during an operation, the journal is
replayed and any journaled operations in progress at the time of the crash are
completed. This procedure ensures that the structure of the filesystem is consistent.
Users on other servers will experience only a slight delay in filesystem operations
during the recovery.
Server registry
HP Scalable NAS uses a registry to control server access to PSFS filesystems on the
SAN disks imported into the cluster. A server is added to the registry when it mounts
its first PSFS filesystem. Under normal operations, a server remains in the registry
until it either unmounts its last PSFS filesystem or leaves the cluster.
However, if a server crashes or loses communication with the cluster and that server
is in the registry (indicating that it had active PSFS mounts), HP Scalable NAS will
remove the server
s access to the filesystems. When this situation occurs, an alert will
appear on the Management Console and a message will be written to the cluster
log. You will need to reboot the server to restore its access.
After the server is rebooted and rejoins the cluster, it is deleted from the registry.
When the server again mounts a PSFS filesystem, it will be added back into the
registry.
Filesystem management and integrity
HP Scalable NAS uses the SANPulse daemon to manage PSFS filesystems. SANPulse
performs the following tasks:
Coordinates filesystem mounts, unmounts, and crash recovery operations.
Checks for cluster partitioning, which can occur when cluster network communic-
ations are lost but the affected servers can still access the SAN. If this situation
occurs, HP Scalable NAS determines which servers should continue to have SAN
access and excludes the other servers from the SAN. This step prevents data
corruption from occurring.
Communicates filesystem status to the Management Console. It reports both the
global status of a filesystem (for example, whether it is up or going through a
Configure PSFS filesystems
122