Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
3. Oracle Solaris Runtime Issues
The rstchown Parameter is Obsolete
Recommended Adoption of SHA-256 and SHA-512 crypt Plug-ins for Password Encryption
Trusted Stripe Disappears From the Screen After a Resolution Change (6460624)
ZFS Dynamic LUN Expansion Restriction (6241086)
The config/local_only Property in sendmail Must Not Be Set to true (6970172)
x86: ata Driver Timeouts During Boot (6586621)
zoneadm install Command Fails With a ZFS Legacy Mount (6449301)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Command Can Sweep Disk Used by ZFS Without Warning (6412771)
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support Issue
ZFS GUI Should Check for /usr/lib/embedded_su Patch at the Beginning of Each Wizard (6326334)
Failure to Synchronize File System on Panic (6250422)
Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
System Crash Dump Fails on Devices Greater Than 1 TByte in Size (6214480)
Hardware-Related Issues and Bugs
SPARC: System Might Hang if the Elastic Policy is Set (6989192)
System Panic Might Occur During DR operations for Crypto (7048323)
SPARC: Disk Warning Is Displayed When Booting the Oracle Solaris OS (7047435)
SPARC: Dynamic Reconfiguration Operations Fail on an OPL Platform (7060498)
x86: System Shuts Down If ata Disks or Controllers Are Replaced on a Running Machine (7059880)
SPARC: System Panic Might Occur When Executing Bulk Crypto Operations on sun4v T3 Machines (7041435)
Message Signaled Interrupt (MSI-X) Cannot Be Retargeted When the apix Module Is Loaded (7058060)
x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (6810093)
The ZFS ARC Allocates Memory Inside the Kernel Cage Preventing DR (6522017)
mpathadm Command Does Not Display Load-Balance Setting Specific to Device
Registration Tool Prevents Power Management on Some Frame Buffers (6321362)
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in the Oracle Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-U.S. English Keyboards
Contention Exists Between Certain Devices That Share the Same Bus (6196994)
Some DVD-ROM and CD-ROM Drives Fail to Boot the Oracle Solaris 10 OS (4397457)
SPARC: Copy Relocation Does Not Work (7083331)
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java Desktop System
New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)
AltGr Key Does Not Work As a Mode Switcher in Some Russian Locales (6487712)
x86: Arabic Text Not Appearing in ar Locales
Several Arabic Fonts Do Not Work in GNOME Desktop (6384024)
Unable to Switch Input Language on Session-Saved Applications (6360759)
Migration Note for UTF-8 Locales
Emails Saved as Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Hardware for Some Keyboard Layouts Type 6 and 7 Not Available
BIND 9.6 Denies Recursion To Non-Local Networks (7046009)
Configuring Tunnels With the Same Source Address (4152864)
System Domain of Interpretation Is Not Configurable (6314248)
IP Forwarding Disabled by Default in the Oracle Solaris 10 OS
Oracle Solaris Commands and Standards
SPARC: Incorrect Results Are Displayed for the cpustat Command on a T4 1.2 Chip
winbind Command Fetches Only the First 1000 Active Directory Users
Changed Man Pages for Trusted Extensions Are in Reference Manual Only
Bash 3.00 No Longer Sets Some Environment Variables
New ln Utility Requires -f Option
New tcsh Version Rejects setenv Variable Names That Use a Dash or an Equal Sign
STDIO getc Family EOF Condition Behavior Change
Output Columns of the ps Command Have Been Widened
Solaris Volume Manager Does Not Remove Devices Correctly If fdisk Does Not Have Valid Entries
Solaris Volume Manager metattach Command Might Fail
Email and Calendar Application
Problem With Changing Authentication Type (6246543)
Wrong Help Window Opened For Volume Control (6253210)
User Preferences Not Fully Compatible
Nautilus ACL MASK Is Not Synchronized With Group Permissions (6464485)
strftime(3c) Should Support GNU Extension in %-m and %-d (6448815)
x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
Certain View Options Might Cause File Manager to Fail (6233643)
Package Database Contains Path Names That Do Not Exist (7054481)
SPARC: 64-bit Version of the libsoftcrypto Library Is Slow (7048794)
patchrm Command Is Not Supported After Applying Patch 144500/144501 (7033240)
lucreate Introduces Latency on Slower UFS Systems (7051757)
The Availability Suite Module sdbc Fails to Load During Boot (6952222)
Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (6952499)
SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software
Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool
Cannot Delete Existing Diskless Clients From the System (6205746)
SPARC: smosservice delete Command Does Not Successfully Remove All Service Directories (6192105)
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 8/11 Release
This section describes system administration bugs in this Oracle Solaris 10 OS.
When you run the pkgchk -n command after an upgrade or after performing a Live Upgrade, you might find that several packages contain path names that do not exist. Because of package history issues, the /var/sadm/install/contents file might not correctly reflect the state of some of the upgraded packages for which the files were removed.
You might see error messages similar to these examples:
ERROR: /usr/jdk/instances/jdk1.6.0/bin/jhsearch pathname does not exist
Workaround: Remove the paths from the contents database.
Make sure you are in single-user mode with the root role.
Remove the paths for any files in the package that cause errors.
# removef package path
Commit the changes.
# removef -f package
For example:
# removef SUNWjhdev /usr/jdk/instances/jdk1.6.0/bin/jhsearch # removef SUNWjhdev /usr/jdk/instances/jdk1.6.0/bin/jhindexer # removef -f SUNWjhdev
The 64-bit version of the libsoftcrypto library runs slowly because it does not use the T4 crypto instructions. As a result, applications that use the 64-bit version of the libsoftcrypto library can encounter performance degradation.
If you install kernel patch 144500 on a SPARC based system or patch 144501 on an x86 based system, the existing ZFS storage pools on the system are upgraded. However, if you use the patchrm command to remove the patch after the root pool is upgraded, the system does not boot because the upgraded pool version does not match the running OS. Therefore, if the root pool is upgraded and the patch is removed, the system does not boot.
If an existing nonroot pool is upgraded and the patch is removed, the SMF local file system service goes into maintenance mode because the local ZFS mounts will fail. Therefore, if a non-root pool is upgraded and the patch is removed, the local ZFS mounts fails.
Caution - Do not remove this kernel update (KU) patch with the patchrm command. |
Performing a live upgrade on a slower UFS system by using the lucreate command takes more time.
In this Oracle Solaris 10 release, the sdbc module fails to load during boot and gives the following error message:
[ID 819705 kern.notice]/usr/kernel/drv/sparcv9/sdbc: undefined symbol WARNING: mod_load: cannot load module 'sdbc'
Workaround: Install patch 123246–07 for SPARC based systems and patch 123247–07 for x86 based systems.
Virtual machines (VMs) that are running Oracle Solaris 10 9/10 guests can be subject to the following problems:
The time of day clock can stop moving forward.
Sleep can hang.
The guest VM can hang entirely.
Workaround: The Oracle Solaris guests must be pinned to physical CPUs. Pin the domain's virtual CPUs to the host's physical CPUs as follows:
# xm vcpu-pin domain vcpu cpus
See the xm(1) man page for more information.
The FKU 137137-xx patch does not support third-party volume manager software, with some exceptions. This lack of support is due to prepatch, postpatch, and postbackout implementation. If you use unsupported third-party volume manager software, you cannot apply the FKU patch. The following error message is displayed during patch installation:
unsupported root slice type xxxxx
Note that the Fujitsu and Veritas Volume Manager software is supported.
Workaround: None.
On systems that have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in AHCI, legacy, or RAID modes. The Oracle Solaris OS supports AHCI and legacy modes.
The SATA mode setting in BIOS must not be changed after an initial Oracle Solaris installation. The SATA mode setting must also not be changed before or after an Oracle Solaris upgrade. If the SATA mode BIOS setting is modified after the Oracle Solaris 10 OS is installed, the system will reset and fail to boot without indicating what led to the failure.
Workaround: If a boot failure occurs as a result of changing the BIOS setting, revert back to the original setting in order to boot the Oracle Solaris OS.
When run on large file systems, for example, ZFS, applications using the statvfs(2) or statfs(2) functions to get information about the state of the file system exhibit an error. The following error message is displayed:
Value too large for defined data type
Workaround: Applications should use the statvfs64() function instead.
On systems running an Oracle Solaris OS release that is not zones aware, using the patchadd -R command, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.
In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this case.
There is no indication that the -R option did not work. As a result of the failure of the command, Oracle Solaris 10 packages or patches are not installed on any of the installed non-global zones.
This problem occurs while you are installing and uninstalling packages or patches.
Note - The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether any installed non-global zones are used as the alternate root path, restrict the use of the -R option in all cases.
For more information, see the following man pages :
Choose one of the following workarounds.
Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.
If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:
SPARC: Patch ID 119254-19
x86: Patch ID 119255-19
Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.
Instead, boot the alternate root, for example, the Oracle Solaris 10 release, as the active OS. Then install and uninstall the Oracle Solaris 10 packages and patches without using the -R option.
A system that runs Sun Patch Manager 2.0 can manage remote systems that run Patch Manager, including Sun Patch Manager 1.0.
However, a system with an earlier version of Patch Manager cannot manage remote systems that run Patch Manager 2.0. Earlier versions include the following:
Sun Patch Manager Base Software 1.x
Sun Patch Manager 1.0
Note - Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.
If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:
Failing with error EXM_BMS.
Workaround: Unshare the /export partition before adding the diskless client.
If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.
Workaround: Follow these steps:
Make sure that no clients exist that use the service.
# unshare /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/.copyofSolaris_10_sparc.all # rm -rf /export/.copyofSolaris_10 # rm -rf /export/Solaris_10 # rm -rf /export/share # rm -rf /export/root/templates/Solaris_10 # rm -rf /export/root/clone/Solaris_10 # rm -rf /tftpboot/inetboot.sun4u.Solaris_10
If this file server does not provide functions or resources for any other services, remove the following entry from the /etc/bootparams file.
fs1-24 boottype=:os
Remove the following entry from the /etc/dfs/dfstab file.
# share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr
Modify the /var/sadm/system/admin/services/Solaris_10 file.
If the file server is not running the Oracle Solaris 10 OS, delete the file.
If the file server is running the Oracle Solaris 10 OS, remove all entries after the first three lines. The deleted lines specify the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.