Red Hat ENTERPRISE LINUX 5.3 - RELEASE MANIFEST, Руководство по выпуску, Страница: 46 / 240

Release Notes
46
• If the
edac
module is loaded, BIOS memory reporting will not work. This is because the
edac
module clears the register that the BIOS uses for reporting memory errors.
The current Red Hat Enterprise Linux Driver Update Model instructs the kernel to load all available
modules (including the
edac
module) by default. If you wish to ensure BIOS memory reporting on
your system, you need to manually blacklist the
edac
modules. To do so, add the following lines to
/etc/modprobe.conf
:
blacklist edac_mc
blacklist i5000_edac
blacklist i3000_edac
blacklist e752x_edac
• Red Hat Enterprise Linux 5.3 can detect online growing or shrinking of an underlying block device.
However, there is no method to automatically detect that a device has changed size, so manual
steps are required to recognize this and resize any file systems which reside on the given device(s).
When a resized block device is detected, a message like the following will appear in the system
logs:
VFS: busy inodes on changed media or resized disk sdi
If the block device was grown, then this message can be safely ignored. However, if the block
device was shrunk without shrinking any data set on the block device first, the data residing on the
device may be corrupted.
It is only possible to do an online resize of a filesystem that was created on the entire LUN (or
block device). If there is a partition table on the block device, then the file system will have to be
unmounted to update the partition table.
• If your system has a GFS2 file system mounted, a node may hang if a cached inode is accessed
in one node and unlinked on a different node. When this occurs, the hung node will be unavailable
until you fence and recover it via the normal cluster recovery mechanism. The function calls
gfs2_dinode_dealloc
and
shrink_dcache_memory
will also appear in the stack traces of any
processes stuck in the hung node.
This issue does not affect single-node GFS2 file systems.
• The following message may be encountered during system boot:
Could not detect stabilization, waiting 10 seconds.
Reading all physical volumes. This may take a while...
This delay (which may be up to 10 seconds, dependant on the hardware configuration) is necessary
to ensure that the kernel has completed scanning the disks.
• The current implementation of
User Payload Access
in
ipmitool
allows you to configure devices,
but does not allow you to retrieve the current settings for those devices.