Filter
Top Products
Chapter 7 HPSS User Interface Configuration
458 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
Block devices:
2 fd
3 ide0
8 sd
22 ide1
65 sd
66 sd
The block device that matches our major number (3) is ide0.
3. Now put this information together to form the media descriptor. Since the format is
<adapter>(<major>,<minor>), for our example the media descriptor is ide0(3,71).
Option specifies how the filesets on the filesystem will be managed by HPSS. The parameter may
be either archive/delete, or archive/rename. In either case, only files are archived by HPSS (not
directories), and the files can only be accessed from XFS. If archive/delete is selected, any files
deleted from XFS will also be deleted from HPSS. If archive/rename is selected, any file deleted
from XFS is not deleted from HPSS, but renamed instead. This allows for the possibility of restoring
a file later, if it was accidentally deleted.
MigratePolicy and PurgePolicy specify the name of the policies that will be used to migrate and
purge files on this aggregate. The name of the migrate policy must appear in the MigratePolicy
section of policy.dat, and the name for the purge policy must appear in the PurgePolicy section of
the file. In the example above, the names of the policies are wait and run, but these names have no
special meaning to HDM. Section 7.6.3.3.4: policy.dat File on page 459 discusses policy.dat in detail.
MPQueueSize specifies the number of entries the HDM will allocate in shared memory for
tracking migration and purge candidates. Refer to Section 7.6.2.8.1: Migration/Purge Algorithms and
the MPQueue on page 444 for information and advice regarding this parameter.
Ftid specifies the fileset ID. The parameter is specified in the form <high>.<low>, where <high>
and <low> are numbers representing the high and low 32 bits for the fileset ID. This ID should be
the same as the fileset Id of the HPSS fileset.
When a fileset is only partially configured, the global mount point is represented by a ‘?’. Typically,
this happens only for a short period of time while the administrator is setting up the HPSS fileset.
To complete the configuration, an administrator will create the HPSS fileset using either SSM or the
create_fset utility.
An administrator must not edit filesys.dat to "fix" the "?"s! This data will be assigned when the
HPSS fileset is created.
Gateway specifies the fully qualified name of the host where the DMAP Gateway that will manage
this fileset runs. If the fileset is partially configured, the host name is represented by a ‘?’. That
prevents end users from accessing the XFS filesystem. To complete the configuration, an
administrator will use SSM to create the HPSS fileset.
Port specifies the TCP port that the DMAP Gateway uses to listen for requests from HDM.
Conventionally, this is 7001. Do not confuse this port number with the port number used by HDM
to listen for requests from the DMAP Gateway (6002). Until the fileset is fully configured, the port
will be shown as zero.