Description
Solaris 10 patches 147440-19 through 147440-22 (SPARC) or 147441-19 through 147441-22 (x86) introduce a transition in the way space is allocated for the dump device. At the first reboot after this transition, the space required for the dump is temporarily doubled. For ZFS systems, if there is insufficient free space in the root pool for the doubled space, the dump device will not be configured.
This failure to configure the dump device is silent. The effect is only noticed if, at a later date, the system panics and a dump is not collected.
This is a transition issue in Solaris. Once the workaround below has been implemented or newer patches have been applied, this issue will not recur.
Occurrence
This issue can occur in the following releases:
SPARC Platform
•Solaris 10 with patch 147440-19, 147440-20, 147440-21, or 147440-22 and without patch 147440-23
x86 Platform
•Solaris 10 with patch 147441-19, 147441-20, 147441-21, or 147441-22 and without patch 147441-23
Note 1: Solaris 9 and Solaris 11 are not impacted by this issue.
Note 2: This issue only occurs if there is insufficient space for a temporary doubling of the size of the dump device.
For example, if the system has a dump volume of 16G, then during the next boot after patches 147440-19/147441-19 are applied to the system, there needs to be an additional 16G free in the root pool.
Symptoms
Should the described issue occur, dump is disabled, as shown by running dumpadm(1M):
# dumpadm | grep 'Dump device:'
Dump device: none (dumps disabled)
With dump disabled, if a system panics, a dump will not be collected.
Workaround
To work around this issue, re-configure the dump device after the post-patch reboot of the system. This can be done as 'root' user, as in the following example:
a) To record the old dump device before installing the affected patches, type the following:
# dumpadm | grep 'Dump device:'
b) After the patch is installed, if the dump device has not been configured, re-configure it using the original value of the dump device, as in the following example:
# dumpadm -d <dump-device>
This issue is addressed in the following releases:
SPARC Platform
•Solaris 10 with patch 147440-23 or later
x86 Platform
•Solaris 10 with patch 147441-23 or later
Solaris 10 patches 147440-19 through 147440-22 (SPARC) or 147441-19 through 147441-22 (x86) introduce a transition in the way space is allocated for the dump device. At the first reboot after this transition, the space required for the dump is temporarily doubled. For ZFS systems, if there is insufficient free space in the root pool for the doubled space, the dump device will not be configured.
This failure to configure the dump device is silent. The effect is only noticed if, at a later date, the system panics and a dump is not collected.
This is a transition issue in Solaris. Once the workaround below has been implemented or newer patches have been applied, this issue will not recur.
Occurrence
This issue can occur in the following releases:
SPARC Platform
•Solaris 10 with patch 147440-19, 147440-20, 147440-21, or 147440-22 and without patch 147440-23
x86 Platform
•Solaris 10 with patch 147441-19, 147441-20, 147441-21, or 147441-22 and without patch 147441-23
Note 1: Solaris 9 and Solaris 11 are not impacted by this issue.
Note 2: This issue only occurs if there is insufficient space for a temporary doubling of the size of the dump device.
For example, if the system has a dump volume of 16G, then during the next boot after patches 147440-19/147441-19 are applied to the system, there needs to be an additional 16G free in the root pool.
Symptoms
Should the described issue occur, dump is disabled, as shown by running dumpadm(1M):
# dumpadm | grep 'Dump device:'
Dump device: none (dumps disabled)
With dump disabled, if a system panics, a dump will not be collected.
Workaround
To work around this issue, re-configure the dump device after the post-patch reboot of the system. This can be done as 'root' user, as in the following example:
a) To record the old dump device before installing the affected patches, type the following:
# dumpadm | grep 'Dump device:'
b) After the patch is installed, if the dump device has not been configured, re-configure it using the original value of the dump device, as in the following example:
# dumpadm -d <dump-device>
This issue is addressed in the following releases:
SPARC Platform
•Solaris 10 with patch 147440-23 or later
x86 Platform
•Solaris 10 with patch 147441-23 or later
No comments:
Post a Comment