This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
For NetBackup Enterprise Server and NetBackup Server patches, see the NetBackup Downloads.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
vm-hpux1123-5.0MP2RP3P3
Sign in if you want to rate this patch.

 Basic information
Release type: P-patch
Release date: 2014-11-10
OS update support: None
Technote: None
Documentation: None
Popularity: 745 viewed    23 downloaded
Download size: 248.69 MB
Checksum: 659126868

 Applies to one or more of the following products:
Storage Foundation 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation Cluster File System 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation for Oracle 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation for Oracle RAC 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation HA 5.0MP2 On HP-UX 11i v2 (11.23)
Volume Manager 5.0MP2 On HP-UX 11i v2 (11.23)
Volume Replicator 5.0MP2 On HP-UX 11i v2 (11.23)

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
vm-hpux1123-5.0MP2RP3P2 (obsolete) 2012-07-17
vm-hpux1123-5.0MP2RP3 (obsolete) 2010-10-13

This patch requires: Release date
vm-hpux1123-5.0MP2RP3P1 2011-11-04
sfha-hpux1123-5.0MP2RP3 2010-11-15

 Fixes the following incidents:
1003433, 1045826, 1164654, 1274122, 1274123, 1274138, 1274142, 1274148, 1274155, 1274177, 1274185, 1274194, 1274241, 1274243, 1274255, 1274272, 1274276, 1275028, 1299382, 1299403, 1360759, 1360836, 1360849, 1361304, 1362201, 1362204, 1363314, 1376234, 1381724, 1394216, 1409142, 1415504, 1416347, 1416349, 1422656, 1427498, 1427499, 1427500, 1427503, 1427504, 1427505, 1427506, 1450039, 1450048, 1450098, 1450934, 1451436, 1453894, 1455184, 1459367, 1465688, 1470963, 1501518, 1501593, 1501595, 1504534, 1504777, 1507982, 1509485, 1514000, 1514814, 1522342, 1528686, 1542863, 1543470, 1555898, 1557153, 1586930, 1587888, 1592476, 1631998, 1632029, 1632058, 1632081, 1636487, 1650957, 1670680, 1677976, 1719779, 1849485, 1872735, 1872747, 1874059, 1876291, 1885021, 1902781, 1921587, 1924619, 1927987, 1937718, 1937832, 1938036, 1938076, 1938088, 1938114, 1938117, 1944180, 1944259, 1946104, 1946105, 1946107, 1946109, 1946110, 1946112, 1946114, 1946116, 1946117, 1946118, 1957355, 1957358, 1969589, 2000303, 2027839, 2049321, 2049394, 2078241, 2091195, 2111423, 2111424, 2111441, 2111639, 2111672, 2112470, 2112477, 2138782, 2215565, 2236561, 2248993, 2274273, 2277306, 2280633, 2323929, 2325112, 2353415, 2353422, 2360720, 2368917, 2419942, 2497156, 2497157, 2497160, 2497164, 2497166, 2497228, 2530898, 2574355, 2627009, 2634096, 2662215, 2662216, 2803256, 2803260, 2803294, 2803331, 2883661, 3059082, 3059133, 3068188, 3121042, 3130375, 3541581, 3590514, 3590681, 3599106, 3632121

 Patch ID:
PHCO_44151
PHKL_44152

 Readme file  [Save As...]
                          * * * READ ME * * *
             * * * Veritas Volume Manager 5.0 MP2 RP3 * * *
                         * * * P-patch 3 * * *
                         Patch Date: 2014-11-07


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Volume Manager 5.0 MP2 RP3 P-patch 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v2 (11.23)


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation 5.0 MP2
   * Veritas Storage Foundation Cluster File System 5.0 MP2
   * Veritas Storage Foundation for Oracle 5.0 MP2
   * Veritas Storage Foundation for Oracle RAC 5.0 MP2
   * Veritas Storage Foundation HA 5.0 MP2
   * Veritas Volume Manager 5.0 MP2
   * Veritas Volume Replicator 5.0 MP2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHCO_44151, PHKL_44152
* 1872735 (1542605) The vxconfigd(1M) daemon dumps core when the disk group is imported on the 
slave node.
* 1872747 (1405756) vxpfto values are not getting persistent after rebooted node join on cluster.
* 2803294 (2680482) On system startup, there are many random directories like the 
vx.$RANDOM.$RANDOM.$RANDOM.$$ directories that are not cleaned up in the /tmp/ 
folder.
* 2883661 (2189812) When the 'vxdisk updateudid' command is executed on a disk which is in 
the 'online invalid' state, the vxconfigd(1M) daemon dumps core.
* 3059082 (1921503) The vxvmconvert(1M) command fails with the an error message.
* 3059133 (2979824) The vxdiskadm(1M) utility bug results in the exclusion of the unintended paths.
* 3068188 (1820179) "vxdctl debug debuglevel"  command dumps core if vxconfigd 
log file was modified when vxconfigd starts with "logfile=file-name" option.
* 3121042 (2310284) In the Veritas Volume Manager (VxVM) versions prior to 5.1SP1, the Cross-
Platform-Data Sharing (CDS) disk initialization of Logical Unit Number (LUN) 
size greater than 1 TB may lead to data corruption.
* 3130375 (3130361) Prevent disk initialization of size greater than 1TB for disks with the CDS 
format.
* 3541581 (1675599) The vxconfigd daemon leaks memory while excluding and 
including a Third party Driver-controlled Logical Unit 
Number (LUN) in a loop. As a part of this, vxconfigd loses
its license information and an error is seen 
in the system log.
* 3590514 (983047) The vxconfigd(1M) daemon dumps core during the distribution of the diskgroup-
configuration copies amongst the disks.
* 3590681 (1052684) The vxconfigd(1M) dumps core during the device discovery in the 
memset() function.
* 3599106 (3263105) The disk evacuation operation (vxevac()) fails for a volume with Data Change 
Object (DCO).
* 3632121 (2864311) Creating kernel patch as a corerequisite for command patch as 
command patch contains kernel binaries
Patch ID: PHCO_43057, PHKL_43058
* 2627009 (2413763) Uninitialized memory read results in a vxconfigd coredump
* 2634096 (1206369) The recoveryoption of enclosure when set to nothrottle, is not persistent after reboot.
* 2662215 (2067319) MaxFli:vxconfgid hung on master when join two slaves are trying to join the cluster
* 2662216 (530741) CVM: vxconfigd assert in commit()
* 2803256 (2647975) Customer ran hastop -local and shared dg had splitbrain
* 2803260 (2040150) Loss of SCSI-3 PGR Keys during cluster reconfiguration if there are 32 or more keys per LUN.
* 2803331 (2792748) CVM join fails because of wrong fd close.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: PHCO_44151, PHKL_44152

* 1872735 (Tracking ID: 1542605)

SYMPTOM:
The vxconfigd(1M) daemon dumps core when the disk group is imported on the 
slave node. The following stack trace is observed:
config_import()
slave_dg_import()
slave_response()
fillnextreq()
vold_getrequest()
request_loop()
main()

DESCRIPTION:
After importing the diskgroup on the slave node, the vxconfigd(1M) deamon tries 
to set the PFTO value for the disks in the disk group.The vxconfigd(1M) daemon 
uses the information sent by the master node in form of a buffer to set the 
PFTO value. However, when the PFTO value is set, the records sent by the master 
node is changed to a garbage value. As a result, the vxconfigd(1M) daemon 
accesses the illegal memory and dumps core. The information required to set the 
PFTO value is locally available on the slave node.This local information on the 
slave node is subsequently used to set the PFTO value.

RESOLUTION:
The code is modified to avoid the illegal memory access.The information 
available on the slave node is used to set the PFTO value, instead of relying 
on the buffer sent by the master node.

* 1872747 (Tracking ID: 1405756)

SYMPTOM:
vxpfto values are not getting persistent after rebooted node join on cluster.

DESCRIPTION:
The PFTO values for disks are set only during the
diskgroup import operation. These values are not set
appropriately on shared disk groups when a node joins
the cluster. Any node in the cluster which has been
rebooted will not observe the manual PFTO setting on
the disk after joining the cluster, while remaining
nodes which are not rebooted will continue to observe
the value manually set.

RESOLUTION:
The PFTO values for disks in shared diskgroups are
now set appropriately when a node joins the cluster
and when the slave nodes import a shared diskgroup.

* 2803294 (Tracking ID: 2680482)

SYMPTOM:
On system startup, there are many random directories like the 
vx.$RANDOM.$RANDOM.$RANDOM.$$ directories that are not cleaned up in the /tmp/ 
folder.

DESCRIPTION:
In general, the start-up scripts should call the quit() 
function, to clean the errors detected. However, the 
start-up scripts call the exit() function instead of 
calling the quit()  function. This results in some 
directories that are created randomly to be unclean.

RESOLUTION:
The code is modified so that the scripts call the quit() 
function instead of calling the exit() function.

* 2883661 (Tracking ID: 2189812)

SYMPTOM:
When the 'vxdisk updateudid' command is executed on a disk which is in 
the 'online invalid' state, the vxconfigd(1M) daemon dumps core with the 
following stack trace:
priv_join()
req_disk_updateudid()
request_loop()
main()

DESCRIPTION:
When udid is updated, the null check is not done for an internal data 
structure. As a result, the vxconfigd(1M) daemon dumps core.

RESOLUTION:
The code is modified to add null checks for the internal data structure.

* 3059082 (Tracking ID: 1921503)

SYMPTOM:
The vxvmconvert(1M) command fails with the following error message:
VxVM vxprtvtoc INFO V-5-2-865 usage : 
vxprtvtoc -f <filename> <device>
The conversion operation failed with the following error:
VxVM vxlvmencap ERROR V-5-2-310 The <c#t#d#> disk does not appear to be prepared
for this system.

DESCRIPTION:
The problem occurs on an Active Passive (AP) storage array that has multiple
primary paths to the disks. The incorrect logic to select the primary enabled 
path
that is active returns a NULL value, and this causes the error.

RESOLUTION:
Modified the code to correctly select the primary enabled path that is active.

* 3059133 (Tracking ID: 2979824)

SYMPTOM:
While excluding the controller using the vxdiskadm(1M) utility, the unintended 
paths get excluded

DESCRIPTION:
The issue occurs due to a logical error related to the grep command, when the 
hardware path of the controller to be retrieved is excluded. In some cases, the 
vxdiskadm(1M) utility takes the wrong hardware path for the controller that is 
excluded, and hence excludes unintended paths. Suppose there are two 
controllers viz. c189 and c18 and the controller c189 is listed above c18 in 
the command, and the controller c18 is excluded, then the hardware path of the 
controller c189 is passed to the function and hence it ends up excluding the 
wrong controller.

RESOLUTION:
The script is modified so that the vxdiskadm(1M) utility now takes the hardware 
path of the intended controller only, and the unintended paths do not get 
excluded.

* 3068188 (Tracking ID: 1820179)

SYMPTOM:
The "vxdctl debug debuglevel" (1M) command core 
dumps and the following stack trace is displayed:
strcpy.strcpy()
xfree_internal()
msg_logfile_disable()
req_vold_debug()
request_loop()
main()

DESCRIPTION:
The vxconfigd(1M) command uses a static memory for storing
 the logfile information when it is started with 
logfile=file-name. This logfile can be changed with the 
vxdctl(1M) command. The "vxdctl debug" (1M) command uses 
dynamically allocated memory for storing the path 
information. If the default debug level is changed using 
the vxdctl(1M) command, the allocated memory for path
information is deleted assuming that it is created by
the vxdctl(1M) debug command. Thus, it results in core 
dump.

RESOLUTION:
The code is modified to allocate dynamic memory for 
storing the path information.

* 3121042 (Tracking ID: 2310284)

SYMPTOM:
In the Veritas Volume Manager (VxVM) versions prior to 5.1SP1, the Cross-
Platform-Data Sharing (CDS) disk initialization of Logical Unit Number (LUN) 
size greater than 1 TB may lead to data corruption.

DESCRIPTION:
The Veritas Volume Manager (VxVM) versions prior to 5.1SP1, allows CDS-disk 
initialization of LUN size greater than 1TB. A CDS disk of size greater than 
1TB can cause data corruption because of writing the backup labels. 
and the label ids. in the data or the public regions.VxVM should not allow the 
CDS-disk initialization for the LUN size that is greater than 1TB to support 
the CDS compatibility across platform.

RESOLUTION:
The code is modified to restrict the vxdisksetup(1M)command to perform the CDS-
disk initialization for a CDS disk of size greater than 1TB.

* 3130375 (Tracking ID: 3130361)

SYMPTOM:
Disks greater than 1 TB can be initialized with the Cross Platform Data 
sharing 
(CDS) format.

DESCRIPTION:
CDS formatted disks use Sun Microsystems Label (SMI) for partitioning. SMI 
partition table is capable of storing partition size of 1 TB only. 
EarlierVxVM 
releases did not prevent initialization of disks greater than 1 TB with the 
CDS 
format.

RESOLUTION:
The code is modified so that VxVM can explicitly prevent initialization of 
disks greater than 1 TB with the CDS format. Other VxVM utilities 
like vxvmconvert, vxcdsconvert, and DLE (vxdisk resize) either 
explicitly 
fail the operation, if the environment involves greater than 1 TB disks, or 
use 
the HPDISK format wherever possible.

* 3541581 (Tracking ID: 1675599)

SYMPTOM:
The vxconfigd daemon leaks memory while excluding and 
including a Third party Driver-controlled Logical Unit 
Number (LUN) in a loop. As a part of this, vxconfigd loses
its license information and the following error is seen 
in the system log:
"License has expired or is not available for operation"

DESCRIPTION:
In the vxconfigd code, the memory allocated for various 
data structures related to device discovery layer is not 
freed, resulting in the memory leak.

RESOLUTION:
The code is modified so that the memory is released after 
its scope is over.

* 3590514 (Tracking ID: 983047)

SYMPTOM:
The vxconfigd(1M) daemon dumps core during the distribution of the diskgroup-
configuration copies amongst the disks. The following stack trace is observed:
rem32I()
ncopy_set_scatter()
ncopy_set_group()
ncopy_dist_copies_inside_jbod()
ncopy_dist_copies_inside_enclr()
ncopy_policy_some()
ncopy_set_copies()
dg_balance_copies()
dg_import_finish()
dg_recover_all()
mode_set()
setup_mode()
startup()
main()

DESCRIPTION:
The vxconfigd(1M) daemon distributes the diskgroup-configuration copies amongst 
thedisks in an enclosure. During this process it categorizes the disks amongst
the controller groups, and distributes the configuration copies amongst the 
disks in thecontroller group. This involves the configuration copies on the 
disks being enabled or disabled. 
It uses some random function to identify a disk whose configuration copy is to 
be enabled. However, before the random calculation is performed, it does not 
check if all the configuration copies in a controller group are already in the 
enabled state or not. As a result, an attempt to divide by zero occurs. This 
leads to the core dump.

RESOLUTION:
The code is modified to check if all the configuration copies in a controller
group are in the enabled state, before the disk whose configuration
copy is to be enabled is identified. The distribution of the configuration 
copies are not performed for such instances. This prevents the core dump.

* 3590681 (Tracking ID: 1052684)

SYMPTOM:
During the device discovery in the memset() function, the vxconfigd(1M) daemon 
dumps core with the following stack trace:
memset()
padstring()
ddl_exclude_vidpid_from_vxvm()
ddl_exclude_device_from_vxvm()
mark_exclude_device()
ddl_claim_single_disk()
ddl_thread_claim_disk()
ddl_task_start()
volddl_thread_start()
__pthread_bound_body()

DESCRIPTION:
This issue is observed in the device discovery when the disk array from some 
vendor is excluded from the VxVM control such that the length of the vendor ID 
or the product ID strings exceeds 8 characters or 16 characters respectively. 
The disk array can be excluded from the VxVM control using vxddladm(1M) command.
Few internal data structures are maintained in the code to store the vendor and 
the product ID strings and their maximum limits. However, if some disk array is 
excluded from the VxVM control, such that the vendor ID length exceeds 8 
characters or the product ID length exceeds 16 characters, then the vendor and 
the product ID strings do not get NULL terminated during the initialization. As 
a result, the memset() function accesses the incorrect index of the destination 
buffer.This results in the core dump.

RESOLUTION:
The code is modified to correctly initialize the vendor ID and the product ID 
related to the internal data structures.

* 3599106 (Tracking ID: 3263105)

SYMPTOM:
The disk evacuation operation (vxevac()) fails for a volume with Data Change 
Object (DCO).

DESCRIPTION:
During the vxevac() operation, all sub-disks of a volume that reside on the 
specified source disk are moved to the destination disk. As part of the disk 
evacuation of the volume, its corresponding Data Change Log volume's (DCL's) 
sub-disks are also moved.
The vxevac() operation re-tries to move the sub-disks of the DCL volume. This 
fails because the sub-disks are already moved.

RESOLUTION:
The code is modified to exclude the DCL volumes, for which the disk evacuation 
is already completed as a part of the parent-volume-disk evacuation.

* 3632121 (Tracking ID: 2864311)

SYMPTOM:
VxVM Command Patch PHCO_44156 patches the following kernel modules in the VxVM
command fileset, VRTSvxvm.VXVM-RUN.

/usr/conf/mod/dmphpalua
/usr/conf/mod/dmphdsalua
 
Installing the patch will rebuild the kernel but a reboot is not enforced.

DESCRIPTION:
Typically VxVM command patches do not issue a reboot.  In order to continue 
following that, PHCO_44156 is not flagged for reboot. As such, PHCO_44156 should
be installed along with a co-dependent VxVM kernel patch, which will serve to
trigger the reboot.

RESOLUTION:
A new VxVM kernel patch is released to be installed with PHCO_44156 to enforce a
reboot.

Patch ID: PHCO_43057, PHKL_43058

* 2627009 (Tracking ID: 2413763)

SYMPTOM:
vxconfigd, the VxVM daemon dumps core with the following stack:

ddl_fill_dmp_info
ddl_init_dmp_tree
ddl_fetch_dmp_tree
ddl_find_devices_in_system
find_devices_in_system
mode_set
setup_mode
startup
main
__libc_start_main
_start

DESCRIPTION:
Dynamic Multi Pathing node buffer declared in the Device Discovery Layer was not 
initialized. Since  the node buffer is local to the function, an explicit 
initialization is required before copying another buffer into it.

RESOLUTION:
The node buffer is appropriately initialized using memset() to address the 
coredump.

* 2634096 (Tracking ID: 1206369)

SYMPTOM:
The recoveryoption of enclosure when set to nothrottle, is not persistent after 
reboot.

DESCRIPTION:
When the CLI 'vxdmpadm setattr' was used to set recovery option as nothrottle, 
the persistent information was not updated correctly.
After a reboot the nothrottle recoveryoption was not being considered, hence 
user set value was not effective and the value changed back to default.

RESOLUTION:
Corrected vxdmp code to update nothrottle recovery option and to read it back at 
boot time.

* 2662215 (Tracking ID: 2067319)

SYMPTOM:
In a multi node CVM (Cluster Volume Manager) environment, the vxconfigd process
(VxVM configuration daemon) on master node may hang during a cluster
reconfiguration.

The vxconfigd can be found in tight loop with following stack:
  msgtail() + 0x204
  msg() + 0x5c
  send_slaves() + 0xd94
  master_send_abort() + 0x90
  send_slaves() + 0xe4
  master_get_results() + 0x58
  commit() + 0x1acc
  req_vol_commit() + 0x968
  request_loop() + 0xec8
  main() + 0x14e0
  __start() + 0x68

A number of following messages can be seen in the syslog.
  VxVM vxconfigd WARNING  V-5-1-10377 send_slave: got slave_join: retry later

DESCRIPTION:
In CVM environment, master synchronizes the transaction details related to any
configuration change among all the joined slaves (passive). While a transaction
is in progress, if CVM reconfiguration happens due to join of a new node, the
master aborts the transaction. In this situation a race between a passive slave
and master is causing the vxconfigd hang on the master node.

RESOLUTION:
The transaction abort code is modified to handle the CVM reconfiguration properly.

* 2662216 (Tracking ID: 530741)

SYMPTOM:
In CVM(Cluster Volume Manager) environment where a private DG(Disk Group) is
imported, vxconfigd process may dump a core when 'vxdg -g <DG> flush' on the
private DG is executed just after the following commands in sequence:

i) A volume stop in the DG fails with error "Error in cluster processing" 

  # vxvol -g <Private DG> stop <Volume>
  VxVM vxvol ERROR V-5-1-10128  Error in cluster processing

ii) Subsequent volume stop succeeds.

  # vxvol -g <Private DG> -f stop <Volume>
  #

The core shows the following stack;

  dbf_fmt_tbl+0x4c0()
  voldbf_fmt_tbl+0x3c()
  voldbsup_format_record+0xa0()
  format_write+0x2d8()
  ddb_update+0x15c()
  dg_update+0x11c()
  req_dg_flush_common+0x354()
  req_dg_flush_name+0x7c()
  request_loop+0xae4()
  main+0xcb4()
  _start+0x108()

Then once the DG is deported, next import will be failed with the following error;

  # vxdg import <Private DG>
  VxVM vxdg ERROR V-5-1-10978 Disk group <Private DG>: import failed: 
  Disk group has no valid configuration copies

In the messages file, the following log will be seen;

  vxvm:vxconfigd: [ID 702911 daemon.error]      Disk <Disk>, copy 1: Block 1:
Duplicate record in configuration

DESCRIPTION:
On any configuration change, VxVM will try to keep the same configuration data
to be stored in the user land(vxconfigd), kernel land(vxio) and on-disk
database. If the transaction of configuration change encounters an error, VxVM
will clean up any inconsistencies between the user land, kernel land and on-disk
database.

In CVM environment, if cluster reconfiguration occurs following a transaction of
configuration change on a private DG, the transaction may be aborted because of
the reconfiguration. However appropriate clean up on the databases is not done
in an error case where transaction in kernel is aborted by the
reconfiguration.

Then another configuration change in the same private DG would result in a
duplicate record in the VxVM configuration database leading to a coredump or
disk group import issue.

This is a rare timing issue, however may be seen in a normal cluster stop operation.

RESOLUTION:
Code changes are made to hold on appropriate clean up and set appropriate
error code.

* 2803256 (Tracking ID: 2647975)

SYMPTOM:
Serial Split Brain (SSB) condition caused Cluster Volume Manager (CVM)
Master Takeover to fail. The below vxconfigd debug output was noticed when the
issue was noticed,

VxVM vxconfigd NOTICE V-5-1-7899 CVM_VOLD_CHANGE command received
V-5-1-0 Preempting CM NID 1
VxVM vxconfigd NOTICE V-5-1-9576 Split Brain. da id is 0.5, while dm id is 0.4 
for
dm cvmdgA-01
VxVM vxconfigd WARNING V-5-1-8060 master: could not delete shared disk groups
VxVM vxconfigd ERROR V-5-1-7934 Disk group cvmdgA: Disabled by errors 
VxVM vxconfigd ERROR V-5-1-7934 Disk group cvmdgB: Disabled by errors 
...
VxVM vxconfigd ERROR V-5-1-11467 kernel_fail_join() :           Reconfiguration
interrupted: Reason is transition to role failed (12, 1)
VxVM vxconfigd NOTICE V-5-1-7901 CVM_VOLD_STOP command received

DESCRIPTION:
When Serial Split Brain (SSB) condition is detected by the new CVM
master, on Veritas Volume Manager (VxVM)  versions 5.0 and 5.1, the default CVM 
behaviour will cause the new CVM master to leave the cluster and causes
cluster-wide downtime.

RESOLUTION:
When SSB is detected in a diskgroup, CVM will only disable that
particular diskgroup and keep the other diskgroups imported during the CVM 
Master
Takeover, the new CVM master will not leave the cluster with the fix applied.

* 2803260 (Tracking ID: 2040150)

SYMPTOM:
IO error messages for dmpnode observed in events logs (with reservation 
conflict error). Disk Marked Failing. We hit this issue when total number of PGR 
keys goes 32 or more by count.

DESCRIPTION:
Whenever there is 32 or more keys, we are not able to get all keys because 
only 7th byte of response buffer is used to get total bytes where keys are 
stored. In case of N keys, DMP can only read the first N % 32 (where % is 
mathematical modulo) keys of them.

RESOLUTION:
As per scsi-3 standard the 4th to 7th byte of response buffer of 
PGR_READ_KEYS command gives total bytes where keys are stored. Calculating 
buflen to follow using 4th to 7th byte of response buffer.

* 2803331 (Tracking ID: 2792748)

SYMPTOM:
In an HPUX CVM environment, the slave join fails with the 
following error message in syslog :

VxVM vxconfigd ERROR V-5-1-5784 cluster_establish:kernel interrupted vold on 
overlapping reconfig.

DESCRIPTION:
During the join, the slave node performs disk group import. As 
part of the import, the file descriptor pertaining to "Port u" is closed because 
of a wrong assignment of the return value of open(). Hence, the subsequent write 
to the same port was returning EBADF.

RESOLUTION:
This code issue is corrected by adding additional brackets 
thereby avoiding the wrong file descriptor close. Also, allow setting pfto 
attribute to 0.



INSTALLING THE PATCH
--------------------
$ swinstall -x autoreboot=true PHCO_44151 PHKL_44152
Please do swverify after installing the patches in order to make sure that the patches are installed correctly using:

   $ swverify PHCO_44151 PHKL_44152


REMOVING THE PATCH
------------------
To remove the patch, enter the following command:

   # swremove  -x autoreboot=true PHCO_44151 PHKL_44152


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
Incidents fixed in MP2RP3P1:
==========================
unixvm-cvs:
Incident parent                 Abstract
-------- ---------------------------------------------------------------------
2049321 (2441937) vxconfigrestore precommit fails with awk errors
2138782 (1822681) memory leak in vxio/voldrl_cleansio_start
2215565 (2209866) Inconsistent behavior with handling of siteconsistent flag
2236561 (990338)  FMR Refreshing a snapshot should keep the same name for the snap object
2248993 (1715204) vxsnap operations leads to orphan snap obj in case of any failure occurs during operation, orphan snap
 object can't be removed.
2274273 (850816)  Parallel 'vxsnap reattach' operations can cause data corruption. Also, lead to orphan snap objects.
2277306 (2183984) System panic in dmp_update_stats() routine
2280633 (2280624) Need to set site consistent only on mirrored-volumes.
2323929 (2323925) If rootdisk is encapsulated and if install-db is present, clear warning should be displayed on system
boot.
2325112 (1545835) vxconfigd core dump during system boot after VxVM4.1RP4 applied.
2353415 (2349352) During LUN provisioning in single path IO mode environment a data corruption is observed
2353422 (2334534) In CVM environment, vxconfigd level join is hung when Master returns error "VE_NO_JOINERS" to a joinin
g node and cluster nidmap is changed in new reconfiguration
2360720 (2359814) vxconfigbackup doesn't handle errors well
2368917 (1818780) Oakmont Linux consume many memories during dmp test.
2419942 (844758)  vxbrk_rootmir fails with second swapvol
2497156 (2165141) vxvm resets b_clock_ticks to zero if I/O hints are passed by VxFS
2497157 (2026773) DMP: vxconfigd hang after array side port disable followed by vxdisk scandisks
2497160 (1268784) Memory Leaks in VxVM plugin of VxMS
2497164 (1381772) Slow performance of snapshot backups after applying ET1269854.
2497166 (1215169) Customer concerned about high memory consumption by vxesd on 5.0MP2RP2 on HP 11.23
2497228 (2481938) QXCR1001120138: vxconfigbackup throwing an error when DG contains a sectioned disk
2530898 (1137504) vxesd -k does not kill existing intance but starts multiple ones

vmprov:
2574355 Create a vmprovider patch for 5.0/11.23 MP2RP3P1

Incidents fixed in MP2RP3:
==========================
Incident parent                 Abstract
-------- ---------------------------------------------------------------------
1045826 (929437)  HP-UX 11.23 - vxvm 5.0 MP1 - errors from apm_keyget: invalid APM crc
1514814 (1362609) vxconfigd ERROR V-5-1- 12826 osuuid invalid guid in console.log VxVM 5.0
1677976 (1976961) vxconfigd is hung in dmp_close_path
1937718 (1933970) Restrict the max_specialio tunable value to the permissible limit.
2000303 (1589715) vxconfigd dumps core, after vxdmpadm getportids ctlr=<ctlr_name>   on a disabled ctlr
2027839 (2027831) vxdg free not reporting free space correctly on CVM master. vxprint not printing DEVICE column for SDs
2049394 (2029324) /etc/vx/diag.d/vxcvmdiag cvminfo core dumps
2078241 (2078209) resize of vxvm volume resulting in vxconfigd hang -- Need to increase the default value for volpagemod_max_memsz
2091195 (1224659) Customer appears to be hitting e1224659 when running vxconfigbackup on 5.0MP2RP2 on HP 11.23
2111423 (1488399) DMP: Detection of I/O being sent on SCTL device on HP
2111424 (1485075) vmtest/tc/scripts/admin/voldg/cds/set.tc hits DMP ted assert dmp_select_path:2a
2111441 (1954062) vxrecover results in os crash
2111639 (1114178) vxconfigd dumped a core in req_dg_get_info_common()
2111672 (1528932) vxconfigd asserts in config_db_disable()
2112470 (339187)  CVM activation tag in vxprint -m output breaks vxprint
2112477 (1138518) vx commands (such as vxdg, vxdctl, vxdisk) hanging

Incidents fixed in MP2RP2:
==========================
1927987 (1927982) vxpfto returns error arbitrarily even though the command sets the values correctly.
1944259 (1701865) join failed due to interrupted reconfig on joiner and same reconfig completed on master
1451436 (1593032) vxfenconfig ERROR V-11- 2-1064 DMP Idle Lun Monitoring DeRegistration FAILED
1957355 (1744224) FMR3: multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption
1937832 (1755466) vol_find_ilock: searching of ilock is inefficient
1938088 (1755830) kmsg: sender: the logic for resend of messages needs to be optimized
1938117 (1755810) kmsg: sender thread is woken up unnecessarily during flowcontrol
1938114 (1755788) for a broadcast message, sender thread may end up sending the same message multiple times (not resend)
1938036 (1755519) kmsg layer: receiver side flowcontrol is not supported
1938076 (1755628) kmsg layer: with heavy messaging in the cluster the receiver thread slows down processing
1275028 (927444)  Makefile.kernel file needs dcoinc.h header file
1849485 (1677416) Node is not joining back into the cluster
1969589 (1969526) panic in voldiodone when a hung priv region I/O comes back
1944180 (1819777) panic caused because of voldisk getting deleted in kernel when I/Os are active, due to duplicate da rid.
1946107 (1435470) Cluster nodes panicked in voldco_or_pvmbuf_to_pvmbuf code after installing 5.0MP3
1957358 (1729558) multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption in FMR2
1874059 (1435681) vxesd looping, using ~100% of one CPU.
1902781 (1228526) Running vxdg flush on a slave node in a cvm cluster disables the disk group
1924619 (1532363) vxdisk 'updateudid' is corrupting diskid. Import of diskgroup fails.
1587888 (1587885) vxdiskunsetup fails with error "awk: Input line cannot be longer than 3, 000 bytes"
1876291 (913890)  EMC ASL (libvxemc.so) with PowerPath co- existence is unable to skip LUNZ disks (CLARiiON) and PP co-existence broken on HP
1946112 (1471581) vxconfigd may hang when checking for ecopy functionality on array (ASL)
1946117 (1742702) vxvmconvert fails, probably due to wrong disk capacity calculation
1946110 (147037)  vxconfigd cores at start up
1946109 (1463547) Persistent vxconfigd core dump on dynamic LUN reconfiguration.
1921587 (1907796) Corrupted Blocks in Oracle after Dynamic LUN expansion and vxconfigd core dump
1946105 (1421078) Manpage for vxdg(1M) needs to cover last shared dg disk detach scenario better
1946116 (1059720) Switching to EBN does not imediately show EFI disks correctly
1885021 (839077)  vxresize fails on filesystems greater than 2TB
1946114 (1676061) System panic'd after 2 out of 4 paths to disk were removed.
1946118 (1192166) vxdg -n [newdg] deport [origdg] causes a sort of memory leak
1946104 (1203661) vxclustadm man page needs mcsg instead of hpsg, redundant ifdefs
1501595 (1650955) 'vxdctl enable' caused node panic after one path unmasked/unpresented on array

Incidents Fixed in MP2RP1
==================
1164654 (795042)  vxvmconvert tools needs to be modified to eliminate the use of private LVM headers.
1274122 (828910)  Double free of memory in voldg_clean_cpulist()
1274138 (1087073) disk.convert script prints VGs converted list when one or more failed
1274155 (1015605) HPUX11.23/VxVM4.1:Poison nibble: nibble of 0xc in the dmp minor will cause panic
1274241 (1001370) Lun reuse issue not fixed by the DMP backport hotfix
1274243 (1064826) [LINUX TC] scripts/admin/cbr/backupdaemon.tc gives error "Could not do stat on path /devsdw"
1274255 (972406)  Tc /vmtest/tc/scripts/admiAn/vold/voldhang_dbg.tc#5 has hung in IA debug .
1360836 (1321272) vxcommands hanging after re-connect the FC-site link
1361304 (1260745) Node is not joining the cluster after reconnect the FC & heartbeat link.
1394216 (1393764) vxconfigd hung on node which is on which try to become master on site2 when FC and haerbeat link is disabled at same time.
1409142 (1361260) Slow I/O performance with VxFS filesystems on mirror-concat VxVM volumes with DCO and DRL.
1455184 (1414336) Disk devices do not appear in vxdisk list, but in vxprint
1470963 (1599295) /vmtest/tc/scripts/support/vxdisksetup/setup.tc is FAILED with vxdisksetup on IA
1501518 (1395616) vxdmp for the PGR_PREEMPT command unnecessarily retries on all paths and multiple times incase of RESV_CONFLICT
1501593 (1426480) VOLCVM_CLEAR_PR ioctl does not propogate the error returned by DMP to the caller
1504534 (795129)  :HPUX 11iv2:VxVM 3.5 Patch3:DG loses - CVM/VxVM with MC/SG
1504777 (1131566) If a config or klog copy hits an error, vxconfigd should validate and possibly detach the disk
1507982 (1507935) 5.0MP3RP1 Campus Cluster: vxconfigd core dumps when settag set to long sitename
1509485 (1220091) Reduce slave disk re-onlines from SLAVE_DISK_OP_NOTIFY request from master.
1514000 (1458481) volfmr_copymaps_instant panic on node of cluster during shared and private dg creations
1522342 (1269468) Enclosure removed/presented back multiple times, whilst vxconfigd is restarted, core dumps
1528686 (1227106) HxRT SFOR 5.0mp3 PowerPath/DMX : PGR key issues - Uncertain PGR key number and vold_pgr_unregister failed errors
1542863 (1541662) System panicked in DRL code when running flashsnap
1543470 (1159227) HxRT50MP2: Getting core file related to vxesd in SFORAHA stack using combo installer.
1555898 (1068626) Full resync occurred in remaining nodes after SFORAC panic rebooted
1557153 (1729344) vxdg deport hung
1592476 (1543908) While running vxevac command, Oracle process thread stuck into ogetblk() which leads to i/o hang.
1631998 (1397234) Vm command hung consistently during DMP testing on PA machine.
1632029 (1392872) Nodes has panicked on which failover has happened when master TOCed and disable FC and both sites are writing to same volume.
1632058 (1393756) Vxcommands hung on master & slave after FC-site link disconnected
1632081 (1321296) Tc /vmtest/tc/scripts/admin/ispbo/snappr int-clb.tc#1 has dumped the core in vxassist.
1636487 (1289510) vxconfigd dumps core during vmcert run and later vm hung
1650957 (1228140) After setting path attribute to active, path state is not updated.
1670680 (1787772) deporting a dg hangs after re-connect the FC site Link
1719779 (1468885) The vxbrk_rootmir script does not complete and is hanging after invoking vxprivutil
1363314 (1260746) Node not joining back with 2min delay in disconnecting FC & heartbeat link
1586930 (1878759) /scripts/kernel/vxdmp/misc/dmp_scsi.tc cause panic on 11.23 IVM Guest machine
==================

Incidents Fixed in MP2
==============================
1003433 (600447)  vxprivutil dumpconfig <disk>   is showing last_platform as 0x0#bad
1274123 (832350)  vxdctl's initdmp section of man page require correction
1274142 (524055)  vxvm:vxassist : ERROR:Cannot update volume vol-1
1274148 (900090)  HP -- MSA arrays do not have an ASL and are not recognized as a JBOD
1274177 (1090155) Pri 3/ HP/ VxVM 3.5/290-682-873/ During vxevac, the vxsd command can absorb all nfile resources in kernel
1274185 (1067501) 210-074- 149:HP:JAGag38229:VxVM4.1:'vxdisksetup - iB' incorrectly calculates publen
1274194 (1079281) vxconfigrestore hits awk limitation in cbr_res_main()
1274272 (1189432) (DS6000)vxdmpadm disalbe/enable ctlr will hang all VX command
1274276 (1211302) EVA6k/HP-UX : Slave node panics after disable primary paths.
1299382 (1053529) Unable to import a shared disk group on the DR site
1299403 (1213239) HP:11.31: WILLOW: CVM: Recovery for subvolumes(of a layered volume) does not happen due to missing -f option
1360759 (1260756) vxconfigd core dumps after fix for vxcommands hanging is applied
1360849 (1260757) Master node is getting crashed after reattach the site
1362201 (853822)  master stuck in 'master selection' during random shutdown -r (updown) on 16 node cluster
1362204 (865400)  panic in vol_kmsg_handle_send_err+00035C during shutdown -r and rejoin of 1 node in 16 node cluster
1376234 (1265794) vxvol set doesn't allow changing campus cluster options while the volume is open
1381724 (1321475) Join Failure Panic Loop on axe76 cluster
1415504 (990475)  FMR2 : Oring of DRL Recovery Map with FMR Detach Map when the volume is opened in RWBK mode
1416347 (1416080) System panic in vol_change_disk() routine due to NULL deference.
1416349 (1386980) Panic in vol_putdisk(). Looks like another version of same problem as in e1288427
1422656 (1004746) New TC's for Fmr2.
1427498 (913656)  abort from CBO gets stuck due to deadlock causing safetytimer expiry
1427499 (1133089) HP:11.31:WILLOW:CVM: In consecutive master takeovers, slave state is not reset appropriately
1427500 (1145348) HP:11.31 : WILLOW: Reconfiguration deadlock in master node and passive slaves during DRL Rebuild response
1427503 (1156613) Safety timer expiry due to CVM reconfig taking too long for SG's comfort.
1427504 (1171932) HP:11.31: CVM: master takeover reconfig continues on master but gets interrupted on slaves with a JOIN causing deadlock
1427505 (1168279) volsio stuck in defer Q causing reconfiguration to hang
1427506 (1210957) Vxio hung IO's and uncorrectable write errors
1450039 (1443679) FMR3: I/Os initiating DCO updates for clearing DRL async clear region may not wait for its completion.
1450048 (1246785) Panic in dmp_get_iocount() due to invalid cpu table address.
1450098 (1207898) Upon stop all nodes in the RAC cluster, some stale fencing keys are left from Master node with HDS USP V array
1450934 (1450932) Enhance DMP's delay queue processing logic to avoid infinite retries
1453894 (1453694) System panic in scsi_strategy_real() when an extra paths are added to an existing LUN on the fly.
1459367 (1033534) Enhancements for online and offline disk opertions
1465688 (1461717) 'vxsnap make' command result in vxconfigd and IO sleep too long time
================================





Read and accept Terms of Service