Patch-ID# 109970-12
Keywords: single user hang shutdown init SUNWscm scmadm display mc_rms rammc
Synopsis: Data Services 2.0 Core: Core Patch
Date: Mar/01/2002

Solaris Release: 8

SunOS Release: 5.8

Unbundled Product: Data Services Core

Unbundled Release: 2.0

Xref: 

Topic: 

Relevant Architectures: sparc.sun4u
NOTE:
			IMPORTANT NOTICE:  
************************************************************************
* When installing Data Services 2.0 patches, be sure to install ALL    * 
* Data Services patches, closely following the installation steps      * 
* documented in this README file, prior to performing a system reboot. *
************************************************************************
	NOTE:  	SPECIAL INSTALLATION INSTRUCTIONS FOR DATA SERVICES PATCHES
	       	Because this patch updates kernel modules, the user must 
		boot the system up in single-user mode to apply the patch,
	 	and then reboot the system.
		This patch must be installed from a read/write directory.  
		It is highly recommended that the patch directory be copied 
		to /tmp on the machine being patched and installed from 
		there.
		1) Boot the machine into single user mode
		2) Install the Core patch first  
   			example  #patchadd 109967-09
		3) Install the latest product patch after installing 
		   Core patch
			example  #patchadd 109983-08
		4) Repeat Step 3 for all installed Data Services
		   products
			example  #patchadd 109975-07
		5) Reboot the system after you complete adding the patches.
        NOTE:   If you are running SNDR 2.0, there is a chance that the 
                system will hang during shutdown from single-user mode due 
                to certain module dependencies.  To avoid this, execute the 
                following command from single-user mode BEFORE issuing the 
                shutdown command:
                # /usr/opt/SUNWesm/sbin/rdcadm -p
        NOTE:   If you are using Instant Image 2.0 or Fast Write Cache 2.0
                with Component Manager 2.2, it is recommended that the
                Instant Image and Fast Write Cache command line interface
                (CLI) be used in place of the Sun StorEdge Management 
                Console.
	NOTE: 	Refer to "Patch Installation Instructions" section for 
		generic information on installing this patch.
	NOTE: 	Refer to "Special Product Install Instructions" section 
		for information on installing Data Services products.

BugId's fixed with this patch: 4288525 4337401 4342772 4345262 4350378 4351940 4353608 4354436 4357687 4365611 4375102 4399212 4399221 4401671 4416884 4422621 4431481 4470319 4472080 4475159 4479665 4494556 4505017 4521096 4532737

Changes incorporated in this version: 4431481 4479665 4494556 4505017 4521096 4532737

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: 

/etc/init.d/sv
/usr/kernel/drv/mc_rms
/usr/kernel/drv/nsctl
/usr/kernel/drv/nskern
/usr/kernel/drv/rammc
/usr/kernel/drv/sdbc
/usr/kernel/drv/sdbc.conf
/usr/kernel/drv/sparcv9/mc_rms
/usr/kernel/drv/sparcv9/nsctl
/usr/kernel/drv/sparcv9/nskern
/usr/kernel/drv/sparcv9/rammc
/usr/kernel/drv/sparcv9/sdbc
/usr/kernel/drv/sparcv9/sv
/usr/kernel/drv/sv
/usr/kernel/drv/sv.conf
/usr/kernel/misc/sparcv9/spuni
/usr/kernel/misc/spuni
/usr/opt/SUNWesm/SUNWscm/sbin/nscadm
/usr/opt/SUNWesm/SUNWscm/sbin/scmadm
/usr/opt/SUNWesm/SUNWspsv/sbin/svadm
/usr/opt/SUNWscm/lib/nskernd
/usr/opt/SUNWscm/sbin/sd_stats 
<install_dir>/SUNWesm/SUNWspcsl/lib/classes/libspcs.jar
<install_dir>/SUNWesm/SUNWspcsl/lib/libspcs.so

Problem Description:

4532737 System hangs when SNDR tries to sync an IDE based disk partition
4521096 DS 2.0 core-12 patch breaks the hard links to /etc/init.d/sv
4505017 Cannot open /dev/nsctl at scm start
4494556 109969-11 preinstall fails patch level error
4479665 The scmadm command output limits volume display to 13 characters
4431481 Can't do an init 6 from single user mode - shutdown scripts hang or timeout
 
(from 109970-11)
 
4475159 Possible data corruption when filesystem not newfs prior to entering SV layer
 
(from 109970-10)
 
4472080 fsck BAD SUPER BLOCK with latest Data Services patches. (with or without FWC)
4470319 DS allows I/O beyond end of volume
 
(from 109970-09)
 
4422621 II 2.0: Write Performance Down
4399221 SV layer appears to serialize async I/O
4399212 SV layer impacts performance for seq I/O - UFS or VxVm/VxFS
 
(from 109970-08)
 
4416884 Oracle hangs when using SNDR to replicate raw devices
 
(from 109970-07)
 
4401671 apparent bad II vol state causes iiadm -u s SHADOW to not return until complete
4375102 sv/ii/sndr deadlock
 
(from 109970-06)
 
NoBugID No bugs fixed
 
(from 109970-05)
 
4351940 fwcadm cache -s or scmadm -S and Management Console stats do not match
 
(from 109970-04)
 
4365611 Data services not working on Solaris 8 10/00 or with KU 108528-03
 
(from 109970-03)
 
NoBugID Updates to README file
 
(from 109970-02)
 
4357687 "umount volumes; disable sv volumes" still leaves volumes open
 
(from 109970-01)
 
4354436 512 volume limitation
4353608 zeroing buf_t b_forw,b_back after buf freed
4350378 WARNING: sdbc(ASSERT_LEN) fba exceeds limits. fba_len 4032. Max 1024
4345262 Multiple 25GByte II independent volume copy causes JNI-panic & esm_gui lock up
4342772 deconfiguring sv while writing to devices causes IO errors
4337401 Data corruption during a normal reboot
4288525 enable exceptions wrong

Patch Installation Instructions:
--------------------------------
For Solaris 7-8 releases, refer to the man pages for instructions on
using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.  The following example
installs a patch to a standalone machine:
 
        example# patchadd /var/spool/patch/104945-02
 
The following example removes a patch from a standalone system:
 
        example# patchrm 104945-02
 
For additional examples please see the appropriate man pages.
 
Special Product Install Instructions: 
------------------------------------- 
 
PRODUCT INSTALLATION INSTRUCTIONS - ADDING DATA SERVICES
 
	NOTE:	The following section applies to customers who currently 
		have one or more Data Services products installed, have 
		patched those products one or more times, and wish to add 
		an additional Data Services product.  If this is a new 
		installation of Data Services products, go to the next 
		section entitled, "PRODUCT INSTALLATION INSTRUCTIONS - 
		NEW INSTALLATION.
 
For installation of additional Data Services 2.0 products on a 
system that has existing Data Services patches installed:
 
	1) Determine if existing Data Services products were loaded 
	   from original 2.0 CD or from re-released 2.0 CD.  To 
	   determine this:
 
        	1a) Run the following for the appropriate OS:
 
                        Command                              OS
                        -------------------------------------------
                        showrev -p | grep 109967-06     Solaris 2.6
                        showrev -p | grep 109969-06     Solaris 7
                        showrev -p | grep 109970-06     Solaris 8
 
                        o If the patch does not exist, go to step 2).
 
                        o If the patch exists, go to step 1b).
 
		1b) Run the following for the appropriate OS:
 
                        Command                              OS
                        -------------------------------------------
                        ls -d /var/sadm/patch/109967-06  Solaris 2.6
                        ls -d /var/sadm/patch/109969-06  Solaris 7
                        ls -d /var/sadm/patch/109970-06  Solaris 8
 
                        o If the directory exists, remove all the Data 
                          Services patches as directed in step 2).
 
                        o If the directory does not exist, remove all 
                          the -07 and higher revisions of the Data 
                          Services patches as directed in step 2).  Do 
                          not attempt to remove any -06 or lower 
                          revisions of the Data Service patches.
 
	2) Back out all the Data Services patches using the patchrm 
	   command.  The Data Services patch numbers are:
 
                        Solaris 2.6:
                                Core:           109967-XX
				FWC:            109971-XX
                                Instant Image:  109975-XX
                                SNDR:           109979-XX
                                STE:            109983-XX
                        Solaris 7:
                                Core:           109969-XX
				FWC:            109973-XX
                                Instant Image:  109977-XX
                                SNDR:           109981-XX
                                STE:            109985-XX
                        Solaris 8:
                                Core:           109970-XX
				FWC:            109974-XX
                                Instant Image:  109978-XX
                                SNDR:           109982-XX
                                STE:            109986-XX
 
	3) Reboot the system into single user mode
	4) Install additional 2.0 Data Services product(s)
	5) Reinstall the appropriate patches (numbers listed above)
	6) Reboot the system
 
 
PRODUCT INSTALLATION INSTRUCTIONS - NEW INSTALLATION
 
	NOTE:	The following applies to customers who currently have 
		no Data Services patches installed.  If Data Services 
		have already been installed and patched one or more 
		times, go to the previous section entitled, "PRODUCT 
		INSTALLATION INSTRUCTIONS - ADDING DATA SERVICES."
 
For installation of Data Services 2.0 products on a system that has no 
Data Services products previously installed:
 
	1) Install ALL desired Data Services 2.0 products
	2) Install ALL Data Services patches (including core patch) for 
	   the installed 2.0 Data Services
	3) Reboot the system
 
 
Additional Information:
-----------------------
 
A new tunable has been introduced in this patch, which is included
in the file sv.conf. It is called sv_threads and its description
is as follows:
 
 sv_threads
 
 The number of threads allocated when loading the sv kernel module.
 The value should be set to at least (2 * number of device in sv.cf).
 
 However, if lots of asynchronous (including filesystem) i/o is
 anticipated increasing this value may improve performance.
 
** NOTE **
Sv_threads default value is 64, which Data Services Engineering
believes should be adaquate for most configurations. 
 
If there is a need to increase this value, it is recommended
to increase by a factor of X2 and monitor for improvement.
For example increase from 64 -> 128 and determine if there
is an improvement in I/O performance. 
 
Sv_threads maximum setting is directly proportional to the
amount of physical memory available when SV intializes.
Each thread allocated consumes approximately 30KB of memory.
 
For customers installing FWC for the first time on Solaris 8 10/00 (or kernel 
update 108528-03 or higher), please use the following instructions:
 
1) Boot the machine into single user mode 
 
2) Install FWC in single user mode per the instructions in the FWC 2.0 
Installation and User's Guide  
 
3) Install the core patch 109970-12 in single user mode before rebooting the 
machine.
 
4) Reboot the machine into multi-user mode.
 
For customers who have already installed FWC on Solaris 8 10/00 (or kernel 
update 108528-03 or higher) and performed a full reboot without having applied 
the core patch 109970-12, please use the following instructions:
 
If you are seeing the following message during the reboot:
 
MOBoot: ERROR: class com.sun.esm.mo.cache.CacheMOImpl could not be started - exception thrown by method com.sun.esm.mo.cache.CacheMOImpl.adminStart()
 
1) Boot the machine into single user mode
 
2) Remove the mo and mc persistence files:
 
 	rm -r /var/opt/SUNWesm/mc/*
	rm -r /var/opt/SUNWesm/mo/*
 
3) Install the core patch 109970-12 in single user mode.
 
4) Reboot the machine into multi-user mode.
 
(MCBoot and MOBoot errors relating to the LOG service might 
appear as the machine is coming down, but will be corrected 
as the machine starts up again and the persistence files are 
recreated)

Special Install Instructions:
-----------------
None.

README -- Last modified date:  Friday, March 1, 2002

