Installation of Patch Which Contains File 'libc.so.1' May Fail on Solaris 10 x86 Systems With zfs(1M) as the Root Filesystem

---

Installation of Patch Which Contains File 'libc.so.1' May Fail on Solaris 10 x86 Systems With zfs(1M) as the Root Filesystem

1. Impact

With patch 137138-09 installed on a Solaris 10 x86 system, attempts to install a patch that contains the file 'libc.so.1' may fail when zfs(1M) is the root filesystem. The patch being added to the system may be left partially installed.

Note: If the patch being installed is a Deferred Activation Patch (DAP), upon reboot the system may generate warnings or panic, terminating in single user mode. An example of a DAP patch delivering 'libc.so.1' is 139556-08. Examples of Non-DAP patches delivering 'libc.so.1' are 141415-xx  and 139507-xx.

2. Contributing Factors

This issue can occur in the following release:

x86 Platform

• Solaris 10 with patch 137138-09 and without patch 119255-70

Notes:

1. Solaris 8 and 9 and OpenSolaris and Solaris 10 on the SPARC platform are not impacted by this issue.

2. This issue arises when patch 137138-09 is installed on a system, followed by an attempt to install any patch which delivers 'libc.so.1' (including DAP or Non-DAP).

3. Systems are only affected by this issue if they use a zfs(1M) root filesystem.  To determine if this is the case, the following command can be run:

# df -F zfs
(rpool/ROOT/s10x_u6wos_07b):51991095 blocks 51991095 files

The above shows the response if root is a zfs(1M) filesystem.

If root is not a zfs(1M) filesystem, then the following will be output to the console:

df: Warning: / mounted as a ufs file system

3. Symptoms

Should the described issue occur, errors will appear in the patch log file as shown below:

#tail -7 /var/tmp/139556-08.log.4985

mv: cannot rename /var/run/.patchSafeMode/root/lib/libc.so.1.20102 to /lib/libc.so.1: Device busy
ERROR: Move of /var/run/.patchSafeMode/root/lib/libc.so.1.20102 to dstActual failed
usage: puttext [-r rmarg] [-l lmarg] string
pkgadd: ERROR: class action script did not complete successfully

Installation of <SUNWcslr> failed.

4. Workaround

To avoid this issue until patches can be applied: when attempting to install any patch containing 'libc.so.1' (DAP or Non-DAP), unmount libc(3LIB) before patching the system, using the following command as 'root' user:

#umount /lib/libc.so.1

If this issue has occurred when installing a non-DAP patch, the patch containing 'libc.so.1' should be backed out using the patchrm(1M) command. Then apply the workaround above before installing the patch.

5. Resolution

This issue is addressed in the following release:

x86 Platform

• Solaris 10 with patch 119255-70 or later
  

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.

Modification History

23-Jul-2009: Updated Impact statement for clarification
04-Sep-2009: Updated Contributing Factors and Resolution sections. Now resolved.

Attachments

This solution has no attachment