Hp StorageWorks Scalable File Share Bedienungsanleitung Seite 126
- Seite / 362
- Inhaltsverzeichnis
- FEHLERBEHEBUNG
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Creating and modifying file systems5–42
5.7.4 Disabling quota functionality on one or all file systems
You can disable quota functionality on a specific file system by entering the modify filesystem
command, selecting the Change quota options menu option, and then disabling quotas on the file
system (see Section 5.6.5 for more information on changing file system attributes).
To disable quota functionality for all file systems on a client node, remove the lquota option from the
/etc/modprobe.conf.lustre file or the /etc/moduldes.conf.lustre file on the node and then
remount all Lustre file systems on the node. When you are remounting each file system, make sure that no
other Lustre file system is mounted on the client node; otherwise, the lquota module will not unload on the
client node.
You must repeat this process on each client node where you want to disable quota functionality.
When the lquota options are removed from the /etc/modprobe.conf.lustre file or the
/etc/modules.conf.lustre file on a client node, the lquota module will not be loaded on the node
and quotas will not be enforced on the node. You do not need to disable quota functionality on the file
system itself or to disable the HP SFS system-wide quota attribute. However, depending on which options
and mode you use, the sfsmount(8) command may report an error. In addition, the sfsconfig(8)
command will attempt to re-enable the lquota module. To prevent this from happening, disable quota
functionality on the file system. (The sfsmount and sfsconfig commands are described in Chapter 4 of
the HP StorageWorks Scalable File Share Client Installation and User Guide.)
If no file system has quota functionality enabled, you can remove the lquota module on client nodes as
described above.
5.8 Managing supplementary groups resolution
The HP SFS system does not resolve secondary groups directly. Instead, it uses one or more user-supplied
group servers. You have the option of configuring group server(s) before or after you create a file system.
Refer to Chapter 9 of the HP StorageWorks Scalable File Share System Installation and Upgrade Guide for
information on configuring and managing group servers.
5.9 Creating a system nickname
The system name and nickname are not file system attributes, but they have important effects on file system
properties. The system name is used by client nodes to distinguish the Lustre devices belonging to different
HP SFS systems; that is, the system name (without the domain name) is used as the prefix in the device name.
For example, a client may be connected to two HP SFS systems, one called south and the second named
west, each having a single MDS service called mds1. The client node can distinguish between the two
MDS services, because the MDS service names presented to the client are south-mds1 and west-mds1.
However, a problem arises if the same system name has been used for different HP SFS systems. For
example, a company may have two HP SFS systems, one with the fully qualified domain name
south.my.domain.com and the second with the fully qualified domain name south.fs.org. A client
node attempting to connect to both of these systems would see an MDS device named south-mds1 on
both systems. If this problem occurs, a system nickname can be defined for use in Lustre device names
instead of the system name.
The system nickname must be a valid host name of not more than 18 characters; HP recommends that you
use a shorter name (not more than 10 characters).
To create or change a system nickname, perform the following steps:
1. Unmount all file systems on all client nodes.
CAUTION: If a file system is mounted on a client node during the process of changing the system
nickname, it may cause serious problems: client nodes may become unstable, or may crash or
hang.
- 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.031 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern