| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris 10 1/13 Release Notes Oracle Solaris 10 1/13 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris 10 1/13 Release Notes Oracle Solaris 10 1/13 Information Library |
3. Oracle Solaris Runtime Issues
Recommended Adoption of SHA-256 and SHA-512 crypt Plug-ins for Password Encryption
System Might Encounter Data Integrity Issues (15825389)
System Reboots Continuously Because of a ZFS-Related Panic (15809921)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Command Can Sweep Disk Used by ZFS Without Warning (15325067)
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 (15287937)
Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
Hardware-Related Issues and Bugs
SPARC: Dynamic Reconfiguration Operations Fail on an OPL Platform (15725179)
x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (15544691)
The ZFS ARC Allocates Memory Inside the Kernel Cage Preventing DR (15377173)
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
Programs Compiled With Some Options of Oracle Solaris Studio Do Not Run (16237300)
Firefox and Thunderbird Hang in the Hangul Input Method (16043053)
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java Desktop System
x86: Arabic Text Not Appearing in ar Locales
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
System Domain of Interpretation Is Not Configurable (15283123)
IP Forwarding Is Disabled by Default in the Oracle Solaris 10 OS
Oracle Solaris Commands and Standards
Changed Man Pages for Trusted Extensions Are in Reference Manual Only
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
Email and Calendar Application
Problem With Changing Authentication Type (15256650)
User Preferences Not Fully Compatible
x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
System Administration Issues and Bugs
Oracle VTS fputest Fails on Fujitsu M10 Systems (15989998)
Oracle VTS testprobe_ramtest Fails on Fujitsu M10 Systems (15955560)
Oracle VTS testprobe_l3sramtest Fails on Fujitsu M10 Systems (15955589)
Crash Dump Is Saved in the /var/crash Directory (15767302)
Using DISM Might Cause the System to Hang (15807808)
x86: Running the ludelete Command Can Delete Shared Datasets Not Related To the OS (15817477)
Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (15643194)
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
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 1/13 Release
The following Solaris Volume Manager bugs apply to the Oracle Solaris 10 1/13 release.
The bcm_sata SATA HBA driver supports SATA disks and SATA ATAPI devices. The driver supports RD1000, which is a removable SATA ATAPI device. The volume manager (vold) does not create a node when the media in RD1000 does not have valid entries in fdisk. Therefore, the rmformat command does not perform as expected.
Workaround: Use the following workaround:
Turn off the volume manager (vold).
# /etc/init.d/volmgt stop
Run the following commands as needed:
fdisk
rmformat
format
newfs
mount
Restart the volume manager.
# /etc/init.d/volmgt start
If you have a Solaris Volume Manager mirrored root (/) file system in which the file system does not start on cylinder 0, all submirrors that you attach must also not start on cylinder 0.
If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original submirror does not start on cylinder 0, the following error message is displayed:
can't attach labeled submirror to an unlabeled mirror
Workaround: Choose one of the following workarounds:
Ensure that both the root file system and the volume for the other submirror start on cylinder 0.
Ensure that both the root file system and the volume for the other submirror do not start on cylinder 0.
Note - By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) file system somewhere else on the disk. Common system administration practice is to start slice 0 at cylinder 0. Mirroring a default JumpStart installation with root on slice 0 but not cylinder 0 to a typical secondary disk with slice 0 that starts at cylinder 0 can cause problems. This mirroring results in an error message when you attempt to attach the second submirror. For more information about the default behavior of the Oracle Solaris installation programs, see the Oracle Solaris 10 Installation Guides.
|