PLY_HSM HSME01022 Hierarchical Storage Mgmt ECO Summary
TITLE: PLY_HSM HSME01022 Hierarchical Storage Mgmt ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Compaq Computer Corporation 1999. All rights reserved.
Modification Date: 17-JUN-1999
Modification Type: New Kit
PRODUCT: Hierarchical Storage Management V2.2 for OpenVMS
OP/SYS: OpenVMS VAX V6.2 - V7.2
OpenVMS Alpha V6.2- V7.2
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: HSME01022
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 151650 Blocks
HSME01022.A 1332 Blocks
HSME01022.B 10278 Blocks
HSME01022.C 16002 Blocks
HSME01022.D 16074 Blocks
HSME01022.E 16020 Blocks
MDMSC029.A 810 Blocks
MDMSC029.B 6624 Blocks
MDMSC029.C 14382 Blocks
MDMSC029.D 10098 Blocks
MDMSC029.E 14382 Blocks
MDMSCLIENTC029.A 774 Blocks
MDMSCLIENTC029.B 6354 Blocks
MDMSCLIENTC029.C 14382 Blocks
MDMSCLIENTC029.D 9756 Blocks
MDMSCLIENTC029.E 14382 Blocks
Kit Applies To: Hierarchical Storage Management V2.2 for
OpenVMS VAX V6.2-V7.2 and Alpha V6.2-V7.2
System/Cluster Reboot Necessary: Unknown
Rolling Re-boot Supported: Information Not Available
Installation Rating: INSTALL_UNKNOWN
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for Hierarchical Storage Management V2.2 on
OpenVMS Vax and Alpha V6.2 through V7.2. This kit addresses the
following problems:
HSME01022 contains fixes to the following problems:
o Shelf Handler Reports File Fault
Problem_Statement
If a process with a null process name opens a file,
the shelf handler converts the get_info request to a
file fault. This problem was reported to occur when the
DFO(defragger)'s pre and post-processing file runs as an
unnamed sub-process.
o Repeated load/unload problem with REPACK
Problem_Statement
If shared devices were used while repacking a particular
archive class, it would result in continuous load and
unload of the volume to the drive (thrashing). HSM would
scan for all the configured devices and then dismounted,
deallocated and unloaded the drives that were not used for
the last 2 minutes.
Solution
As this lapse of 2 minutes is very short for shared
devices the timeout period is now increased to 5 minutes
in HSME01022.
A typical situation is when one of two configured drives
- needed for continuing a repack operation, but one "timed
out" and unloaded before the other loaded or vice versa.
o Fix for the MBXFULL problem with REPACK
Problem_Statement
When the shelf handler is busy with many requests, the
repack operation can fail with MBXFULL errors.
Solution
This situation is improved in the HSME01022. The repack
process retries if it hits any MBXFULL error. Also, it
displays an OPCOM message. The repack operation is retried
every 5 seconds, till a maximum of 30 minutes.
o Timestamp with BACKUP Error Messages
Solution
Timestamp is appended to BACKUP error messages to help
in troubleshooting problems. These error messages with
timestamp are in the HSM$SHELF_HANDLER.LOG file.
o Check for Deallocation of Tape Volumes
Problem_Statement
In HSM 2.2 the REPACK process would not perform a check if
Volumes can be deallocated in case of a repack failure.
Solution
HSME01022 performs the required check and displays the
following Opcom message and prints it in the REPACK listing
file:
"Please Verify if Volume xxxx can be deallocated"
HSME01022 does not deallocate the tapes as that has to
be done manually after verifying that there are no more
catalog references for the particular volumes.
o Unpreshelve does not Remove Catalog References
Problem_Statement
The UNPRESHELVE command would not remove catalog entries
thus resulting in an unwieldy catalog and lengthy searches.
Solution
If shelf attribute SAVE_TIME is set to NONE the UNPRESHELVE
command deletes these catalog entries.
o Additional Information with Backup Error
Solution
In case of NOTANSI and LABELERR errors, there is a
possibility that the error is caused because the ANSI
10,000 file limit per volume is reached. The message
"10,000 file limit possibly reached" now appears with the
NOTANSI and LABELERR reports.
o HSM overwrites ACE during reshelve operation
Problem_Statement
It was found that when HSM reshelved to different set of
archive classes, the existing entries were overwritten.
o The V2.2 Workaround for preclusion of Fault_ON_OPEN feature
re-implemented:
Problem_Statement
HSM V2.2 was modified to improve performance of FILE_INFO
requests (typically from Backup). The change removed the
Fault Info request from the normal request processing
logic.
Solution
As this affected the NFS customers, who depend upon the
Fault on open behaviour, the workaround implemented in V2.2
was, to define a system logical as:
$ define/system HSM$SHP_NO_FAST_INFO "TRUE"
This would disable the Fault Info feature, and re-enable
the old FOO behavior. This logical must be defined on any
node upon which HSM$SHP_FAULT_ON_OPEN is also defined. In
HSME01022 the modification is re-implemented, to permit
FAULT_ON_OPEN behavior to take precedence, the work around
is no more required.
o Mount Failure Without Error Message
Problem_Statement
In HSM 2.2, the mount subprocess failed repeatedly on Alpha
without reporting any error message.
Solution
This problem is fixed so that user gets an error message if
any, during the spawning of the mount process.
o Missed IRP fields and OVMS V7.2 Support
Problem_Statement
OVMS V7.2 Raven testing revealed that manipulation of IRP
fields by HSDRIVER broke when new ancillary fields were
added. These new fields were missed by HSDRIVER, which
subsequently caused processes to break.
Solution
HSDRIVER is now modified to fix this problem.
o Maximum Saveset Size
Problem_Statement
More than one customer requested to be allowed to specify
the maximum HSM saveset size.
Solution
This feature is implemented as the attribute SAVESET_SIZE
for Archive class, to match the associated media type
properties. In HSME01022 the default (and minimum) value
is 10MB corresponding to the fixed value in HSM 2.2. There
is no preset maximum value. Desired saveset sizes can be
specified at the command line, or the unlimited saveset
size gets set when a zero value is specified.
Example
the following command specifies a saveset size of 20MB:
SMU SET ARCHIVE/SAVESET_SIZE=20
o REPACK Memory Leak
Problem_Statement
REPACK was observed to be consuming large page file quota.
In case of large systems - that involved numerous files,
this resulted in the 'insufficient memory' error which
inturn aborted the process.
Solution
Found to be due to a memory leak in the REPACK process,
this problem is fixed in this release.
o HSM$BACKUP sometimes overwrote a valid saveset
Problem_Statement
There used to be a possibility of HSM$BACKUP overwriting
a valid saveset at end-of-tape, whenever there was an
unexpected error during BACKUP.
o Improved Tape Repack in HSME01022.
Solution
The following new qualifiers have been added to the SMU
REPACK command in HSME01022:
o /REPORT
The /REPORT option is added to SMU REPACK which, if
specified, will only perform the analysis phase of
a repack, but not actual repacking. This feature
will allow the system manager to analyze repacking
requirements/benefits, select the most useful threshold
values, and schedule repacks at convenient times with
a good estimate of how long the repack will take. If
used with the /SAVE option, the resultant candidates
file could be used in a subsequent repack if the
system manager wants the entire repack, as analyzed,
to proceed. For Example:
$ SMU REPACK 11/VOLUME=AQD527 -
/LIST=AQD527_REPORT.LIS/REPORT
o /SAVE
Normally, repack deletes the candidates file when it
completes (normally, on error, or on /CANCEL). With a
/SAVE qualifier, the candidates file would be retained,
and a subsequent repack could continue the repack from
where it left off with a REPACK/RESTART. In addition,
the candidates file could be retained from a REPACK
/REPORT/SAVE command, which performs just the analysis
phase, then the data moving phase could be initiated by
a REPACK/RESTART. For Example:
$ SMU REPACK 11/VOLUME=AQD527 -
/LIST=AQD527_REPORT.LIS/REPORT/SAVE
o /RESTART
The /RESTART qualifier would utilize the current
candidates file and restart the repack from where it
left off, without a further analysis or repacking files
/volumes that had already been repacked. For Example:
$ SMU REPACK 11/VOLUME=AQD527 -
/LIST=AQD527_REPORT.LIS/RESTART
o REPACK Default Listing File
The /LIST qualifier is defaulted for the SMU REPACK
command. The default list file is HSM$LOG:HSM$REPACK.LIS
o REPACK Status Messages
The repack feature has been improved to give status
messages, while the repack operation is in progress. The
repack process issues operator messages to indicate the
start and completion of the operation on each volume in the
volume set. Operator reply should be enabled for the TAPES
or CENTRAL opcom classes, to take advantage of this.
$ REPLY/ENABLE=(TAPES,CENTRAL)
o Improved List File
The repack listing file has been made to contain more
detailed information about the repack process.
o Files in Deep-rooted Directories
HSME01022 now supports shelving and unshelving of files
in deep-rooted directories. The hierarchy can be upto a
maximum of 16 levels.
INSTALLATION NOTES:
Enter the following command from the system prompt to install HSME01022.
$ @SYS$UPDATE:VMSINSTAL HSME01022 device OPTIONS N
For specific instructions and examples of the Installation Notes chapter 3
of the Release Notes. and the Hierarchical Storage Management for OpenVMS
Installation and Configuration Guide Version 2.2.
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
hsme01022.README
.CHKSUM
hsme01022.a-dcx_axpexe
hsme01022.a-dcx_vaxexe
hsme01022.b-dcx_axpexe
hsme01022.b-dcx_vaxexe
hsme01022.c-dcx_axpexe
hsme01022.c-dcx_vaxexe
hsme01022.d-dcx_axpexe
hsme01022.d-dcx_vaxexe
hsme01022.e-dcx_axpexe
hsme01022.e-dcx_vaxexe
mdmsc029.a-dcx_axpexe
mdmsc029.a-dcx_vaxexe
mdmsc029.b-dcx_axpexe
mdmsc029.b-dcx_vaxexe
mdmsc029.c-dcx_axpexe
mdmsc029.c-dcx_vaxexe
mdmsc029.d-dcx_axpexe
mdmsc029.d-dcx_vaxexe
mdmsc029.e-dcx_axpexe
mdmsc029.e-dcx_vaxexe
mdmsclientc029.a-dcx_axpexe
mdmsclientc029.a-dcx_vaxexe
mdmsclientc029.b-dcx_axpexe
mdmsclientc029.b-dcx_vaxexe
mdmsclientc029.c-dcx_axpexe
mdmsclientc029.c-dcx_vaxexe
mdmsclientc029.d-dcx_axpexe
mdmsclientc029.d-dcx_vaxexe
mdmsclientc029.e-dcx_axpexe
mdmsclientc029.e-dcx_vaxexe
mdmsclientc029.CVRLET_TXT
|
