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.
The latest patch(es) : vm-hpux1131-5.0.1RP3P7 
Sign in if you want to rate this patch.

 Basic information
Release type: P-patch
Release date: 2012-11-26
OS update support: None
Technote: None
Documentation: None
Popularity: 1192 viewed    19 downloaded
Download size: 268.25 MB
Checksum: 3796848418

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

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

This patch is obsolete. It is superseded by: Release date
vm-hpux1131-5.0.1RP3P7 2014-09-25
vm-hpux1131-5.0.1RP3P6 (obsolete) 2014-06-09
vm-hpux1131-5.0.1RP3P5 (obsolete) 2013-12-20

This patch supersedes the following patches: Release date
vm-hpux1131-5.0.1RP3P3 (obsolete) 2012-01-31
vm-hpux1131-5.0.1RP3P1 (obsolete) 2011-05-24
vm-hpux1131-5.0.1RP1P1 (obsolete) 2010-05-06

This patch requires: Release date
sfha-hpux1131-5.0.1RP3 2011-04-04

 Fixes the following incidents:
2575150, 2631371, 2674273, 2753970, 2779347, 2846151, 2860459, 2860462, 2860464, 2872617, 2872633, 2872635, 2872916, 2913666, 2913669

 Patch ID:

 Readme file  [Save As...]
                          * * * READ ME * * *
             * * * Veritas Volume Manager 5.0.1RP3P4 * * *
                          * * * P-patch * * *
                         Patch Date: 2012-11-26

This document provides the following information:


Veritas Volume Manager 5.0.1RP3P4 P-patch


   * Veritas Volume Manager 5.0.1

HP-UX 11i v3 (11.31)

This patch fixes the following Symantec incidents:

Patch ID: PHCO_43185, PHKL_43186

* 2575150 (Tracking ID: 2617277)

Man pages missing for the vxautoanalysis and vxautoconvert commands.

The man pages for the vxautoanalysis and vxautoconvert commands are missing from
the base package.

Added the man pages for vxautoanalysis(1M) and vxautoconvert(1M) commands.

* 2631371 (Tracking ID: 2431470)

1. "vxpfto" command sets PFTO(Powerfail Timeout) value on a wrong VxVM device 
when it passes DM(Disk Media) name to the "vxdisk set" command with -g option.
2. "vxdisk set" command does not work when DA name is specified either -g 
option specified or not. 

  # vxdisk set [DA name] clone=off 
  VxVM vxdisk ERROR V-5-1-5455 Operation requires a disk group 
  # vxdisk -g [DG name] set [DA name] clone=off 
  VxVM vxdisk ERROR V-5-1-0 Device [Da name] not in configuration or associated 
with DG [DG name]

1. "vxpfto" command invokes "vxdisk set" command to set the PFTO value. It 
shall accept both DM and DA names for device specification. However DM and DA 
names can have conflicts such that even within the same disk group, the same 
name can refer to different devices - one as a DA name and another as a DM 
name. "vxpfto" command uses a DM name with -g option when invoking the "vxdisk 
set" command but it will choose a matching DA name before a DM name. This 
causes incorrect device to be acted upon.
Both DM and DA name can be specified for the "vxdisk set" command with -g 
option however the DM name are given preference with -g option from the design 

2. "vxdisk set" command shall accept DA name for device specification.
Without -g option, the command shall work only when DA name is specified. 
However it doesn't work because the disk group name is not extracted from the 
DA record correctly. Hence the first error.
With -g option the DA name specified is treated as a matching DM name wrongly, 
hence the second error.

Code changes are made to make the "vxdisk set" command working correctly on DA 
name without -g option and on both DM and DA names with -g option. The given 
preference is DM name when -g option is specified. It resolves the "vxpfto" 
command issue as well.

* 2674273 (Tracking ID: 2647975)

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 
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

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.

Necessary code changes have been done to ensure that 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.

* 2753970 (Tracking ID: 2753954)

When cable is disconnected from one port of a dual-port FC HBA, only 
paths going through the port should be marked as SUSPECT. But paths going 
through other port are also getting marked as SUSPECT.

Disconnection of a cable from a HBA port generates a FC event. 
When the event is generated, paths of all ports of the corresponding HBA are 
marked as SUSPECT.

The code changes are done to mark the paths only going through the 
port on which FC event is generated.

* 2779347 (Tracking ID: 2779345)

1. Creation of a volume failed on a disk indicating in-sufficient space available.
2. Data corruption seen. CDS backup label signature seen within PUBLIC region data.

Cross Platform Data (CDS) disk uses Solaris VTOC as Platform block. When a disk is
initialized as CDS, geometry obtained from SCSI MODE-SENSE/fake geometry
algorithm is written within the VTOC.
With operations like BCV cloning, firmware upgrade etc, geometry obtained from
MODE-SENSE/fake geometry can be different from the stamped geometry.
If disk size obtained using the geometry stored on disk label is lesser than the
disk size obtained from
MODE-SENSE/fake geometry, operation like creating a volume might fail due to
in-sufficient space available.
If disk size using fake geometry is greater than the disk size obtained from
MODE-SENSE geometry, data corruption might occur if CDS backup label is written
with operation like "vxdisk flush".

The fix is that the geometry on the disk is honored, i.e the geometry used
during initialization will be used for operation like "vxdisk flush".

* 2846151 (Tracking ID: 2108993)

When an existing path/LUN is removed and at the same time new LUN is added on
executing 'vxdisk scandisks' dmp_do_reconfig() reports error and discovery gets
aborted. Following error message is displayed:

VxVM vxconfigd DEBUG V-5-1-0 dmp_do_reconfig: DMP_RECONFIGURE_DB failed: No such
file or directory

'vxdisk list' will not show the newly added disks.

The scenario where the newly added device reuses the device numbers of removed
devices, was not handled in DMP (Dynamic Multi Pathing) code.

The DMP driver has been changed to handle this case.

* 2860459 (Tracking ID: 2257850)

Memory leak is observed when information about enclosure is accessed by vxdiskadm.

The memory allocated locally for a data structure keeping information about the
array specific attributes is not freed.

Code changes are made to avoid such memory leaks.

* 2860462 (Tracking ID: 1874383)

Vxconfigd leaks memory during DMP device reconfiguration.

In vxconfigd code, during device reconfiguration, memory allocated for the
data structures related to device reconfiguration is not freed which led to memory

The memory is released after its scope is over.

* 2860464 (Tracking ID: 1675599)

Vxconfigd leaks memory while excluding and including a Third party Driver
controlled LUN in a loop. As part of this vxconfigd loses its license information
and following error is seen in system log:
        "License has expired or is not available for operation"

In vxconfigd code, memory allocated for various data structures related to
device discovery layer is not freed which led to the memory leak.

The memory is released after its scope is over.

* 2872617 (Tracking ID: 2413763)

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


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.

The node buffer is appropriately initialized using memset() to address the 

* 2872633 (Tracking ID: 2680482)

There are many random directories not cleaned up in /tmp/, like 
vx.$RANDOM.$RANDOM.$RANDOM.$$ on system startup.

In general the startup scripts should call quit(), in which it call do the 
cleanup when errors detected. The scripts were calling exit() directly instead 
of quit() leaving some random-created directories uncleaned.

These script should be restored to call quit() instead of exit() directly.

* 2872635 (Tracking ID: 2792748)

In an HPUX cluster 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.

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.

Code changes are done to avoid closing the wrong file 

* 2872916 (Tracking ID: 2801962)

Operations that lead to growing of volume, including 'vxresize', 'vxassist 
growby/growto' take significantly larger time if the volume has version 20 
DCO(Data Change Object) attached to it in comparison to volume which doesn't 
have DCO attached.

When a volume with a DCO is grown, it needs to copy the existing map in DCO and 
update the map to track the grown regions.  The algorithm was such that for 
each region in the map it would search for the page that contains that region 
so as to update the map. Number of regions and number of pages containing them 
are proportional to volume size. So, the search complexity is amplified and 
observed primarily when the volume size is of the order of terabytes. In the 
reported instance, it took more than 12 minutes to grow a 2.7TB volume by 50G.

Code has been enhanced to find the regions that are contained within a page and 
then avoid looking-up the page for all those regions.

* 2913666 (Tracking ID: 2000661)

The enhanced noreonline needs to take care of diskgroup rename
operation explicitly.

While renaming a shared diskgroup, the master node updates the
on-disk information to reflect rename of diskgroup before actual import. With
NOREONLINE propagated to slaves, the slaves do not refresh the in-core
information belonging to the disks involved in the import operation. So when the
import operation on slaves tries to verify the (new) diskgroup information sent
by the master with the information available in-core, it does not match.

The shared diskgroup import operation explicitly re-onlines the
disks selected for import so that the latest information (if updated by the
master) is available to the slave nodes even if NOREONLINE is specified.

* 2913669 (Tracking ID: 1959513)

The shared diskgroup import times increase drastically with more number
of disks attached to the CVM cluster

As part of regular shared diskgroup import, First the master node
followed by all slaves nodes do re-online of all the disks attached to the
cluster which are not part of any imported diskgroup. With more number of disks
attached to the cluster, the re-online times are higher which causes the import
times to be high as well. diskgroup import command supports a -o noreonline
option to skip the reonline of disks on the master node however the same is not
propogated to slaves. Hence the import times with this option specified are
still on the higher side.

The option to skip reonline of disks during import is propogated to
slave nodes because of which the REONLINE is skipped on entire cluster ensuring
very good shared diskgroup import times.

a)VxVM 5.0.1 (GA)version or version must be installed before applying these

b) All prerequisite/corequisite patches have to be installed.The Kernel patch requires a system reboot for both installation and removal.

c) To install the patch, enter the following command:
   # swinstall -x autoreboot=true -s <patch_directory>   PHCO_43185 PHKL_43186
Incase the patch is not registered, the patch can be registered using the following command:
   # swreg -l depot <patch_directory>  ,
   where  <patch_directory>   is the absolute path where the patch resides.

d) Please do swverify after installing the patches in order to make sure that the patches are installed correctly using:
   $ swverify PHCO_43185 PHKL_43186

a)To remove the patch, enter the following command:
  # swremove -x autoreboot=true PHCO_43185 PHKL_43186


Incidents in 5.0.1 RP3P3 VxVM
2631114 (2272959) vxio V-5-0-0 message missing a space
2631378 (2052459) CFS mount failed on slave node due to registration failure on one of the paths
2626223 (2626199) "vxdmpadm list dmpnode" printing incorrect path-type
2605861 (1398914) recurrence of 'vxdisk -o thin list' not reporting correct SIZE information for XIV luns
2353424 (2334534) In CVM environment, vxconfigd level join is hung when Master returns error "VE_NO_JOINERS" to a joining node and cluster nidmap is changed in new reconfiguration
2631106 (2441937) vxconfigrestore precommit fails with awk errors
2631109 (990338)  FMR Refreshing a snapshot should keep the same name for the snap object
2631112 (2248730) vxdg import command hangs as vxrecover daemon (spawned by vxdg) doesn't close standard error stream
2631359 (2324507) The manpage for vxrelayout(1M) command is incorrect
2631361 (2354046) man page for dgcfgrestore is incorrect.
2631364 (2359814) vxconfigbackup doesn't handle errors well
2631365 (1818780) Oakmont Linux consume many memories during dmp test.
2631367 (2386120) Enhancement request to add diagnostic logging to help triage a CVM master takeover failure situation
2631371 (2431470) vxpfto uses DM name when calling vxdisk, but vxdisk will match DA name first and thus cause corruption
2631375 (2481938) vxconfigbackup throwing an error when DG contains a sectioned disk
2631376 (2492451) vxvm-startup2 launches vxesd without checking install-db.
2658078 (2070531) Campus cluster: Couldn't enable siteconsistency on a dcl volume, when trying to make the disk group and its volumes siteconsistent.

Incidents in 5.0.1 RP3P2 VxVM
2578834 (2566315) vPar6.0 VxVM guest installation deadlock panic
2578576 (2052659) machine with A/A array connected panicked after vm installation
2521084 (2521083) Panic 'Fault when executing in kernel mode' on c8+mpath
2424221 (2423608) panic in vol_dev_strategy()following FC problems
2337436 (2339210) I/O failover from primary to secondary paths and vice-a-versa is very slow on HUAWEI S5600 Series Arrays
2353417 (2349352) During LUN provisioning in single path IO mode environment a data corruption is observed
2578872 (2147922) Thin Reclaim not detected directly for VMAX Microcode Version 5875
2585238 (2585239) vxdisk-alldgs-list running very slow with many lunpaths
2325119 (1545835) vxconfigd core dump during system boot
2324001 (2323925) If rootdisk is encapsulated and if install-db is present, clear warning should be displayed on system boot.
2274277 (1715204) vxsnap operations leads to orphan snap obj in case of any failure occurs during operation, orphan snap object can't be removed.
2581508 (1097258) vxconfigd hung when an array is disconnected
2585238 (2585239) vxdisk-alldgs-list running very slow with many lunpaths
2578872 (2147922) Thin Reclaim not detected directly for VMAX Microcode Version 5875
2578863 (2067319) vxconfgid hung on master when join two slaves are trying to join the cluster
2578858 (2215104) Support thin Provision/reclamation on HP P9500
2578845 (2233611) Hitachi ASL (libvxhdsusp) doesn.t claim the VSP R700 array. This ASL also performs SCSI inquiry on pages 0xE0 and 0xE3 without checking if these pages are supported by the array, this leads to possible warning messages  in array logs.
2578837 (530741)  CVM: vxconfigd assert in commit()
2535859 (2522006) ASL Request for HxRT SF-RAC 5.0.1 HP-UX 11.31 HP P6300/P6500
2528142 (2528133) vxdisk ERROR V-5-1-0 - Record in multiple disk groups
2528119 (2054454) In a configuration where multiple disk groups exist with same DM names across these DG's and an operation like "vxdisk list <DANAME>  " is executed on DA names corresponding to these DM's
2414161 (2067182) vxesd core dumped with SIGILL
2273214 (2233889) Parallel recovery of volumes is not happening if dcl is present.

Incidents in 5.0.1 RP3P1 VxVM
2344566 (2344551) When upgrading VxVM on DRD clone, install-db is created even for encapsulated rootdisk.

Incidents in 5.0.1 GARP3 VxVM 
2198181 (1972755) TP/ETERNUS:No reclaim seen with Stripe-Mirror volume.
2231022 (2029324) /etc/vx/diag.d/vxcvmdiag cvminfo core dumps
2230852 (2204434) SAS disk rootability failing
2231013 (1969526) panic in voldiodone when a hung priv region I/O comes back
2111250 (2078209) resize of vxvm volume resulting in vxconfigd hang -- Need to increase the default value for volpagemod_max_memsz to 64MB
2209175 (2183984) System panic in dmp_update_stats() routine
2169195 (2144891) VX command return very slow when disabling the "active" path.
2230669 (2001827) I/O buffer hung in DMP after repeated path busy errors on its underlying paths.
2230671 (2026773) DMP: vxconfigd hang after array side port disable followed by vxdisk scandisks
2230656 (2077688) I/O hang seen on ALUA arrays under heavy IO load and path failover testing.
2230672 (2165141) vxvm resets b_clock_ticks to zero if I/O hints are passed by vxfs
2266818 (2088426) On shared DG destroy, restrict re-online of disks to only those belonging to the DG.
2247712 (2136046) Needs to log additional information and handle hang case in cvm scripts.
2201136 (2197254) While creating volumes on thinrclm disks, the option "logtype=none" does not work with vxassist command.
2230675 (1734864) vxdg reattachsite fails to clear a detach flag (DM_PFLAG_DETACHED) as part of reattaching the disks back.
2230673 (1594843) CampusCluster: vxdg reattachsite leaves disk group in an unrecoverable state due to inaccessible disks
2204148 (2200670) vxattachd does not recover disks if disk group not imported
2230676 (1263410) vxdg reattachsite leaves disk group in an unrecoverable state due to inaccessible disks
2230674 (1946460) vxdg reattchsite is not doing da-dm assosiation on slave after dg deport-import, when disks are in detached state.
2222105 (839077)  Unable to grow 2.6Tb volume/file system with vxresize due to statvfs() returning EOVERFLOW
2231022 (2029324) /etc/vx/diag.d/vxcvmdiag cvminfo core dumps
2231009 (1528932) vxconfigd asserts in config_db_disable()
2059161 (2027831) vxdg free not reporting free space correctly on CVM master. vxprint not printing DEVICE column for SDs
2235588 (2081662) CX380: ASL could not discover RAID LEVELS with Extended Attributes.
2230668 (2160959) static vold build script not workign for TP ASLs

Incidents in 5.0.1 GARP2 VxVM 
2059167 (1860892) Cache Object corruption when replaying the CRECs during recovery
2059168 (1915356) I/O stuck in vxvm caused cluster node panic
2059166 (1745992) CVR:I/O hang in 4 node CVR cluster
2059303 (2040150) Loss of SCSI-3 PGR Keys during cluster reconfiguration if there are 32 or more keys per LUN.
1956960 (2017120) TP:HP-UX: no reclamation for after executed fsadm -R
1913450 (1840673) After adding new luns one of the nodes in 3 node CFS cluster hangs
2071517 (1741182) Campus Cluster: Detach of DCO in plex detach context exposes serialization hang.
2060312 (1923906) CVM: Master should not initiate detaches while leaving due to complete storage failure.
2039118 (1899688) [VVR]Every I/O on smartsync enabled volume under VVR leaks memory
2071515 (1673937) Campus cluster: When a slave node loses complete storage, all sites can get detached on master.
2059170 (2029735) System panic in volobject_iogen due to null gio_object
2059119 (1513385) VVR:Primary panic during autosync or dcm replay.
2052527 (1957427) SSST: system panic with string 'Can't sleep in interrupt context'
2052524 (1755735) recovery I/Os get broken down to voliomem_chunk_size
2052521 (1089875) Increasing vol_maxio, vol_maxspecialio, and MAXIOSIZE to 1 MB on HP-UX
1937726 (1933970) Restrict the max_specialio tunable value to the permissible limit.
1925842 (1819777) Panic in voldiosio_start() as race window exists while handling duplicate DA records
1670279 (1461717) 'vxsnap make' command result in vxconfigd and IO sleep too long time
2059239 (1954062) vxrecover results in os crash
2092315 (2094627) Campus Cluster : reattachsite on a particular dg enables a disabled volumes and plexes of another dg
2046497 (1665400) vxconfigd sleeps for 1 second between retries which can contribute to the timeout
2071587 (1933528) DR:Disk going to error state after replacing lun.
2075323 (2012344) vxconfigd core dump while adding and removing jbod definition.
2013736 (1950480) DMP: Support of Powerpath 5.1.2 on HP 11.31
2071582 (1982715) vxclustadm dumping core in realloc
2059169 (2013483) vradmind core dumps during VVR setup in FileStore environment
1670283 (1471003) CampusCluster:"vxdg -s import oradg" failed with "requried lock not held in transaction"
2056317 (1594325) need to backout *unit_io and *pref_io changes
2060303 (1880279) Evaluate the need for intelligence in vxattachd to clear stale keys on failover/shared dg's in CVM and non CVM environment.
2059125 (2029480) DG join failure with error "Configuration too large for configuration copies" renders source DG into inconsistent state
1670281 (1470548) CampusCluster:detached site can not be reattached "VxVM vxdg WARNING V-5-1-13835 Disk List is empty for site siteB"
2059155 (1468885) The vxbrk_rootmir script does not complete and is hanging after invoking vxprivutil
2052521 (1089875) Increasing vol_maxio, vol_maxspecialio, and MAXIOSIZE to 1 MB on HP-UX
2049163 (339187)  CVM activation tag in vxprint -m output breaks vxprint
1670291 (1532363) vxdisk 'updateudid' is corrupting diskid. Import of diskgroup fails.
2020060 (2068127) TP: 'vxdisk -o thin list' cannot recognize the size of LUNs greater than 2TB
2071596 (1762561) DMP: System panic when perform excludearray operation with powerpath
2060306 (1650663) Segmentation fault (core dumped) by vxsnap addmir
2059300 (1534379) vxdg split failed with Internal config daemon error

Incidents in 5.0.1 RP1 P1 VxVM
2006417 (2006415) vxdisk init fails on SAS with Kauai. Geometry calculation needs to be changed

Incidents in 5.0.1 GARP1 VxVM
1907686 (1729558) multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption in FMR2
1921537 (1744224) FMR3: multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption
1921516 (1589018) num_retries field is getting re-initialized to initial value leading to looping and delay in error handling time.
1913442 (1531409) Need revisit of DDL reconfiguration code path as NODE_QUIESCE flag
1845132 (1845133) Enable dmp_cache_open
1907654 (1826088) After pulling out FC cables of local site array, plex became DETACHED/ACTIVE
1913513 (1485075) The vxconfigd daemon hangs while it is waiting for an I/O to return.
1936567 (1488399) DMP: Detection of I/O being sent on SCTL device on HP
1702468 (1677416) CVM join & takeover issues in shared A/P storage config due to not breaking more than 64K size kmsgs
1831743 (1804262) VVR:File system I/O of size bigger than 256k fails with error ENXIO after 2TB(> 2G blocks)offset.
1921484 (1835569) Incorrect dropping of messages when the messages arrive out of order during kernel-level join leading to hang/system crash.
1921545 (1822681) memory leak in vxio/voldrl_cleansio_start
1921551 (1733811) System panic on voldco_isdirty code path while doing vxsnap make operation after upgrading from DCO version 10
1907686 (1729558) multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption in FMR2
1944594 (1879520) Issues with changing namingscheme from osn with mode=new to ebn
1921484 (1835569) Incorrect dropping of messages when the messages arrive out of order during kernel-level join leading to hang/system crash.
1877451 (1922543) Need to include dmp alias names in JUMBO API output.
1949219 (1949220) Add Thin Provisioning support to ASLs
1837894 (1834168) vxdisksetup does not set a non-zero return status in case device is in use by LVM.
1921472 (1869002) Introduction of Circular buffer at vold level for master-slave communication.
1907688 (1885582) Installing VxVM on any blade h/w results in error: "Device path not valid"
1921549 (1676061) System panic'd after 2 out of 4 paths to disk were removed.
1907668 (1742702) vxvmconvert fails, probably due to wrong disk capacity calculation
1913447 (1726902) vxconfigd dumped core while trying to choose a path in dmp_dmpdevice_to_pathlist_ebn()
1921584 (1907796) Corrupted Blocks in Oracle after Dynamic LUN expansion and vxconfigd core dump
1921541 (1797540) VxVM: vxdisk resize intermittently causes vxconfigd to dump core.
1921532 (1060336) vxresize should not roll back if fsadm failed but disabled vxfs

Read and accept Terms of Service