Filter
Top Products
Chapter 7 HPSS User Interface Configuration
454 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
When multiple HDM servers are to be run on the same machine, each HDM must have a unique
SharedMemoryKey. HDM servers cannot share memory or logs without serious consequences.
ZapLogName specifies the name of the file used for the zap log. Typically, this will be /var/hpss/
hdm/hdm<id>/hdm_zap_log. This file contains a record of the archived fileset files that need to be
destroyed. The file must exist before HDM is started, but can be empty. The size of the file is
unbounded, but typically will be small. This log is very important and should be stored on a
reliable disk.
7.6.3.3.2 filesys.dat File
The filesystem configuration file, filesys.dat, is a text file that defines each aggregate and fileset
HDM manages. If HDM receives an event related to an aggregate or fileset not listed in the file, the
event will be aborted and the end user will receive an error. The file must be located in the same
directory as config.dat, typically /var/hpss/hdm/hdm<id>.
This file is maintained by HDM and should not need to be edited by an administrator. When HDM
modifies the file, a copy of the original file is saved using a name like filesys.YYMMDDhhmmss,
where YYMMDDhhmmss gives the date and time that the original file was saved (not the date
when the original file was first created.) If many changes are made in a short period of time, HDM
will not save a copy of each file, but rather will save the most recent file in filesys.bak, overwriting
the previous backups in the process. For example, if the system administrator creates a large
number of filesets at 10:00 AM on 4/1/99, when the operation is complete, three files will be
created: a file named filesys.990401100000 containing a copy of the filesys.dat that was in effect
before the new filesets were created; filesys.bak describing all but the last fileset; and filesys.dat
describing all of the filesets.
When HDM is first started, filesys.dat must be present. It is not possible to start HDM if filesys.dat
is empty or does not have the right format. To make a suitable file for starting HDM the first time,
use a text editor to create a file whose first and last lines are identical and contain the string "# HDM
filesys.dat version 1". Alternatively, create the file by copying a template file using
commands such as these:
cd /opt/hpss/config/templates
cp hdm_filesys.dat.template /var/hpss/hdm/hdm<id>/filesys.dat
where /var/hpss/hdm/hdm<id> is the directory where filesys.dat is to beplaced.
Although HDM is responsible for maintaining filesys.dat, it may occasionally be necessary for the
administrator to edit the file manually to correct problems. This section describes the format of the
file.
It is not safe to edit the file any time XDSM managed filesets or aggregates are being created or
deleted. Once the file has been edited, HDM must be restarted for the changes to take effect.
Remember, until HDM is restarted, it can overwrite any changes.
Comments may appear in this file, but they will not be preserved when HDM updates the file.
Comments begin with a '#' character and continue to the end of the line. HDM requires that the first
and last lines in the file contain the comment "# HDM filesys.dat version 1". If these lines
are absent or incorrect, HDM assumes the file is corrupt; so be careful not to alter these lines. With
the exception of these two lines, HDM ignores comments.