Red Hat ENTERPRISE LINUX 5.5 - TECHNICAL NOTES Manual page 139

configured to send it via the bonded interface works as expected, and the resulting core is transferred
successfully. (BZ#532030
* kdump could create a truncated or zero-length vmcore file on large-memory systems. This was due
to the amount of system RAM causing the creation of more than thirty-two E820 map entries in the
BIOS, which in turn led kexec to truncate that list, thus causing memory to be ignored during kdump
boot, and eventually resulting in truncated or zero-length vmcore files. With this update, kdump is now
aware of this potential situation on large-memory systems, with the result that vmcore files are created
correctly, without being truncated or zero in length.
All users of kexec-tools are advised to upgrade to this updated package, which resolves these issues.
1.89.2. RHBA-2010:0179: bug fix update
An updated kexec-tools package that fixes numerous bugs is now available.
kexec-tools provides kexec binary that facilitates a new kernel to boot using the kernel's kexec
feature either on a normal or a panic reboot, together with ancillary utilities that form the userspace
component of the kernel's kexec feature
This update addresses the following issues:
* previously, the kdump kernel command line supported a "mem=" parameter that limited the memory
that was dumped. When this parameter was set, the dump would result in an I/O error. The "mem="
parameter has been removed from kexec to ensure that core dumps succeed.
* previously kdump waited indefinitely for all devices in its critical_disks list to be available before it
performed a dump. Kexec-tools now has a disk_timeout parameter that limits how long kdump will wait
for storage to respond.
* a logical flaw meant that the presence of files with certain names in current directory of mkdumprd
would prevent a dump. The code used to evaluate the remote server name has been corrected.
1200
(BZ#509404 )
* host names specified in the kdump.conf script needs to be entered as fully-qualified domain names
to allow for DNS changes. The documentation for kdump has been revised to make this requirement
1201
clear. (BZ#510816 )
* previously, the vmcore file created by starting kdump with an initscript used the "--sparse=always"
option when copying, resulting in a smaller file. The same option has now been added as a
default value in the kdump.conf configuration file, ensuring that the default behavior is consistent.
1202
(BZ#511003 )
* previously, faulty logic in the code that cleans up files used by kdump in /tmp meant that files were
sometimes left behind in /tmp. This has been corrected to ensure that files in /tmp are cleaned up.
1203
(BZ#512098 )
1196
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=532030
1197
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=533793
1198
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239791
1199
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=500741
1200
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=509404
1201
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=510816
1202
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=511003
1203
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=512098
1196
)
1199
(BZ#500741 )
RHBA-2010:0179: bug fix update
1197
(BZ#533793 )
1198
(BZ#239791 )
129