Hp StorageWorks Scalable File Share Instrukcja Użytkownika Strona 143
- Strona / 362
- Spis treści
- ROZWIĄZYWANIE PROBLEMÓW
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
Verifying the system 6–13
• Use the following table to determine the drive_number for the array; the drive number is
derived from the bay number. For example, the drive number for the disk in bay 3 is 130.
In the following example, the hpls_cciss_info command gets the status of the disk in bay
10:
# hpls_cciss_info -i -D 1,2,0,145
CONTROLLER:1:BUS:2:DRIVE:145:BLOCKSIZE:512:BLOCKS:488397168:BOX:1:BAY:10:TYP
E:
SERIAL_ATA:RPM:0:MODEL:Maxtor
7Y250M0 :SERIAL:Y6915WHE :FIRMWARE:YAR51KW0:
DISKSTATUS:logvol,smartcapable,smartenabled,smartfactoryerr
If one or more of the following values are displayed in the DISKSTATUS field, this indicates that
a disk failure is predicted:
• smartfactoryerr — predictive failure (01/5D) errors are recorded in the Factory M&P
data for this drive.
• smartpowererr — predictive failure (01/D5) errors are recorded in the Since Power
M&P data for this drive.
TIP: You can use the diskinfo wrapper script for the hpls_cciss_info command to view
the drive status on all SFS20 arrays attached to a server. To run the diskinfo script, enter the
following command on the server:
# /usr/opt/hpls/diags/bin/diskinfo -v
The command reports disk and controller information for all arrays attached to the server. The
-v argument is optional; if you do not use it, the command provides the report in a shorter
summary format.
9. Check that there are no errors being logged for disks.
If errors are being logged, events such as the following are generated:
2005/04/08 09:47:07 storage !! south1: P6C8CX7MQPS7UK: array 1: disk bay 12:
disk Y6912TFE is logging errors (was online)
You can search for these events in the system log by entering the following command:
sfs> show log facility=storage && data contains "disk bay"
If you find such events in the log, you can confirm the current status of the disk by entering the
hpls_cciss_info command using the following syntax:
hpls_cciss_info -E -D controller,port,0,drive_number
See Step 8 for information on how to determine the controller, port, and drive_number
values to use in the command.
In the following example, the hpls_cciss_info command gets the status of the disk in bay 10:
# hpls_cciss_info -E -D 1,2,0,145
Disk 1,2,0,145: logged 39 offset 19
[13] type 1 scsi_op 40 sense 0x4 qual 0 sense_code 0x8 (10 mins ago)
[18] type 1 scsi_op 40 sense 0x3 qual 0 sense_code 0x11 (5 mins ago)
Medium Error: Unrecovered Read Error
Bay Drive
Number
Bay Drive
Number
Bay Drive
Number
Bay Drive
Number
1 128 4 131 7 134 10 145
21295132813511146
31306133914412147
- 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
Powiązane produkty i podręczniki dla Przechowywanie Hp StorageWorks Scalable File Share
(107 strony)© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.066 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji