Hp StorageWorks Scalable File Share Bedienungsanleitung Seite 207
- Seite / 362
- Inhaltsverzeichnis
- FEHLERBEHEBUNG
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Replacing hardware components 8–9
disk drive as soon as possible, because if a second disk drive fails, it will cause the entire logical
drive to fail.
• If the status of any logical drive on the array is set to recovery in progress, this indicates
that the logical drive is being rebuilt. Do not proceed to Step 2 while any logical drive on the
array shows the recovery in progress status.
• If the status of any logical drive on the array is set to recovery ready, this indicates that the
logical drive is ready to rebuild, but is waiting for another logical drive to finish rebuilding (the
logical drive that is currently rebuilding will have the recovery in progress status). The
recovery ready status is a temporary one, and it will change to recovery in progress
when the logical drive starts rebuilding
. Do not proceed to Step 2 while any logical drive on the
array is showing the recovery ready status.
• If the status of all logical drives on the array is set to ok, this indicates that there is no RAID
rebuild in progress on the array, and you can proceed to Step 2.
2. Replace the disk.
3. Wait for at least two minutes to allow the monitoring software to scan the array, then enter the show
array array_number command and look at the output to determine the status of the new disk. If
the status of the disk is not set to ok, reseat the disk (that is, take the disk out and put it back in again)
or insert a different disk.
If the replacement disk is not recognized after several attempts, contact your HP Customer Support
representative and report the problem.
4. Wait for at least two minutes to allow the monitoring software to scan the array, then enter the show
array array_number command and look at the output to determine the status of the logical drives
on the array. The RAID rebuild should now be in process, and the logical drives should show a status
of recovery in progress, or recovery ready. When the rebuild is finished, the status should
change to ok.
If the logical drive still has a failed status, the logical drive may be damaged and may need to be
reconstructed. In this event, you can attempt to reconstruct the logical drive as described in
Section 9.40; if this does not allow you to recover the data from the logical drive, contact your HP
Customer Support representative.
In the rare circumstances where you need to replace a second disk in the array, you must wait for the RAID
rebuild that is triggered when the first disk is replaced to complete before you proceed to replace the second
disk. Use the array array_number command as described in Step 1 above to determine when the RAID
rebuild has completed.
8.1.11 Replacing an SFS20 controller module
Replacing an SFS20 controller module usually triggers the battery packs on the array to recharge. This can
take some time (on average, about two hours, but possibly up to six and a half hours). During this time, the
array works in an extremely degraded mode.
Configuration impact
The serial number of the array changes; the array number remains the same.
Note the following points:
• You must ensure that the module you are putting into the array has a cache and batteries. The
modules do not come with these installed, and you may have to remove the cache and batteries from
the old controller and place them in the new controller.
- System User Guide 1
- Version 2.2 1
- Contents 3
- 4 Viewing system information 4
- A CLI commands 9
- About this guide 11
- HP SFS documentation 12
- Documentation conventions 12
- Naming conventions 13
- For more information 13
- Providing feedback 13
- Safety considerations 15
- 1Overview 17
- 1.1 Product overview 18
- 1.1.2 Overview of HP SFS 19
- 1.1.3 HP SFS configurations 20
- 1.1.3.2 Storage 21
- 1.1.3.3 Network connections 23
- 1.1.3.3.2 Management network 24
- 1.3 Supported hardware 25
- Overview1–10 26
- 2 The sfsmgr utility 27
- 2.1 Overview 28
- 2.2 Starting the SFS CLI 28
- 2.3 Running sfsmgr commands 29
- The sfsmgr utility2–6 32
- 3 Operating the system 33
- 3.1 Booting the system 34
- 3.2 Shutting down the system 36
- 3.3 Booting a server 36
- 3.4 Booting multiple servers 37
- 3.7 Stopping a file system 39
- 3.8 Starting a file system 40
- 3.11 Managing licenses 47
- 3.12 Managing remote access 53
- 3.12.3 Viewing authorizations 55
- 4Viewing system information 57
- 4.4 Viewing LUN information 67
- 4.5 Viewing array information 69
- 4.6 Viewing event logs 72
- 4.6.1.1 Event filters 73
- 4.6.1.2 Event severity 73
- 4.6.1.3 Event facility 73
- LUNs — EVA4000 storage 88
- File system name 100
- Mount point 100
- Stripe size 100
- MDS LUNs 100
- Number of OST services 101
- Interconnects 102
- Quota options 102
- Mount options 102
- Stripe count 102
- 5.4 Operating a file system 111
- 5.7 Managing quotas 121
- command on 123
- # lfs quotacheck -ug /data 124
- 5.7.3 Checking quota limits 125
- 5.10 Deleting file systems 127
- 6.1 Verifying the system 132
- Verifying the system 6–5 135
- # ssh south3-adm hostname 150
- Sequential test 151
- Parallel test 152
- Incremental test 152
- Latency test 157
- Unidirectional bandwidth test 158
- Verifying the system 6–33 163
- 6.2 Managing email alerts 169
- 6.2.4 Default email alerts 171
- Managing email alerts 6–43 173
- 6.2.5 Modifying email alerts 174
- 6.2.6 Creating email alerts 174
- 6.2.7 Viewing email alerts 175
- 6.2.9 Deleting email alerts 176
- 6.5 Removing log files 180
- 6.6.1 Overview 181
- 6.6.2 Viewing the IML 181
- 6.6.3 Clearing the IML 181
- Configuration impact 201
- Object Storage Server 202
- Number FCA2214 DC) 204
- [root@south4 var]# raw -qa 206
- 8.2 Upgrading firmware 214
- # service cluster stop 216
- 8.3.3 Adding SFS20 arrays 222
- 8.3.4 Removing SFS20 arrays 222
- 9Troubleshooting 225
- 9.2 Server fails to boot 227
- 9.3 Server stops responding 227
- /proc/fs/lustre/mds/mds2 247
- # repair-lfsck -f scratch 250
- Troubleshooting9–34 258
- Remedial action 261
- 9.27.2.1 Recreating files 262
- 9.30 Accessing consoles 275
- 9.31.1.2 Using a Web browser 276
- 9.32 Troubleshooting licenses 277
- 9.36 System log files 288
- ACLI commands 295
- A.1 General information 296
- A.2 accept license command 297
- A.3 activate ost command 297
- A.4 boot server command 297
- A.5 configure commands 298
- A.5.2 configure server 300
- A.6 create commands 301
- A.6.3 create authorization 302
- A.6.4 create database_backup 302
- A.6.5 create filesystem 303
- A.7 deactivate ost command 304
- A.8 delete commands 304
- A.8.2 delete array 305
- A.8.3 delete attribute 305
- A.8.4 delete authorization 305
- A.9 disable commands 306
- A.9.2 disable server 307
- A.10 enable commands 308
- A.11 help command 309
- A.12 kill command command 309
- A.13 modify commands 310
- Interactive mode 311
- Scripted mode 311
- A.14 monitor command command 312
- A.15 pause filesystem command 312
- A.16 quit command 313
- A.18 scan mac command 313
- A.19 set commands 314
- A.19.2 set attribute 315
- A.19.3 set lun 316
- A.19.4 set nics 317
- A.19.5 set password 318
- A.19.6 set server 318
- A.20 show commands 319
- A.20.4 show authorization 320
- A.20.5 show commands 320
- A.20.6 show database_backups 321
- A.20.7 show filesystem 321
- A.20.8 show license 321
- A.20.9 show log 321
- Examples 322
- A.20.10 show lun 323
- A.20.11 show network 323
- A.20.12 show ost 323
- A.20.13 show server 324
- A.20.14 show support 324
- A.20.15 show system 324
- A.20.16 show version 324
- A.21 shutdown server command 325
- A.22 start filesystem command 325
- A.23 stop filesystem command 326
- A.24 syscheck command 326
- A.26 ! command 328
- B Performance figures 329
- B.1 I/O performance 330
- SFS20 storage — 250GB disks 331
- SFS20 storage — 5000GB disks 331
- B.2 Network performance 332
- B.3 SFS20 array configuration 333
- RAID5 and ADG Read Bandwidth 334
- 64 clients 336
- 128 Clients 336
- 192 clients 336
- Bandwidth vs Clients 337
- Single Client Varying OSTs 338
- 1500 MTU Average Write MB/sec 339
- 9000 MTU Average Read MB/sec 340
- C.1 EVA4000 storage examples 344
- EVA4000 storage examples C–3 345
- C.2 SFS20 storage examples 346
- SFS20 storage examples C–5 347
- D.1 RAID rebuild information 350
- E HP SFS specifications 351
- HP SFS specificationsE–4 354
- Glossary 355
- Glossary–2 356
- Glossary–3 357
- Glossary–4 358
- 9-24, 9-25 361
Verwandte Produkte und Handbücher für Lager Hp StorageWorks Scalable File Share
Lager Hp SAN Bedienungsanleitung
(30 Seiten)
(30 Seiten)
© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.026 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern