Patch-ID# 105459-04
Keywords: cvm suncluster volume manager
Synopsis: SunCluster 2.1: Patch for the Cluster Volume Manager
Date: Jan/29/99

Solaris Release: 2.5.1 2.6

SunOS Release: 5.5.1 5.6

Unbundled Product: SunCluster

Unbundled Release: 2.1

Relevant Architectures: sparc

BugId's fixed with this patch: 4104327 4114085 4124356 4124916 4126657 4126726 4129451 4144143 4144806 4151066 4155764 4195113

Changes incorporated in this version: 4126726 4144143 4195113

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

[SUNWvxva]
/opt/SUNWvxva/bin/vxva

[SUNWvxvm]
/kernel/drv/vxio
/sbin/vxconfigd
/usr/lib/vxvm/type/gen/vxmake
/usr/lib/vxvm/type/raid5/vxmake
/usr/sbin/vxclust
/usr/sbin/vxmake

[Unbundled]
scripts/fix_lib/sbin/vxconfigd
scripts/fix_lib/usr/lib/vxvm/type/gen/vxmake
scripts/fix_lib/usr/lib/vxvm/type/raid5/vxmake
scripts/fix_lib/usr/sbin/vxclust
scripts/fix_lib/usr/sbin/vxmake
scripts/upgrade_start
scripts/upgrade_finish


Problem Description: 

4126726:
When a disk drive in A5000 is replaced, "vxdisk list" prints duplicate lines
for same DEVICES after "vxdctl enable".  The duplicated DEVICEs is different
from the replaced disk.  If the duplication remains, vxva aborts with
segmentation fault when it is executed.  Before this patch, the duplication
can be removed after rebooting the machine.  Changes have been incorporated
in the vxconfigd to handle this situation properly.

4144143:
If there are two DRL logs (one per plex) associated with data plexes, and
the node on which they are imported crashes during I/O, then during reimport
"vxvol startall" fails (coredumps) with the following message:
  -----------------------------------------------------------------------
  vxvm:vxvol: ERROR:  Volume junkdg.1: Invalid active log magic number
  vxvm:vxvol: ERROR:  Volume junkdg.2: Invalid active log magic number
  vxvm:vxvol: ERROR: gen/vxvol killed by signal 11, core dumped
  -----------------------------------------------------------------------
To compound the problem "vxrecover -sb" fails to start the volumes in the
diskgroup.  vxrecover exits with status zero and does not report any error
message.  So you would not notice the problem until you try to access the
volume, this results in cluster abort.

4195113:
When SC2.1 is started or goes through any reconfiguration, vxiod gets to be 
reseted by vxclust to 10 (default).  It will overwrite any customized 
setting for vxiod.

4155764:
When plexes are detached as a result of I/O failure on one or more disks,
volume manager stores this information in Config copies and/or Logs. If
the diskgroup is deported before the failure is corrected, when detached
disk come back online, it might be auto imported, in the process old/stale
config/log overwrite new/clean config/log. This could lead to loss of
configuration changes and data corruption (as the fact that disk was detached
is lost and no recovery takes place).

4151066:
Volumes with DRL logs created in a specific manner fails to start
with error "Cannot get record from <volume>". Under such circumstance
it is not possible to any volume reconfiguration.

4144806:
Display on VxVA GUI is not updated when disks/volume/plex/subdisk are added
to/removed from the diskgroup.

4129451:
When nodes are joining cluster, during reconfiguration Step 9, following
message appear on the MASTER node :
vxvm:vxconfigd: Cannot issue internal transaction: Configuration daemon error -1
This message was informational (with no consequence) and has been dropped.

4126657:
Sometimes private diskgroup import fails with the message "Internal
configuration daemon error" during reconfiguration step 11, resulting in
logical host not coming up. This can happen if the private diskgroup import
takes place in the middle of a shared diskgroup transaction (transaction
initiated by diskgroup import is rejected as one transaction is in
progress, which is reported as "Internal configuration daemon error").

4124916:
Running upgrade_start script on a Solaris 2.6 machine reports
                      ***  WARNING ***
            You are running Solaris version less than 2.3.

4124356:
Can not encapsulate rootdisk using CVM. Second reboot after vxinstall
fails with message "Cannot mount root on /pseudo/vxio@0:0 fstype ufs".

4114085:
Sometimes vxconfigd coredumps on SLAVE node during reconfiguration step
11. This can happen if a private diskgroup import takes place in the
middle of a shared diskgroup transaction.

4104327:
The visual administrator GUI (vxva) dumps core if you start it under
certain fault conditions. It continues to run if it was started before
the fault (such as disk or controller failure) occurred. It can also be
(re)started after the fault condtions has been corrected.


Patch Installation Instructions: 
-------------------------------- 
Refer to the Install.info file for instructions on using the
generic 'installpatch' and 'backoutpatch' scripts provided with
each patch.  Any other special or non-generic installation
instructions should be described below as special instructions.


Special Install Instructions: 
----------------------------- 
You must use the installpatch that is shipped with this patch to install
this patch.  Do not use patchadd to install this patch.

This patch MUST be installed before attempting to encapsulate root disk.
The system should be rebooted after the patch has been installed. If you
have encapsulated you boot disk, you must run upgrade_start, install this
patch, reboot, run upgrade_finish and reboot to complete the upgrade.

If you NEED to backout this patch, you MUST unencapsulate the root disk
(using upgrade_start script) first, failure to do so will prevent you
from booting off this disk (see bugID 4124356 above). If you backout
this patch, do not run upgrade_finish (as that would attempt to encapsulate
root disk) until you have (re)installed this or an earlier revision of
this patch.
