Computer Drive User Manual
Table Of Contents
- Chapter 1. HPSS 7.1 Configuration Overview
- Chapter 2. Security and System Access
- Chapter 3. Using SSM
- 3.1. The SSM System Manager
- 3.2. Quick Startup of hpssgui
- 3.3. Configuration and Startup of hpssgui and hpssadm
- 3.4. Multiple SSM Sessions
- 3.5. SSM Window Conventions
- 3.6. Common Window Elements
- 3.7. Help Menu Overview
- 3.8. Monitor, Operations and Configure Menus Overview
- 3.9. SSM Specific Windows
- 3.10. SSM List Preferences
- Chapter 4. Global & Subsystem Configuration
- 4.1. Global Configuration Window
- 4.2. Storage Subsystems
- 4.2.1. Subsystems List Window
- 4.2.2. Creating a New Storage Subsystem
- 4.2.3. Storage Subsystem Configuration Window
- 4.2.3.1. Create Storage Subsystem Metadata
- 4.2.3.2. Create Storage Subsystem Configuration
- 4.2.3.3. Create Storage Subsystem Servers
- 4.2.3.4. Assign a Gatekeeper if Required
- 4.2.3.5. Assign Storage Resources to the Storage Subsystem
- 4.2.3.6. Create Storage Subsystem Fileset and Junction
- 4.2.3.7. Migration and Purge Policy Overrides
- 4.2.3.8. Storage Class Threshold Overrides
- 4.2.4. Modifying a Storage Subsystem
- 4.2.5. Deleting a Storage Subsystem
- Chapter 5. HPSS Servers
- 5.1. Server List
- 5.1. Server Configuration
- 5.1.1. Common Server Configuration
- 5.1.1. Core Server Specific Configuration
- 5.1.2. Gatekeeper Specific Configuration
- 5.1.3. Location Server Additional Configuration
- 5.1.4. Log Client Specific Configuration
- 5.1.1. Log Daemon Specific Configuration
- 5.1.2. Migration/Purge Server (MPS) Specific Configuration
- 5.1.3. Mover Specific Configuration
- 5.1.3.1. Mover Specific Configuration Window
- 5.1.3.1. Additional Mover Configuration
- 5.1.3.1.1. /etc/services, /etc/inetd.conf, and /etc/xinetd.d
- 5.1.3.1.2. The Mover Encryption Key Files
- 5.1.3.1.3. /var/hpss/etc Files Required for Remote Mover
- 5.1.3.1.1. System Configuration Parameters on IRIX, Solaris, and Linux
- 5.1.3.1.1. Setting Up Remote Movers with mkhpss
- 5.1.3.1.2. Mover Configuration to Support Local File Transfer
- 5.1.1. Physical Volume Repository (PVR) Specific Configuration
- 5.1.1. Deleting a Server Configuration
- 5.1. Monitoring Server Information
- 5.1.1. Basic Server Information
- 5.1.1. Specific Server Information
- 5.1.1.1. Core Server Information Window
- 5.1.1.1. Gatekeeper Information Window
- 5.1.1.1. Location Server Information Window
- 5.1.1.2. Migration/Purge Server Information Window
- 5.1.1.3. Mover Information Window
- 5.1.1.1. Physical Volume Library (PVL) Information Window
- 5.1.1.2. Physical Volume Repository (PVR) Information Windows
- 5.1. Real-Time Monitoring (RTM)
- 5.2. Starting HPSS
- 5.1. Stopping HPSS
- 5.2. Server Repair and Reinitialization
- 5.1. Forcing an SSM Connection
- Chapter 6. Storage Configuration
- 6.1. Storage Classes
- 6.2. Storage Hierarchies
- 6.3. Classes of Service
- 6.4. Migration Policies
- 6.5. Purge Policies
- 6.6. File Families
- Chapter 7. Device and Drive Management
- Chapter 8. Volume and Storage Management
- 8.1. Adding Storage Space
- 8.2. Removing Storage Space
- 8.3. Monitoring Storage Space
- 8.4. Dealing with a Space Shortage
- 8.5. Volume Management
- 8.6. Monitoring and Managing Volume Mounts
- 8.7. New Storage Technology Insertion
- Chapter 9. Logging and Status
- Chapter 10. Filesets and Junctions
- Chapter 11. Files, Directories and Objects by SOID
- Chapter 12. Tape Aggregation
- Chapter 13. User Accounts and Accounting
- Chapter 14. User Interfaces
- Chapter 15. Backup and Recovery
- Chapter 16. Management Tools

Mount Option Mount Description
acdirtimeo
Seconds to cache directory attributes. The shorter this value, the more frequently
communication to HPSS is required. Synchronization between separate vfs nodes
or mount points may benefit for a shorter cache period with the expense of longer
latencies.
flushd
The flush deamons look for data pages that need to be written to HPSS, either time
to write or data pages being requested for other files. Each daemon consumes
resources so care should be taken when changing this option. Another possibility is
to change iomax to allow more pages to be available.
rtimeo / wtimeo
Performance gains can be realized when minimizing the number of transfers. This
timeout allows multiple requests to be combined within the time limit.
rpages / wpages
Each specifies the maximum number of kernel buffer pages that can be dedicated to
individual file transfers. Care must be taken to configure this correctly to the
expected number of concurrent transfers and the iomax mount option.
iomax
Maximum number of kernel buffer pages (4096 bytes + overhead) that can be
allocated for data buffers when transferring file data. Each mount point has its own
set of data buffers. Since these pages consume RAM resources, this must be
compatible with application loads and transfer goals for the system. For instance,
the more pages allocated to the mount point, the less RAM available for
applications. This should also be consistent with rpages and wpages.
fcsize
File Cache Size. Cache this much of the file on first access. This consumes
resources so care must be taken not to make this too large. Configuring this to
typical file access patterns will speed access when large enough to cache future
requests.
san / nosan
Configures the mount point to transfer data from buffers directly to SAN devices.
shm
Shared Memory (need to look into this)
dio
Configures the mount point to transfer data to/from directly from application space.
This bypasses Linux VFS file buffering, see ???? for a discussion on advantages
that the Linux VFS buffering provides.
trace
Level of messages logged from the HPSS kernel extension to /var/log/messages.
Ranges from 0 to 5 with 0 being the least and 5 being lots.
sharefd / nosharefd
rattr
Typically short directory listings do not have to access HPSS for file attributes.
Specifying this option will force all directory listings to retrieve file attributes from
HPSS. If the application is always doing long directory listings this has no effect. If
the application always requests short directory listings, this will delay those requests
needlessly.
ip
Configure the network interfaces to use.
cos
Specify the default Class Of Service to use. This can be overridden by an ioctl()
system call once the file is created but BEFORE any data is written. Standard Linux
commands / library functions will not use the ioctl(), they will use the COS setting for
files stored in a fileset.
ro / rw
File system will be ro=read only or rw=read write.
maxsegsz
Use the maximum segment size for the storage class. If not used, the minimum
segment size is used. An application can use ioctl() to set this per file once the file is
created but BEFORE any data is written.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 353