 |
» |
|
|
|
|
|
|
|
|
|
<TITLE>
TITLE: HP Tru64 UNIX - Cumulative fixes for fixfdmn
Copyright (c) Hewlett-Packard Company 2006. All rights reserved.
PRODUCT: HP Tru64 UNIX [R] V5.1B-2
SOURCE: Hewlett-Packard Company
ECO INFORMATION:
ECO Name: T64KIT1000661-V51BB25-E-20060526
ECO Kit Approximate Size: 2.70MB
Kit Applies To: HP Tru64 UNIX V5.1B-2 PK4 (BL25)
ECO Kit CHECKSUMS:
/usr/bin/sum results:
07796 2760
/usr/bin/cksum results:
2775605485 2826240
MD5 results:
8242e2255ad6036535bfac32908d0831
SHA1 results:
ea945f736288d6f1ce3a705a488578e88260e488
ECO KIT SUMMARY:
A dupatch-based, Early Release Patch kit exists for HP Tru64 UNIX V5.1B-2
that contains solutions to the following problem(s):
This patch fixes problems fixfdmn has with AdvFS domains with multi-page
RBMT files, multiple SBM extents, more than one root tag file, clone
filesets, or when given an invalid fileset argument.
The following is a list of the problems fixed:
Fixfdmn does not properly handle domains with multi-page RBMT files. Error
messages are of the type:
fixfdmn: Gathering volume information
fixfdmn: Opening directory '/etc/fdmns/hsv1a-fs01'.
fixfdmn: Opening the volumes.
fixfdmn: Setting volume '/dev/disk/dsk1101a' to volume number 1.
fixfdmn: Checking the RBMT.
fixfdmn: Found corruptions in next RBMT page mcell.
fixfdmn: Found the transaction log onvolume /dev/disk/dsk1101a.
fixfdmn: Mcell (1,0,0) is corrupt.
fixfdmn: Mcell (1,0,4) is corrupt.
fixfdmn: Loading subsystem extents.
fixfdmn: Can't convert page 12 to an LBN,valid range is 0 to 12.
fixfdmn: Can't convert [R]BMT page 12 to LBN.
fixfdmn: Error collecting subsystem extents.
When growing an AdvFS volume, if there are multiple extents representing an
SBM, fixfdmn does not work on all the SBM extents. Example error messages
follow:
fixfdmn: XOR value for SBM Page 6 is not correct.
fixfdmn: Checking the RBMT.
fixfdmn: XOR value for SBM Page 6 is not correct.
fixfdmn: XOR value for SBM Page 7 is not correct.
fixfdmn: XOR value for SBM Page 107334860 is not correct.
fixfdmn: Unable to find the starting block of the SBM.
Fixfdmn fails when a clone's original fileset is missing a tag which is
present in the clone fileset.
Running fixfdmn only on a clone fileset always fails with an error. Example
error messages follow:
#fixfdmn new clone fixfdmn: Checking the RBMT.
fixfdmn: Clearing the log on volume /dev/disk/dsk5c.
fixfdmn: Checking the BMT mcell data.
fixfdmn: Checking the deferred delete list.
fixfdmn: Checking the root tag file.
fixfdmn: Checking the tag file(s).
fixfdmn: Checking the mcell nodes.
fixfdmn: Checking the BMT chains.
fixfdmn: Error correcting the BMT chains on fileset clone.
fixfdmn is not able to continue, no changes made to domain, exiting
Fixfdmn exits when it encounters a domain with more than one root tag file.
An example error message follows:
fixfdmn: Unable to continue, more than one root tag file.
Fixfdmn does not properly handle domains with multi-page RBMT files that
have their last page full and need to grow. Domains of this type will
domain panic when being activated (mounting the first fileset). An example
error message follows:
WARNING: file tag -6 in fileset "" has > 64K extent mcells.
The Patch Kit Installation Instructions and the Patch Summary and Release
Notes documents provide patch kit installation and removal instructions
and a summary of each patch. Please read these documents prior to
installing patches on your system.
The patches in this ERP kit will also be available in the next mainstream
patch kit - HP Tru64 UNIX V5.1B-4.
INSTALLATION NOTES:
1) Install this kit with the dupatch utility that is included in the patch
kit. You may need to baseline your system if you have manually changed
system files on your system. The dupatch utility provides the baselining
capability.
2) The patch in this ERP kit does not have any file intersections with any
other ERP available at this time for this product version.
3) This ERP kit will NOT install over any Customer Specific Patches (CSPs)
which have file intersections with this ERP kit. Contact your normal
Service Provider for assistance if the installation of this ERP kit is
blocked by any of your installed CSPs.
INSTALLATION PREREQUISITES:
You must have installed HP Tru64 UNIX V5.1B-2 PK4 (BL25) prior to
installing this Early Release Patch Kit.
SUPERSEDE INFORMATION:
None
KNOWN PROBLEMS WITH THE PATCH KIT:
None.
RELEASE NOTES FOR T64KIT1000661-V51BB25-E-20060526:
Release Notes
This document summarizes the contents and special instructions for the
Tru64 UNIX V5.1B patches contained in this kit.
For information about installing or removing patches, baselining,
and general patch management, see the Patch Kit Installation
Instructions document.
1 Release Notes
This Early Release Patch Kit Distribution contains:
- fixes that resolve the problem(s) reported in:
o 19396 273 98286 98886 99069 99310 QXCM1000316953 QXCM1000322917
* for Tru64 UNIX V5.1B T64V51BB25AS0004-20040616.tar (BL25)
The patches in this kit are being released early for general customer use.
Refer to the Release Notes for a summary of each patch and installation
prerequisites.
Patches in this kit are installed by running dupatch from the directory
in which the kit was untarred. For example, as root on the target system:
> mkdir -p /tmp/CSPkit1
> cd /tmp/CSPkit1
> <copy the kit to /tmp/CSPkit1>
> tar -xpvf DUV40D13-C0044900-1285-20000328.tar
> cd patch_kit
> ./dupatch
2 Special Instructions
SPECIAL INSTRUCTIONS for Tru64 UNIX V5.1B Patch C1657.04
3 Summary of CSPatches contained in this kit
Tru64 UNIX V5.1B
PatchId Summary Of Fix
----------------------------------------
C1657.04 Cumulative fixes for fixfdmn
4 Additional information from Engineering
None
5 Affected system files
This patch delivers the following files:
Tru64 UNIX V5.1B
Patch C1657.04
./sbin/advfs/fixfdmn
CHECKSUM: 20550 428
SUBSET: OSFADVFS540
[R] UNIX is a registered trademark in the United States and other countries
licensed exclusively through X/Open Company Limited.
Copyright Hewlett-Packard Company 2006. All Rights reserved.
This software is proprietary to and embodies the confidential technology
of Hewlett-Packard Company. Possession, use, or copying of this
software and media is authorized only pursuant to a valid written license
from Hewlett-Packard or an authorized sublicensor.
This ECO has not been through an exhaustive field test process.
Due to the experimental stage of this ECO/workaround, Hewlett-Packard
makes no representations regarding its use or performance. The
customer shall have the sole responsibility for adequate protection
and back-up data used in conjunction with this ECO/workaround.
|
Printable version
