Technical data

The patch README provides instructions on which patches require a reboot.
Note Sun strongly recommends that patch operations are carried out in a single-user mode,
especially when this is recommended by the patch README.
If you are running non-global zones or have lofs disabled, consider the following points when
installing or removing deferred-activation patches:
All non-global zones must be in a halted state for this patch operation. You must halt the
non-global zone before applying the patch.
Deferred-activation patching requires the loopback le system, lofs in order to complete
successfully. Systems running Sun Cluster 3.1 or Sun Cluster 3.2 are likely to have lofs
turned o because of restrictions on HA-NFS functionality when lofs is enabled. Therefore,
before a deferred-activation patch is installed, you must re-enable the loopback le system
by performing the following steps.
1. Remove or comment out the following line in the /etc/system le:
exclude:lofs
2. Reboot your system.
3. Install the patch.
4. After you have completed the patch installation operation, restore or uncomment the
same line from the /etc/system le.
5. Reboot the system to resume normal operations.
No error message is displayed.
Workaround: Sun recommends Solaris Live Upgrade to manage patching. Solaris Live
Upgrade prevents the problems of patching a running system. Solaris Live Upgrade reduces the
amount of downtime involved in patching and reduces risk by providing fallback capability if
problems occur. For more information, see
Solaris 10 5/08 Installation Guide: Solaris Live
Upgrade and Upgrade Planning
.
Possible Error With 32-bit Applications Getting File
System State on Large File Systems (6468905)
When run on large le systems, for example ZFS, applications using statvfs(2) or statfs(2)
to get information about the state of the le system exhibit an error. The following error
message is displayed:
Value too large for defined data type
Workaround: Applications should use statvfs64() instead.
System Administration
Chapter 2 • Solaris Runtime Issues 103