Installation guide

/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. T he function calls
gfs2_dinode_dealloc and shrink_dcache_mem ory 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.
Using the swap --grow parameter in a kickstart file without setting the --maxsize parameter at
the same time makes anaconda impose a restriction on the maximum size of the swap partition. It
does not allow it to grow to fill the device.
For systems with less than 2GB of physical memory, the imposed limit is twice the amount of physical
memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
The gfs2_convert program may not free up all blocks from the GFS metadata that are no longer
used under GFS2. These unused metadata blocks will be discovered and freed the next time
gfs2_fsck is run on the file system. It is recommended that gfs2_fsck be run after the filesystem
has been converted to free the unused blocks. T hese unused blocks will be flagged by gfs2_fsck
with messages such as:
Ondisk and fsck bitmaps differ at block 137 (0x89)
Ondisk status is 1 (Data) but FSCK thinks it should be 0 (Free)
Metadata type is 0 (free)
These messages do not indicate corruption in the GFS2 file system, they indicate blocks that should
9. Known Issues
4 1