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
character device (/dev/hpssfs0) that is used to communicate with the HPSS VFS Daemon
(hpssfsd). All POSIX I/O system calls like open, read, write, close, etc. are first handled by the
VFS abstraction layer after which they are passed down to appropriate functions in the Kernel
Module. The Kernel Module translates the POSIX I/O requests into HPSS requests and then
forwards these requests (via /dev/hpssfs0) to the HPSS VFS Daemon (hpssfsd), which in turn
sends requests to the Core Server.
• HPSS VFS Device Special File (/dev/hpssfs0) – This character device special file corresponds to
a Linux character device and provides the means for sending HPSS requests and receiving HPSS
replies between the Kernel Module and the HPSS VFS Daemon.
• HPSS VFS Daemons (hpssfsd) – The daemon is linked against the HPSS Client API library. It
translates Kernel Module requests to Client API library calls and converts Client API library call
responses back into Kernel Module replies. Instances of the HPSS VFS Daemon are started for
every Linux file system mount.
• HPSS VFS Mount Helper (mount.hpssfs) – The mount helper is spawned by the mount command.
• The Mount Helper calls the mount system call which in turn drills down to the Kernel Module to
do kernel mount processing. The mount helper also spawns one or more HPSS VFS Daemons.
The installation and configuration process populates the system with the above components.
14.3.2. Supported Linux Versions
The VFS Interface is currently only supported on Linux platforms for the Intel x86 and Power PC with
the following kernel version:
• 2.6.18-164.EL5smp (RHEL 5.4 on Intel x86 64-bit and Power PC)
Use the "uname -a" command to determine the kernel version and architecture of the client machine. It is
necessary to modify the client machine's operating system to match the above prerequisites since the
operating system level must match the environment in which the VFS Interface rpm packages were
generated.
14.3.3. Installation and Configuration of VFS
14.3.3.1. Extracting from HPSS Source Tree
In additional to the VFS specific code, the HPSS client API is a pre-requisite for installing VFS on a
client machine. For that reason, the extraction process includes both the ‘fs’ (VFS specific code) and
‘clnt’ (HPSS Client API) packages.
On the HPSS Core Server machine as ‘root’:
% mkdir /tmp/vfs_client
% cd /opt/hpss
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 346