Patch Name: PHSS_17475 Patch Description: s700_800 10.20 OV OST2.X cumulative A.02.20 patch Creation Date: 99/04/19 Post Date: 99/05/12 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: HP OpenView OmniStorage A.02.20.00 Filesets: OMS.f_server OMS.f_client OMS.common OMS.f_gui OMS.f_fs OMS.manpages OMS.documents Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_17475 Symptoms: PHSS_17475: 1 Rebuilding magnetic cache from nearline volumes gene- rates massiv error messages (CHSM710008/CHSM710008) in dedlog file. (ddts: NSMex01055) 2 zb: data corruption w/ part resident files (ddts: JOSqa00295) 3 CHSM410281 errors in qrlog and outward migration fails (ddts: NSMex01740) 4 the ager starts stops in loop (ddts: NSMex01757, JOSqa00253) 5 AGEWEIGHT and SIZEWEIGHT confuses customers (ddts: NSMex01991) 6 VBFS API error code (219) / [CHSM160046] (ddts: NSMex01384, NSMex01768, NSMbb22049 SR #1653279828) 7 Write a par archive to MO volume exits with error "Can't erase the remaining media start = ..." (ddts: JOSqa00302) 8 [CHSM230183] Out of memory in function jcom_alloc() need 416 (ddts: NSMex01821) 9 restore_vbfs has problems to restore "spaced" file names (ddts: NSMex01824) 10 fsck -y could lead to data loss and cause panics at startup (ddts: NSMex01899, JOSqa00305, JOSqa00292, NSMbb19445 SR #1653257691) 11 Application hangs, if needed data are on secondary media and this volume was manually ejected (not using the OMS command exportp). (ddts: NSMex01772) 12 formatp on blank MO fails sometimes if sidf is specified (ddts: NSMex00814) 13 [CHSM230562] jmd: Media set to error state; volume = c00073 (ddts: NSMex01992, NSMex01191) 14 Active mode ager continously submitted migout requests not stopping at ALWM (ddts: NSMex01975) 15 volsets not created if TMPDIR environment variable is set (ddts: NSMex01969) 16 Rebuild fails to rebuild (ddts: NSMex00837, NSMex00371, NSMex01141 SR #5003409540) 17 listp -a could be better, command scrolls over screen with CR's (ddts: NSMex01057) PHSS_15818: 1 Migout-request is created and finished, but the file remains on the MFS. qrlog shows ERROR [CHSM410337]. (ddts: NSMex01536) 2 Zb does not accept "q" to quit if one tape is completely filled with data. (ddts: NSMbb15681, SR: 1653225896) 3 Shutdown hangs after installing PHSS_15452/PHSS_14839 (ddts: JOSqa00248) 4 The Unmount entry in mig-log file shows a wrong platter. (ddts: JOSqa00092) 5 If an application wants to read data and these data are on secondary media which state is not INTERNAL, then the application hangs. (ddts: NSMbb14671, SR: 5003383265) 6 Qr must be restarted after import media. (xddts: NSMex00928) 7 Bkup_vbfs and restore_vbfs hang if more than one tape is necessary and user wants to abort backup / restore pro- cedure with 'q' or 'Q'. (xddts: NSMbb15742) 8 Bkup_vbfs picks up all platters of a MFS with state INTERNAL or EXPORTABLE. (ddts: NSMbb10845, NSMex00576) 9 Restore_vbfs restores files during rebuild which have been deleted before. (ddts: NSMbb15885) 10 Qr core dump on qqr with long file names. (xddts: JOSqa00124) 11 IOS: unable to read files with strlen(path) > 255 (xddts: JOSqa00243) 12 Migration to WORM does not complete. Io_server consuming large amounts of CPU time doing nothing. (xddts: NSMex01476) 13 Tape errors caused by DLT drives. (xddts: NSMex01330) PHSS_15452: 1 After running cleanup freshly formatted platters in the freepool are not completely free anymore. (ddts: NSMex00360) 2 Customer request for a common device type. (ddts: NSMex00485) 3 Sync_media fails to set side A or B in state mainte- nance. (ddts: NSMex00689) 4 Potential data loss because of dropped locks on migins caused by writes. (ddts: NSMex00750) 5 OMS client with two lan cards cannot connect to OMS server. (ddts: NSMex00872) 6 Migout -R /dir/* migrates only a part of the directory content. (ddts: NSMex00879) 7 CAPS file densities not available for DLT7000. (ddts: NSMex00948) 8 Zmrestore has a memory leak. (ddts: NSMex00968) 9 OmniBackII path used in OmniStorage GUI refers to 9.x path. (ddts: NSMex01022) 10 Format media with imbedded "mediainit" fails. (ddts: NSMex01105) 11 Reading data from secondary media fails with error "early end encountered". (ddts: NSMex01149) 12 Active ager runs for ever, not moving bulked aged files. (ddts: NSMex01168) 13 OMS integration with OBII has poor performance. (ddts: NSMex01187) 14 Ded does not allow mounting of largefiles filesystem. (ddts: NSMex01252) 15 Sync_media fails processing large numbers of files. (ddts: NSMex01265) 16 Active ager will migrate all bulk aged files. (ddts: NSMex01274) 17 Recovering single files from a former backup of a migrating file system fails. (ddts: NSMbb16955) 18 Xhsmmgr fails formatting media with duplicate id for syncing. (ddts: NSMbb17328) 19 Bkup_vbfs cannot access error -/status files on remote client host. (ddts: JOSqa00206) 20 Qr: slows down with large numbers of migin requests. Ager waits for all requests to complete, not just its own. (ddts: JOSqa00211) 21 LMOpenSlotVS fails if jukeboxes are numbered 1 and 2, sync_media fails. (ddts: JOSqa00232) 22 OMS needs to be year 2000 compliant (ddts: JOSqa00234) 23 Restore_vol using multiple drives causes a system panic (ddts: NSMex01226) 24 Sync_media fails with WORM media. (ddts: NSMex00776, NSMex00871, NSMex01127, NSMex01133, NSMex01353) 25 Chgstate does not accept more than 50 volumes (ddts: JOSqa00230) 26 WORM media not recognized on series 700 machine (ddts: JOSqa00228) 27 File system 100% full, cannot be aged because no space left (ddts: JOSqa00155) 28 Bulk mode ager memory usage increases (ddts: NSMex01195) 29 Qr and jmd slow with large numbers of truncates, migouts (more volumes than drives). (ddts: JOSqa00235) PHSS_13437: 1 Ager/migout -R not moving all data from magnetic to storage media (xddts: NSMbb16620) 2 listp -B not consistent with listp -S (xddts: NSMbb15784) 3 Some aliases are not resolved by listp or loadp (xddts: JOSqa00190) 4 jmdrestore fails - external bar-code is stored in alias (xddts: JOSqa00129) 5 qr aborts migin request because size of request is too large (xddts: JOSqa00186) 6 Wording within error messages / documentation / log files inconsistant (xddts: NSMbb14815) 7 STK_SILO JMD database and ACSLS gets out of sync (xddts: JOSqa00174) 8 Panic: aging large numbers of files (xddts: JOSqa00178) 9 sync_media does not work correctly for MO/UFS media (xddts: NSMbb16925) 10 formatp GUI tape capacity list needs entries for STK SILO tapes (xddts: JOSqa00072) 11 Qr: migin : early end encounted (xddts: JOSqa00169) 12 STK SILO - installchanger / removechanger does not show ACSLS drive path (xddts: JOSqa00194) 13 new options listp -a and jmdrestore -a (xddts: JOSqa00195) 14 poor performance with duplicate read requests from tape (xddts: NSMex00836) 15 invalid start/size on qr requests can put media in error state (xddts: JOSqa00152) 16 wrong displayed usage in case of misused zmdump/ zmrestore (xddts: NSMbb16966) 17 problems with zmdump in production environment (xddts: NSMbb16926, NSMex00575) 18 after migin -m, most hsm utilities fail on the file (xddts: JOSqa00182) 19 incorrect statement in man page for zb (xddts: NSMex00762) 20 Capacity of Tape is very small when writing to EOT (xddts: JOSqa00185) PHSS_12882: 1 migins from MO are slow (xddts: NSMex00789, JOSqa00168) 2 A4619113 - restore_vbfs coredump or hangs (xddts: NSMex00453, NSMex00731) 3 Migsever fails with bus error & core dump (xddts: NSMex00731, JOSqa00166) 4 jmdrestore fails if media database does not exist (xddts: NSMex00691) 5 removechanger does not update ./data/jmd, listp is inconsistent (xddts: NSMbb15240) 6 File System GUI is accepting ANY value for the maximum file size. (xddts: NSMbb15876) 7 Data on re-imported ONSITE media not accessible (xddts: NSMbb15536) 8 poor performance because of DM_NO_TOKEN usage (xddts: JOSqa00173) 9 hsm_admin -I accepts wrong fsid -- no error message (xddts: JOSqa00075) 10 Qr: truncates are extremely slow (xddts: JOSqa00131) 11 xhsmmonitor shows outstanding requests, qqr does not (xddts: NSMbb14801) 12 qr dumped core after truncate and forward requests (xddts: JOSqa00170) Defect Description: PHSS_17475: 1 Scenario for requesting, testing and use a free inode includes creating a tmp-file. Because this tmp-file has no extended file attributes, removing the file causes the ded to write an error message (wrong attribute ver- sion). Level of these messages was changed from error to note, because it is not really an error message. Resolution: This solution prevents massiv error messages during the rebuild command in /var/opt/omnistorage/log/dedlog. 2 Backing up a partial resident file having its first blocks in secondary media, followed by some blocks on magnetic cache, and closed by further blocks on secondary media causes data corruption. This is caused by read_media() by seeking inside the data image buffer only once, when the data image buffer will be created. The position inside the buffer will not be updated by further calls to read_media(). Resolution: Seek inside data image in read_media() function. 3 The qr core dumps on SIGSEGV cause it grew larger than MAXDSIZE due to about 25.000 requests in its request queue. The ager submits an unlimited number of requests to the qr after a timeout of 24 hours even if the qr did not allow it to do that. jmd list handling requires too many comparisons for volume set iteration. Resolution: Decrease size of communication data and optimize search for volume to migrate to. 4 Due to possible inconsistent configuration settings of AGER_HWM, BLOCK_CREATES_WM and BLOCK_CREATES_REMAINING_BLOCKS the ded was blocking file creation as long as these inconsistencies were corrected. The following inconsistent configurations could occur: a) BLOCK_CREATES_REMAINING_BLOCKS > total file system blocks In that case no file system object could be created, even the file system was newly created. b) (100 - BLOCK_CREATES_REMAINING_BLOCKS in percent) < AGER_HWM && used space < AGER_HWM In that case the ded blocked further file creation and forced the ager to start in active mode, but the ager didn't find migration candidates, because the AGER_HWM was not reached. Resolution: Correct watermark inconsistencies during runtime. 5 agerlog shows error messages like ager ERROR ( 2825): 01/13/1999 19:07:02 [CHSM310057] The value for the AGEWEIGHT parameter was invalid; 1 will be used instead. ager ERROR ( 2825): 01/13/1999 19:07:02 [CHSM310058] The value for the SIZEWEIGHT parameter was invalid; 0 will be used instead. Resolution: The if condition for checking the return value of ReadAgerConfigWithFallback() was modified to verify against == 1 instead of != 0. 6 When running a backup based on 'zb' or BRAPI (OB-OMS-Integration) the 'io_server' mounts an hpufs formatted secondary media under "/tmp". This is a potential safeness problem for all data that reside on secondary media. The behaviour was changed to either use the defined JMD_MNTDIR parameter value from /etc/opt/omnistorage/jmcfg or if not defined "/jmd_mnt" as the default. Resolution: The behaviour was changed to either use the defined JMD_MNTDIR parameter value from /etc/opt/omnistorage/jmcfg or if not defined "/jmd_mnt" as the default. 7 Par writes all former read and archived blocks from MO to a destination MO. At the end of writing all remai- ning blocks at the destination will be erased. But if there are no remaining blocks no block has to be erased. Error in the compare instruction of the current block and the total number of blocks causes the problem. Although par exited with error the MO is usable. But par is used by restore_vbfs and this command aborts if par exits with error. Resolution: If there are no remaining free blocks after restoring a MO (number of blocks in the par archive is equal to the number of blocks on MO) then no blocks have to be erased. 8 The jmd is not reporting the errno set by failing malloc(). Resolution: The errno is reported back to the log message. 9 In the case you use files with special characters in their names it is necessary to create an include_ file instead of typing a filespec for selective file restoring. Resolution: A necessary addition under option -f of the "restore_vbfs" man page regarding special characters in a file name has been included. 10 Forcing a file system check on secondary media by the jmd due to mount failures calls 'fsck' with the -y option, which causes an automatically repaired file system, but potential data loss without any possibility to manually intervent. Although 'fsck' repaired the file system and set the clean flag of the superblock to state FS_OK, or FS_CLEAN, a following mount paniced the system. Resolution: Changing the fsck use from option -y to -P instead will have the following effects: - clear indication on file systems which cannot be repaired automatically without potential data loss. Corresponding media will be set to state 'Error'. - no further mount operations will be performed on these media. 11 If OMS detected an empty slot, although there should be a volume in this slot, then the mount request was requeued until the media was available. Now OMS sets the missing volume to state ONSITE, the mount request will fail and the application will get an error code (errno 2). Furthermore there are error mes- sages in the qr and jmd log file and an email to root of the system will be send. Part of SSPOMS_18 (OMS A.02.10). Resolution: Data access to missing secondary media causes an error message to the calling application and set the system errno to 2. 12 A SIDF formatp on MO failes if the MO is a blank one. The formatp command tries to read the label (which consists of '000...' and interpretes this as file system type. Resolution: Prevent the formatp command from erronously interpreting blank labels. 13 If a media was set to state 'Error' due to access problems the corresponding ERROR log message only shows the volume ID, but no drive number. The drive number is helpful when searching the root cause of the problem, i.e. is either the media itself or the drive causing the problem. Resolution: The drive number was added to the log message. 14 The ager running in active mode did not stop to submit migout requests at the AGER_ALWM. Additionally the agerlog showed an error message like: ager WARNING ( 2329): 01/08/1999 18:46:55 [CHSM310090] The active mode ager was unable to move the file system /test down to the ALWM (76%). The current level is 5%. This was caused by a wrong calculation due to a data range overflow. Resolution: Use 64bit integer data types for calculation. 15 Defining TMPDIR env variable might cause the jmd to fail when reading the volume set database at startup. The jmd renames the orginal volsets file into a temporary name. The temporary file name is created using the tempnam() HP-UX library routine. Unlike tempnam(3S) man page this routine always uses TMPDIR env variable if it's defined and has a valid value. If the temporary name points to a volume different from /var renaming the original volsets file into a temporary name fails and all volumeset information is missing. Resolution: The tmpnam() library routine is used instead. 16 o rebuild dumps core on 21st volume o rebuild leaks memory o rebuild output doesn't reflect progress Resolution: A progress indicator was implemented and memory leaks removed. 17 'listp -a' displays alias for platters, but when there are no aliases it prints '', which is annoying. Resolution: Prevent to only print ''. PHSS_15818: 1 The problem is related to problems with some MO-device drivers to handle the verify-after-write correctly. The migout is processed properly if either the verify- after-write function is switched off or the immediate_ report function of the scsi-MO-device is turned off using the HP-UX-command scsictl. Having both parameters turned ON will lead to failing migrations. Therefore the new Omnistorage jmd parameter 'JMD_MO_WORM_SET_VERIFY_WRITE' is set to OFF in the jmcfg configuration file. 2 zb does not except "q" to respond on the request to either insert a new tape, or to provide a new device path, or to quit the operation. This was caused by a mistype in the source code. The read user input was compared to '1' instead of 'q'. 3 The system hangs during shutdown after all user processes were killed when unmounting file systems of type vxfs, because the system generates a DM_EVENT_PREUNMOUNT event while no OmniStorage event daemon process responds to that event. A modification of /usr/sbin/killall script which excludes the ded from being killed during shutdown solves the problem. The OmniStorage event daemon stays alive and responds to generated events. The original version of the script will be saved as /usr/sbin/killall.save. The system panics after all file systems were successfully unmounted, or during all user processes were killed. This was caused by killing a kdm_user_thread process, which holds a DMAPI token which was never responded to. 4 Printf instruction for log writing gave false value of an array. 5 If a mount request for a secondary media cannot be per- formed because the media is not in state INTERNAL, then the causal migin request was requeued until the media can be mounted. Only a mail to the user root and a log message for the qr were given. Now the qr returns with an error code to the applica- tion. Mail to root and qr log message give an explana- tion about the error code. Error code errno is 2. 6 Platter status check routine is now the same at qr starting time and before submitting migin/migout/trun- cation requests. 7 If end of tape is reached then omnistorage ejects the tape and asks for the next. When then 'q' or 'Q' for 'quit' was entered, Omnistorage tried to close the write/read process, but the tape was already ejected. The tape had to be inserted again. Now the tape handling has been changed. Because a close operation depends on the decision (quit or continue) the user will be asked at first for "quit" or "continue" and then for the next tape. 8 Only platters with state Internal should be backed up. If there are platters belonging to the MFS and have a state which is not INTERNAL, then the user will be asked for continueing or to quit at the beginning of the backup session. With option "-y" a backup can be forced if there are media with a state different to INTERNAL. 9 Under certain circumstances this is a normal behaviour. Therefore the restore_vbfs man page was completed by a caution note. 10 Qr could have memory corruption creating the response to a qqr request. 11 Io_server was saving incorrect string length information for pathnames longer than 255 characters (relative to the mountpoint). And would cause an error when attemp- ting to read the data by the qr. 12 Kernel parameter maxfiles_lim was larger than expected, and used incorrectly, causing the io_server, and clients to overwrite fixed size buffers used in select(). 13 DLT tapes sometimes have invalid file mark directories, and goto end of data will sometimes fail. Added valida- tion and retries. Add search performance improvements to allow seeking directly to large images (by writing more filemarks). Two parameters are added to the iocfg for tape: IOS_TAPE_MAX_FILES_PER_FILESET 1023 IOS_TAPE_MAX_DATA_PER_FILESET 20480 PHSS_15452: 1 During cleanup, the ODM filesystem structure is written to an empty platter. This leads to not recognizing the media being available for the freepool anymore. 2 Add a common device type "DLT" as a backup device for bkup_vbfs for using DLT4000/DLT7000. 3 Sync_media was setting each volume (both sides of a platter) back to internal when syncing was completed for that volume. The other side of the platter still needed to be synced. 4 Sometimes write requests cause inward-migration, the qr was not verifying that the data was still resident be- fore setting dirty indications. 5 All OMS client hosts are known to the OMS server by their entry in /etc/opt/omnistorage/jhosts. If the client's host name is followed by an IP-address (of the second lan card), then exporting of file systems of secondary media from the server to the client will be done via the special IP-address otherwise via the default IP-address (first lan card). OMS server exports file systems of secondary media and client trys to mount it via the default IP-address (first lan-card). 6 Under certain circumstances a false tree was passed for generating migout requests so that the request was dropped. Decision tree was corrected. 7 Jmd device capability database completed with infor- mation for DLT 7000. 8 If zmrestore restores inode information and extended attributes of a file that was migrated out at the time the backup archive was created, 100 byte of allocated memory remain unfreed. If zmrestore restores about 600.000 files the amount of unfreed memory hits the standard MAXDSIZE ( 64MB ) and the system hangs. Part of SSPOMS_1, SSPOMS_3 9 Starting OmniBack from the OmniStorage GUI is failing. When the button is clicked, you get the message: "/usr/omni/bin/xomni: No such file or directory" 10 We substituted the scsi-format_mo by introducing the UNIX-command 'mediainit'. 11 - Creating a new chunk sometimes fails to properly set a dirty flag for the newly created chunk. A new chunk should always be marked dirty. - A new chunk should not have the same mediaid, and fileid as another chunk. - Added some verification to ensure that a image on MO/UFS is not 'grown' by using lseek. lseek() must be used to skip over valid data. - Disabled interrupting because of volume timeouts. This makes migration to MO/UFS media consistent with WORM or tape. The errors where not caused by the interrupts, but appeared more often because of the interrupts. - qr incorrectly causes an error on migin when its volume time slice has expired. The error status on unlock masks the timeout status, and causes the early end message. This fix is only for 'Early End encoun- tered' preceeded by a 'pv_unlock failed' message. 12 Ager was incorrectly locking an invalid range of a file. Preventing the file from being freed from magnetic. 13 Io_server was using 8K block sizes for MO/UFS media. Increased to 32K blocks for default. Allow setting buffer sizes up to 1 meg. ODM endpoint was incorrectly handling read errors. New parameters were added to /etc/opt/omnistorage/brapicfg. The defaults are IOS_WAIT_FOR_CLOSE true IOS_BUFFER_SIZE 32768 14 The Omnistorage DMAPI event daemon ded does not allow to mount file systems which have large file support enabled, even if they are non-Migrating file systems. The ded receives MOUNT events for file systems of type vxfs, but should only prevent to mount Migrating File Systems with the "largefiles" option set. 15 For every query to the jmd to determine the other side of a volume, a LMServer handle was opened, and not closed. After a number of volumes, the process had too many file descriptors open and was unable to communicate to the jmd. 16 Active mode ager counted number of blocks freed from magnetic in 8K blocks. It should have been counting using 1K blocks. Falls counting causes the ager to migrate out more files as needed. 17 Problem was caused by different errors: - Missing destination directory creation for file recovering. - Incorrect directory creation of temp directories. - Incorrect media state of scratch media during file recovering. 18 Xhsmmgr produced an error message saying format failed because id is already in use. The format did succeed as requested. The lmapi library was inappropriately assigning an error if the id returned after format was not the id requested. Because duplicate volume ids are necessary for syncing now a note will be given. Producing an error message is unsuitable. 19 Creation of temp directories on remote clients for bkup_vbfs was incorrect. 20 The parent qr is checking each migin request if it can be responded to (sometimes a client read 'catches up' to readahead and generates a migin event). It does this each time through its main event loop. It checks even migin requests that are generated by 'migin', or qr child attempting to migout part resident chunks. 21 Jmd code was assuming boxes were numbered consecutively starting with 0. If box numbering started with 1, then box 0 was missing and programs had to fail. 22 OmniStorage logging functions write 2 digit year numbers when writing log messages. The OmniStorage ITO Integration product collects water- mark statistic data by calling the omstrmXC monitor template once every hour. Each line of the collected data contains the current date. The year number is written as a 2 digit number. 23 Restore_vol calls the OmniStorage rebuild command. During the rebuild step inodes will be requested. If there was parallel rebuilds for the same migrating file system, it could occur, that an inode was assigned twice, what caused a system panic. Now multiple restore_vol processes are possible. The first process which calls rebuild causes the other restore_vol to wait until the first one is ready with rebuild. 24 - The io_server was failing to read the data portion of zero-length files (which are not normally migrated). - The io_server was returning a incorrect image id on gotoLastImage() if end-of-media was encountered during write. - The io_server was writing an incorrect File Set Identifier when repairing an incomplete write caused by an early termination of a previous io_server. - The io_server also caused sync_media to fail on the copy of last image, because the cscEnd was encountered by the reader, and the writer attempted to close the short image. - Omnistorage was turning off Verify Writes. Added variables to iocfg to set scsi options for verify writes, write without erase, and exclusive. Correct C cast error. - Error on close of fileset was forgotten. Fix error handling. Part of SSPOMS_2, SSPOMS_6 25 Chgstate had a limit of 50 for argc (about 48 volumes), more arguments produce an Usage Error message. Now number of arguments is limited by system parameters (command line, buffer size etc.). 26 A switch case contains two break statements, and mo_check_mediatype() is not reached. 27 File could be created, written, and migrated in until the filesystem has 0 blocks free. The ded now checks water marks (instead of the qr) and will block creation of file system objects if the file system is above BLOCK_CREATES_WM=98. If file system is filled until 98 %, then the active ager starts to migrate out files to secondary media. Free 2 % can be used to write extended attributes of files, which are to be migrated out. A tunable nospace event generation presumes latest available vxfs/dmapi patches which add two new kernel parameters, vx_nwriters, and vx_enospace_factor. They will be set to defaults by the /sbin/init.d/OMSclient script to make them persistent across reboots. Therefore installing patch PHKL_16750/16751 is required. 28 Bulk mode ager had a memory leak. Part of SSPOMS_1, SSPOMS_3, SSPOMS_4 29 Qr was requesting information from jmd for every request even if drives where unavailable. PHSS_13437: 1 If qr handles several migout requests for more than one Migrating File System, then sometimes change from shared_file_handle to exclusive_file_handle (necessary for file locking) failed. Migration of the file failed with error "file busy". 2 listp -B shows the wrong number of blocks for tape sidf media. The capacity for tape sidf is set after format time. Now the number of blocks is set after format time too for this media. listp shows a warning now, when -B and -f option are used together. 3 Hexadecimal aliases are not resolved by the following jmd utils: chgowner, chgstate, copyp, exportp, formatp, fsckp, listp, loadp, mountp, rmplat, setgrp, unloadp, unmountp. They are needed e.g. for barcodes of tapes stored in alias names. 4 For some storage libraries the external barcode is stored in the volume name. It cannot be deleted or changed. For these cases a new option " -a " for jmdrestore is created. If the option -a is set, the volume names are not recovered. 5 Some part of the HSM system adjusts 0 length migin request to the size of file, should adjust it to size of chunk or a file is truncated to a smaller size since the request was submitted. qr was insensitive, and would fail the request. 6 In the case of failing to set extended attributes for a file that gets restored by zb/zmrestore, the command logs an error message which uses wrong terms, "migrate priority" instead of "residence priority" and "migrate- ahead strategy" instead of "read-ahead strategy". 7 If a media is in drive with reference count 1 and the jmd is shutdown then JMD database and ACSLS database get out of sync. Now an inventory is performed for this media - when jmd starts. 8 Aging a large number of files and other stress operations where qr and/or ager were involved could result in the situation that two processes (qr parent and child or ager) would try to access one file using the same (session, token), the pv_current_session/token. (This is heavily used since the migin performance changes.) Change: Every process which uses pvlib has to open its own pv_session now. 9 After syncing, original and sync copies do not show same free space. Files were not being deleted off the copy. Some messages were promoted to warning level. After removing files, sync_media did nothing. The qr was not marking media as being dirty after processing destroy events (handled as list of truncates). Also, list of truncates did not cause truncate requests. 10 New tape capacities: 3490 400MB (compressed 1.2GB), 3490E 800MB (compressed 1.8MB) are added to the list in the GUI, Format Media dialog. 11 The qr, ager, and migout may punch a hole even if the file chunk has modified data. The problem seems especially evident with bulk aged files. The region map contains a truncate/write detection beyond end of file. Sometimes regions get merged, that means the last region includes part of the file. Events were not set properly on this last region. 12 The currently installed boxes show now additionally (acs.lsm.panel.transport) for drives in removechanger and installchanger if a STK silo is installed. 13 listp did not show volume aliases. New option -a lets display the alias name (external bar-code ID's for STK Silo) in place of the Omnistorage volume ID. jmdrestore has a new -a option which does not restore the alias name field in the Omnistorage volume database where the external bar-code ID is stored for STK Silo. 14 qr opens data image before determining if data is resident and the request needs no migration. At ENOSPC, qr responds to event expecting it to be requeued. 15 For sequential media, media would sometimes end up in error state when a migout request was processed that was larger than the file is currently. 16 The man page, the command usage, displayed in the case of missuse, and the list of options which can be added to the zmdump/zmrestore command are inconsistent. 17 The default zmdump/zmrestore implementation supports 512 byte block size only, which means a poor performance when writing to tape drives. 18 If a file has been grown by writing, then a migin -m occured, truncate events are not enabled for the new region of the file. 19 zb fails to restore files from an archive to a non- Migrating File System. All files are restored, but only with a size of 0 bytes, although the zb(1) man page states: "zb works on standard (non-Migrating File System) file systems as well as on Migrating File Systems." This is not correct. On HP-UX 10.x zb supports Migrating File Systems only. 20 At end of tape , when the physical EOT was detected, the capacity (listp -S ) was very small. Migin of a file leads to "Error" state of the tape. PHSS_12882: 1 Using 8k block size for reading from MO, and writing to the file system limits access to migrated files. 2 zmrestore error message "Out of phase--get help" The zmrestore failed by reading the header information of the first element in the zmdump archive. The reason were incorrect data type changes in the binary_hdr structure. zb error message "Writing incorrect data for " This problem occured if zb backs up twice a migrated file. The problem was caused by a missing close of the IOS_DataImage object. 3 If calling the restore_vol utility the migsever execut- able failed due to a read access in the NULL page, core was dumped. It behaved that way because wrong parameters were passed to certain function calls. 4 jmdrestore fails when the media file not exists. jsyncdata was changed, mediafile is created in this case and a syncall is performed. 5 removechanger changes the jmcfg file only. Now at the beginning of jmd the volume database and the list of configured boxes are compared. All volumes for which the box is not configured are set to state "Onsite" - so they can be deleted by rmplat if the user wants it. A warning appears in jlog: WARNING (19971): 10/14/97 10:59:25 Volumes of box %d are in database but not configured - set to Onsite. 6 The accepting conditions was restricted to following MinFileSizeDefault < MinFileSize < MaxFileSize MaxFileSizeDefault=4000000 If the valid range will be overwritten, the default values from the netcfg file will be used. 7 qr is not receiving signals from jmd because signals are blocked. 8 OmniStorage creates many kdm_user_threads (usage of DM_NO_TOKEN). This can cause system to run out of memory and it takes much time (system performance). 9 If hsm_admin is called with the -I option followed by a file system Id (FSID) the command does not check if the given Id is valid. If the file system Id is wrong, hsm_admin sets it to 0x0, which causes later migration to fail. 10 Handling of large numbers of truncates is extremely slow qr child processes do not share resources. 11 Request counting in different places leads to mishand- ling of request counting. 12 Freeing memory twice after truncate and forward requests causes the qr to core dump SR: B700028456 B700028506 1653207514 1653225896 1653247734 5003383265 5003414805 5003409540 1653279828 1653257691 Patch Files: /etc/opt/omnistorage/brapicfg /opt/omnistorage/bin/add_vol /opt/omnistorage/bin/aliasp /opt/omnistorage/bin/bkup_vbfs /opt/omnistorage/bin/chgidp /opt/omnistorage/bin/chgowner /opt/omnistorage/bin/chgstate /opt/omnistorage/bin/cleanup /opt/omnistorage/bin/consolidate /opt/omnistorage/bin/convert_media /opt/omnistorage/bin/copyp /opt/omnistorage/bin/exportp /opt/omnistorage/bin/formatp /opt/omnistorage/bin/fsckp /opt/omnistorage/bin/getfsid /opt/omnistorage/bin/hsm_admin /opt/omnistorage/bin/hsm_session /opt/omnistorage/bin/importp /opt/omnistorage/bin/inventory /opt/omnistorage/bin/jmdbackup /opt/omnistorage/bin/jmdrestore /opt/omnistorage/bin/listp /opt/omnistorage/bin/loadp /opt/omnistorage/bin/migin /opt/omnistorage/bin/migmv /opt/omnistorage/bin/migout /opt/omnistorage/bin/migsever /opt/omnistorage/bin/mountp /opt/omnistorage/bin/par /opt/omnistorage/bin/qjmd /opt/omnistorage/bin/qqr /opt/omnistorage/bin/rebuild /opt/omnistorage/bin/rebuild.sh /opt/omnistorage/bin/resid /opt/omnistorage/bin/restore_file /opt/omnistorage/bin/restore_file.sh /opt/omnistorage/bin/restore_vbfs /opt/omnistorage/bin/restore_vol /opt/omnistorage/bin/rkill /opt/omnistorage/bin/rmplat /opt/omnistorage/bin/setgrp /opt/omnistorage/bin/unaliasp /opt/omnistorage/bin/unloadp /opt/omnistorage/bin/unmountp /opt/omnistorage/bin/vsadm /opt/omnistorage/bin/vsbind /opt/omnistorage/bin/vsclose /opt/omnistorage/bin/vsdbcheck /opt/omnistorage/bin/vshdr /opt/omnistorage/bin/vsopen /opt/omnistorage/bin/vsread /opt/omnistorage/bin/vswrite /opt/omnistorage/bin/wt-check /opt/omnistorage/bin/xhsm /opt/omnistorage/bin/xhsmbackup /opt/omnistorage/bin/xhsmmgr /opt/omnistorage/bin/xhsmmonitor /opt/omnistorage/bin/zb /opt/omnistorage/bin/zdf /opt/omnistorage/bin/zerrmsg /opt/omnistorage/bin/zfind /opt/omnistorage/bin/zls /opt/omnistorage/bin/zmdump /opt/omnistorage/bin/zmdump.sh /opt/omnistorage/bin/zmrestore /opt/omnistorage/bin/zmrestore.sh /opt/omnistorage/lib/errmsgs /opt/omnistorage/lib/guimsg.ehdb /opt/omnistorage/lib/libcheyhsm.sl /opt/omnistorage/lib/qrmsgs.Eng /opt/omnistorage/man/man1/ager.1 /opt/omnistorage/man/man1/listp.1 /opt/omnistorage/man/man1/rebuild.1 /opt/omnistorage/man/man1/zb.1 /opt/omnistorage/man/man1m/add_vol.1m /opt/omnistorage/man/man1m/bkup_vbfs.1m /opt/omnistorage/man/man1m/jmdrestore.1m /opt/omnistorage/man/man1m/restore_vbfs.1m /opt/omnistorage/man/man1m/restore_vol.1m /opt/omnistorage/man/man1m/sync_media.1m /opt/omnistorage/man/man1m/vsbind.1m /opt/omnistorage/man/man1m/zmdump.1m /opt/omnistorage/man/man1m/zmrestore.1m /opt/omnistorage/man/man4/brapicfg.4 /opt/omnistorage/man/man4/jhosts.4 /opt/omnistorage/man/man4/jmcfg.4 /opt/omnistorage/man/man4/netcfg.4 /opt/omnistorage/man/man4/zb.4 /opt/omnistorage/newconfig/ded.inittab /opt/omnistorage/newconfig/iocfg.proto /opt/omnistorage/newconfig/jmcaps.proto /opt/omnistorage/newconfig/jmcfg.proto.libman /opt/omnistorage/newconfig/netcfg.proto /opt/omnistorage/sbin/ager /opt/omnistorage/sbin/installchanger /opt/omnistorage/sbin/io_server /opt/omnistorage/sbin/jmd /opt/omnistorage/sbin/qr /opt/omnistorage/sbin/removechanger /opt/omnistorage/sbin/rpc.kill /opt/omnistorage/sbin/rpc.niod /opt/omnistorage/sbin/sync_media /sbin/ded /sbin/init.d/OMSclient /usr/lib/X11/app-defaults/XHsm what(1) Output: /etc/opt/omnistorage/brapicfg: None /opt/omnistorage/bin/add_vol: None /opt/omnistorage/bin/aliasp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/bkup_vbfs: None /opt/omnistorage/bin/chgidp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/chgowner: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/chgstate: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/cleanup: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/consolidate: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/convert_media: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Wed Apr 21 14:07:19 EDT 1999$ /opt/omnistorage/bin/copyp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/exportp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/formatp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/fsckp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/getfsid: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/hsm_admin: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/hsm_session: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/importp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/inventory: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/jmdbackup: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/jmdrestore: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/listp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/loadp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/migin: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/migmv: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/migout: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/migsever: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/mountp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/par: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/qjmd: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/qqr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/rebuild: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/rebuild.sh: None /opt/omnistorage/bin/resid: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/restore_file: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/restore_file.sh: None /opt/omnistorage/bin/restore_vbfs: None /opt/omnistorage/bin/restore_vol: $Id: bm/etc/backup/restore_vol.sh@@/main/oms_2.2_dev _uid/2 97/07/01 14:37:31 $ /opt/omnistorage/bin/rkill: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/rmplat: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/setgrp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/unaliasp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/unloadp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/unmountp: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsadm: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsbind: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsclose: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsdbcheck: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vshdr: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsopen: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vsread: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/vswrite: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/wt-check: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/xhsm: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ OSF/Motif Version 1.2.5 /opt/omnistorage/bin/xhsmbackup: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ OSF/Motif Version 1.2.5 /opt/omnistorage/bin/xhsmmgr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Id: gui/lib/widgets/cheytreeelem.c@@/main/oms_2.2_d ev_uid/1 97/08/12 14:57:38 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ OSF/Motif Version 1.2.5 /opt/omnistorage/bin/xhsmmonitor: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ OSF/Motif Version 1.2.5 /opt/omnistorage/bin/zb: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/zdf: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/zerrmsg: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/zfind: $Revision: 59.1 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/zls: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/bin/zmdump: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/zmdump.sh: $Release: zmdump.src OMS.02.10.04$ /opt/omnistorage/bin/zmrestore: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/bin/zmrestore.sh: None /opt/omnistorage/lib/errmsgs: None /opt/omnistorage/lib/guimsg.ehdb: None /opt/omnistorage/lib/libcheyhsm.sl: $Id: mm/lib/dslib/dm2pv.c@@/main/oms_2.2_dev_uid/1 9 7/08/12 15:37:35 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date$ $Id: mm/lib/misc/Volume.C@@/main/oms_2.2_dev_uid/2 9 7/08/12 15:38:23 $ $Id: mm/lib/misc/fsidparse.c@@/main/oms_2.2_dev_uid/ 1 97/08/12 15:38:27 $ $Id: mm/lib/misc/getvolset.c@@/main/oms_2.2_dev_uid/ 1 97/08/12 15:38:32 $ $Id: mm/lib/misc/nevermigrate.c@@/main/oms_2.2_dev_u id/1 97/08/12 15:38:41 $ $Id: mm/lib/misc/openpqd.c@@/main/oms_2.2_dev_uid/1 97/08/12 15:38:45 $ $Id: mm/lib/misc/pqd-io.c@@/main/oms_2.2_dev_uid/1 9 7/08/12 15:38:54 $ $Id: mm/lib/misc/portamap.c@@/main/oms_2.2_dev_uid/1 97/08/12 15:38:50 $ /opt/omnistorage/lib/qrmsgs.Eng: None /opt/omnistorage/man/man1/ager.1: None /opt/omnistorage/man/man1/listp.1: None /opt/omnistorage/man/man1/rebuild.1: None /opt/omnistorage/man/man1/zb.1: None /opt/omnistorage/man/man1m/add_vol.1m: None /opt/omnistorage/man/man1m/bkup_vbfs.1m: None /opt/omnistorage/man/man1m/jmdrestore.1m: None /opt/omnistorage/man/man1m/restore_vbfs.1m: None /opt/omnistorage/man/man1m/restore_vol.1m: None /opt/omnistorage/man/man1m/sync_media.1m: None /opt/omnistorage/man/man1m/vsbind.1m: None /opt/omnistorage/man/man1m/zmdump.1m: None /opt/omnistorage/man/man1m/zmrestore.1m: None /opt/omnistorage/man/man4/brapicfg.4: None /opt/omnistorage/man/man4/jhosts.4: None /opt/omnistorage/man/man4/jmcfg.4: None /opt/omnistorage/man/man4/netcfg.4: None /opt/omnistorage/man/man4/zb.4: None /opt/omnistorage/newconfig/ded.inittab: None /opt/omnistorage/newconfig/iocfg.proto: None /opt/omnistorage/newconfig/jmcaps.proto: $Release: jmcaps.proto OMS.02.10.04$ /opt/omnistorage/newconfig/jmcfg.proto.libman: None /opt/omnistorage/newconfig/netcfg.proto: None /opt/omnistorage/sbin/ager: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Id: mm/lib/misc/portamap.c@@/main/oms_2.2_dev_uid/1 97/08/12 15:38:50 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/sbin/installchanger: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/sbin/io_server: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/sbin/jmd: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: VSDB.x,v: OmniStorage_0210$ $Id: VSDB.x,v 59.1 95/10/04 00:18:49 Cheyenne OmniSt orage_0210 $ %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % $Release: lm_acs.c,v: OMS_Silo - OMS.02.11.03$ $Id: lm/lib/port/lm_acs.c@@/main/1 97/11/13 14:44:30 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_eject/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_lock_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_ac/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_ca/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_mo/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_vo/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_response/2.1.2 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_status/2.0A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_set_access/2.1.1 % %rel ease: % %date_created: Mon Aug 1 10:03:45 1994 % (c) 1994 StorageTek %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_unlock_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_get_resp/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_send_req/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_vary_res/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_query_res/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_resp_audf/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A % %full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A % %full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A % %full_name: h/incl/acslm/cdk2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 % %full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A % %full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsapi/csrc/acs_get_pktver/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % acs_ipc_read.c 2.1.3 1/3/95 (c) 1994 STK %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_error/2.1 % %full_name: acsipc/csrc/acs_ipc_write/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_sel_input/2.1 % %full_name: acsipc/csrc/acs_verify_ssi/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_get_sock/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % cl_ipc_read.c 5.5 2/7/94 (c) 1994 STK cl_ipc_creat.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_write.c 1.1 1/10/94 (c) 1989-1994 STK cl_defs.c 1.1 1/10/94 (c) 1989-1994 STK ml_api.c 1.1 1/10/94 (c) 1989-1994 STK cl_status.c 1.2 1/13/94 (c) 1994 StorageTek cl_el_log_register.c 1.1 1/10/94 (c) 1989-1994 STK cl_el_log.c 1.1 1/10/94 (c) 1989-1994 STK cl_log.c 1.1 1/10/94 (c) 1993-1994 StorageTek cl_trace.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_send.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_open.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_init.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_qcreat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_qdelet.c 1.1 1/10/94 (c) 1989-1994 STK dv_api.c 1.1 1/10/94 (c) 1989-1994 STK cl_inform.c 1.1 1/10/94 (c) 1989-1994 STK cl_chk_input.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_xmit.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_macces.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mcreat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mdelet.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mlocat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_data.c 1.1 1/10/94 (c) 1989-1994 STK cl_type.c 1.2 1/11/94 (c) 1994 StorageTek cl_qm_create.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_find.c 1.1 1/10/94 (c) 1989-1994 STK cl_select_in.c 1.1 1/10/94 (c) 1989-1994 STK /opt/omnistorage/sbin/qr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /opt/omnistorage/sbin/removechanger: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/sbin/rpc.kill: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/sbin/rpc.niod: $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ /opt/omnistorage/sbin/sync_media: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp /sbin/ded: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.20.04 ( HP OmniStorage A.02.20, pat ch level 04, PHSS_17475 ) $ $Date: Thu Apr 22 14:07:32 EDT 1999$ libovsnmp ic12_r10dav_gs libc.a_ID@@/main/r10dav/libc_dav/bvd_ dav/1 /ux/libc/libs/libc/archive_pa1/libc.a_ID May 1 1996 11:43:41 /sbin/init.d/OMSclient: $Id: install/hpdmig/OMSclient.sh@@/main/oms_2.2_dev_ uid/5 97/10/06 15:01:55 $ /usr/lib/X11/app-defaults/XHsm: None cksum(1) Output: 2513829219 443 /etc/opt/omnistorage/brapicfg 939108331 6422 /opt/omnistorage/bin/add_vol 1868530262 119519 /opt/omnistorage/bin/aliasp 2221507509 16469 /opt/omnistorage/bin/bkup_vbfs 35775388 37059 /opt/omnistorage/bin/chgidp 3139483736 119513 /opt/omnistorage/bin/chgowner 543517811 119515 /opt/omnistorage/bin/chgstate 3040637857 354442 /opt/omnistorage/bin/cleanup 3057381726 1101415 /opt/omnistorage/bin/consolidate 3827225679 362482 /opt/omnistorage/bin/convert_media 3612500985 156633 /opt/omnistorage/bin/copyp 7126606 119516 /opt/omnistorage/bin/exportp 3001710448 123611 /opt/omnistorage/bin/formatp 3070749525 119516 /opt/omnistorage/bin/fsckp 1355132368 201751 /opt/omnistorage/bin/getfsid 1428894325 152386 /opt/omnistorage/bin/hsm_admin 2104779607 248763 /opt/omnistorage/bin/hsm_session 1299501683 119516 /opt/omnistorage/bin/importp 1459900473 131885 /opt/omnistorage/bin/inventory 436613546 201765 /opt/omnistorage/bin/jmdbackup 1907881685 197653 /opt/omnistorage/bin/jmdrestore 2409417370 131858 /opt/omnistorage/bin/listp 3878780074 119517 /opt/omnistorage/bin/loadp 961992267 222406 /opt/omnistorage/bin/migin 2147829110 366646 /opt/omnistorage/bin/migmv 3864545416 403730 /opt/omnistorage/bin/migout 1781892775 247128 /opt/omnistorage/bin/migsever 1333200920 119516 /opt/omnistorage/bin/mountp 3718674290 156634 /opt/omnistorage/bin/par 710921230 123611 /opt/omnistorage/bin/qjmd 148002528 131969 /opt/omnistorage/bin/qqr 336794058 1221307 /opt/omnistorage/bin/rebuild 309829242 2046 /opt/omnistorage/bin/rebuild.sh 1544520275 205868 /opt/omnistorage/bin/resid 397027848 989345 /opt/omnistorage/bin/restore_file 3802126793 2631 /opt/omnistorage/bin/restore_file.sh 3528359270 33542 /opt/omnistorage/bin/restore_vbfs 1655337232 9578 /opt/omnistorage/bin/restore_vol 3367223668 20543 /opt/omnistorage/bin/rkill 1494645691 119515 /opt/omnistorage/bin/rmplat 2185584773 119515 /opt/omnistorage/bin/setgrp 357358570 119515 /opt/omnistorage/bin/unaliasp 3245980649 119520 /opt/omnistorage/bin/unloadp 3900384381 119516 /opt/omnistorage/bin/unmountp 1633724311 152437 /opt/omnistorage/bin/vsadm 2104591066 374840 /opt/omnistorage/bin/vsbind 3257985198 185455 /opt/omnistorage/bin/vsclose 2899967348 366638 /opt/omnistorage/bin/vsdbcheck 2774514454 185456 /opt/omnistorage/bin/vshdr 3392641843 189555 /opt/omnistorage/bin/vsopen 699772216 185455 /opt/omnistorage/bin/vsread 565766354 185458 /opt/omnistorage/bin/vswrite 2189756508 210022 /opt/omnistorage/bin/wt-check 3205512223 1995757 /opt/omnistorage/bin/xhsm 779575027 3064840 /opt/omnistorage/bin/xhsmbackup 2592225821 4047947 /opt/omnistorage/bin/xhsmmgr 3848061937 2821303 /opt/omnistorage/bin/xhsmmonitor 2453424184 1125153 /opt/omnistorage/bin/zb 1880469934 267734 /opt/omnistorage/bin/zdf 487479965 24669 /opt/omnistorage/bin/zerrmsg 612978655 424461 /opt/omnistorage/bin/zfind 4204460467 222357 /opt/omnistorage/bin/zls 2453424184 1125153 /opt/omnistorage/bin/zmdump 2380844518 2877 /opt/omnistorage/bin/zmdump.sh 2453424184 1125153 /opt/omnistorage/bin/zmrestore 2385830771 3105 /opt/omnistorage/bin/zmrestore.sh 3066993654 525925 /opt/omnistorage/lib/errmsgs 3165476251 579704 /opt/omnistorage/lib/guimsg.ehdb 544200094 1369853 /opt/omnistorage/lib/libcheyhsm.sl 1543860080 50070 /opt/omnistorage/lib/qrmsgs.Eng 1967333304 10823 /opt/omnistorage/man/man1/ager.1 3419864240 8844 /opt/omnistorage/man/man1/listp.1 3872007207 5395 /opt/omnistorage/man/man1/rebuild.1 1445329413 11344 /opt/omnistorage/man/man1/zb.1 3371777965 5685 /opt/omnistorage/man/man1m/add_vol.1m 1087255774 8633 /opt/omnistorage/man/man1m/bkup_vbfs.1m 2582905588 1645 /opt/omnistorage/man/man1m/jmdrestore.1m 854674542 11334 /opt/omnistorage/man/man1m/restore_vbfs.1m 2160625239 2879 /opt/omnistorage/man/man1m/restore_vol.1m 449921427 7300 /opt/omnistorage/man/man1m/sync_media.1m 683803636 5871 /opt/omnistorage/man/man1m/vsbind.1m 948972909 3970 /opt/omnistorage/man/man1m/zmdump.1m 2085318830 6192 /opt/omnistorage/man/man1m/zmrestore.1m 2615136181 1231 /opt/omnistorage/man/man4/brapicfg.4 2259311042 2719 /opt/omnistorage/man/man4/jhosts.4 1682551713 7324 /opt/omnistorage/man/man4/jmcfg.4 3219455538 12595 /opt/omnistorage/man/man4/netcfg.4 2095712374 4072 /opt/omnistorage/man/man4/zb.4 535321568 86 /opt/omnistorage/newconfig/ded.inittab 632870657 1231 /opt/omnistorage/newconfig/iocfg.proto 3543865059 5213 /opt/omnistorage/newconfig/jmcaps.proto 888199609 2505 /opt/omnistorage/newconfig/jmcfg.proto.libman 845954341 1947 /opt/omnistorage/newconfig/netcfg.proto 805965076 851281 /opt/omnistorage/sbin/ager 1792333144 170263 /opt/omnistorage/sbin/installchanger 301603741 1749682 /opt/omnistorage/sbin/io_server 572885908 1605831 /opt/omnistorage/sbin/jmd 3475777476 1763240 /opt/omnistorage/sbin/qr 3162643203 195089 /opt/omnistorage/sbin/removechanger 779171205 20549 /opt/omnistorage/sbin/rpc.kill 1406028859 49455 /opt/omnistorage/sbin/rpc.niod 456996584 1028013 /opt/omnistorage/sbin/sync_media 1351548152 819070 /sbin/ded 511518607 4522 /sbin/init.d/OMSclient 2407436376 19081 /usr/lib/X11/app-defaults/XHsm Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_16750 PHCO_14842 s800: 10.20: PHKL_16751 PHCO_14842 Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_12882 PHSS_13437 PHSS_15452 PHSS_15818 Equivalent Patches: PHSS_17474: s700: 10.10 s800: 10.10 Patch Package Size: 35430 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_17475 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17475.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_17475.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_17475. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_17475.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_17475.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: We strongly recommend to install PHCO_16591 and PHKL_16750/PHKL_16751 or corresponding successors prior or after this OmniStorage product patch. This patch includes the following Site Specific Patches: SSPOMS_1 SSPOMS_2 SSPOMS_3 SSPOMS_4 SSPOMS_6 SSPOMS_9 SSPOMS_10 SSPOMS_13 SSPOMS_17 SSPOMS_20 SSPOMS_22 SSPOMS_24 SSPOMS_26 SSPOMS_28 Installation Instructions: 1> Become root user 2> Install this patch by running swinstall. swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17475.depot