c00653114
 
HP Tru64 UNIX - 5.1B-3 LSM/CLSM Fixes

»

HP Tru64 UNIX

Tru64 UNIX

» Tru64 UNIX V5.1B-6
» Tru64 UNIX V5.1B-5
» Documentation
» Information library
» Software web index
» Software products library
» Patch database
» Services
» Developer & Solution Partner Program
» Send us your comments
» Support Statements

Evolving business value

» Tru64 UNIX to HP-UX 11i transition benefits calculator
» Alpha RetainTrust Program
» Transition

Related links

» Alpha systems
» HP-UX 11i
» Integrity servers
» Linux
» HP storage
» HP solutions
HP-UX 11i: measurably better TCO!
 Advisory Information
 

RELEASE DATE: 2006-04-26

DESCRIPTION

This ERP fixes two problems seen in LSM/CLSM.

1) A failure may be encountered in the importing of a disk group in a three or more node cluster. This import failure is exhibited by “collision! Proposal already active” messages logged in the messages file. An example of these messages is as follows:

****************
Jan 7 13:13:29 node1 vmunix: clsm_propose_ioctl: ioctl '152' failed
Jan 7 13:13:29 node1 vmunix: CLSM: vol_klog_setlog distribution error.
Jan 7 13:13:29 node1 vmunix: clsm_propose: collision! proposal already active.
Jan 7 13:13:29 node1 vmunix: clsm_propose: collision! proposal already active.
Jan 7 13:13:29 node1 vmunix: clsm_propose_ioctl: ioctl '124' failed
Jan 7 13:13:29 node1 vmunix: clsm: vol_change_disk distribution error.
****************

2) The other problem is seen only when using SWXCR devices in a LSM/CLSM environment and is shown as being unable to add a device to the SWXCR controller. This problem can occur either on a standalone system or in a cluster environment and can be seen by a failure to boot a system or to add a device to the SWXCR controller. The symptoms that one may see when using a KZPAC/SWXCR disks on boot is as follows:

****************
starting LSM in boot mode
volio: Illegal vminor encountered
lsm:vold: ERROR: enable failed:
Error in disk group configuration copies
Disk group has no valid configuration copies;
transactions are disabled.
lsm:vold: ERROR: Disk group rootdg:
Errors in some configuration copies:
Disk dsk5, copy 1: Block 0: Disk read failure
Disk dsk0f, copy 1: Block 0: Disk read failure
Disk dsk3f, copy 1: Block 0: Disk read failure
lsm:vold: FATAL ERROR:
Rootdg cannot be imported during boot .....
.....
.....
lsm:vold: ERROR: enable failed:
Error in disk group configuration copies
Disk group has no valid configuration copies;
transactions are disabled.
LSM: Vold is not enabled for transactions
No volumes started
*****************

The symptom of the problem when using disks (LUNs) on a SWXCR controller can be seen by the following:

*****************
# voldisksetup -i dsk0e
lsm:voldisk: ERROR: Device dsk0e: define failed:
Disk write failure
*******************

 

 
SCOPE

The following version is affected:

HP UNIX Tru64 UNIX V5.1B-3

 
RESOLUTION

HP is releasing the following ERP kit publicly for use by any customer. The ERP kit use dupatch to install and will not install over any Customer Specific Patches (CSPs) that have file intersections with the ERP. Contact your service provider for assistance if the installation of this ERP is blocked by any of your installed CSPs.

The fixes contained in the ERP kit are scheduled to be available in the following mainstream patch kit:

HP Tru64 UNIX Version 5.1B-4

The kit distributes the following files:

/sbin/vold

Early Release Patches

HP Tru64 UNIX version: V5.1B-3:
ERP Kit Name: T64KIT1000494-V51BB26-E-20060404
Kit Location:
http://www.itrc.hp.com/service/patch/patchDetail.do?patchid=T64KIT1000494-V51BB26-E-20060404