9. Known Issues

9.1. All Architectures

Bugzilla #484117
The Logical Volume Manager in Red Hat Enterprise Linux 4.8 reports file descriptor leaks, resulting in the following error returned to the installation output: 
				File descriptor NUM (socket:XXXX) leaked on lvm invocation.
This message can be safely ignored.
Bugzilla #468097
When installing Red Hat Enterprise Linux 4 through an Network File System (NFS) server, the installer is unable to correctly close the NFS mount points. This might cause the NFS server to misbehave. In these cases Red Hat suggests the use of an HTTP server for installations.
Bugzilla #468097
On systems where the BIOS is able to do both legacy (acpiphp) and native (pciehp) PCI hotplugging, it is necessary for the administrator to choose a preferred method and explicitly prevent Red Hat Enterprise Linux 4 from loading the module for the undesired method. This is done by blacklisting the undesired module in /etc/modprobe.conf.
Bugzilla #451164
Hardware testing for the Mellanox MT25204 has revealed that an internal error occurs under certain high-load conditions. When the ib_mthca driver reports a catastrophic error on this hardware, it is usually related to an insufficient completion queue depth relative to the number of outstanding work requests generated by the user application.
Although the driver will reset the hardware and recover from such an event, all existing connections at the time of the error will be lost. This generally results in a segmentation fault in the user application. Further, if opensm is running at the time the error occurs, then you need to manually restart it in order to resume proper operation.
Bugzilla #443795
A bug in previous versions of openmpi and lam may prevent you from upgrading these packages. This same bug may cause up2date to fail when upgrading all packages.
This bug manifests in the following error when attempting to upgrade openmpi or lam: 
error: %preun(openmpi-[version]) scriptlet failed, exit status 2
This bug also manifests in the following error (logged in /var/log/up2date) when attempting to upgrade all packages through up2date: 
up2date Failed running rpm transaction - %pre %pro failure ?.
As such, you need to manually remove older versions of openmpi and lam first in order to avoid these errors. To do so, use the following rpm command:
rpm -qa | grep '^openmpi-\|^lam-' | xargs rpm -e --noscripts --allmatches
Bugzilla #430494
When a LUN is deleted on a configured storage system, the change is not reflected on the host. In such cases, lvm commands will hang indefinitely when dm-multipath is used, as the LUN has now become stale.
To work around this, delete all device and mpath link entries in /etc/lvm/.cache specific to the stale LUN. To find out what these entries are, run the following command:
ls -l /dev/mpath | grep <stale LUN>
For example, if <stale LUN> is 3600d0230003414f30000203a7bc41a00, the following results may appear: 
lrwxrwxrwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4
lrwxrwx--rwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
This means that 3600d0230003414f30000203a7bc41a00 is mapped to two mpath links: dm-4 and dm-5.
As such, the following lines should be deleted from /etc/lvm/.cache: 
dev/dm-4 
dev/dm-5 
dev/mapper/3600d0230003414f30000203a7bc41a00
dev/mapper/3600d0230003414f30000203a7bc41a00p1
dev/mpath/3600d0230003414f30000203a7bc41a00
dev/mpath/3600d0230003414f30000203a7bc41a00p1
Bugzilla #195685
If you need to use the hp_sw kernel module, install the updated device-mapper-multipath package.
You also need to properly configure the HP array to correctly use active/passive mode and recognize connections from a Linux machine. To do this, perform the following steps:
  1. Determine what the world wide port name (WWPN) of each connection is by using show connections. Below is a sample output of show connections on an HP MSA1000 array with two connections: 
    Connection Name: <Unknown>
Host WWNN = 200100E0-8B3C0A65
Host WWPN = 210100E0-8B3C0A65
Profile Name = Default
Unit Offset = 0
Controller 2 Port 1 Status = Online

Connection Name: <Unknown>
Host WWNN = 200000E0-8B1C0A65
Host WWPN = 210000E0-8B1C0A65
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Online
  2. Configure each connection properly using the following command:
    add connection [connection name] WWPN=[WWPN ID] profile=Linux OFFSET=[unit offset]
    Note that [connection name] can be set arbitrarily.
    Using the given example, the proper commands should be:
    add connection foo-p2 WWPN=210000E0-8B1C0A65 profile=Linux OFFSET=0
    add connection foo-p1 WWPN=210100E0-8B3C0A65 profile=Linux OFFSET=0
  3. Run show connections again to verify that each connection is properly configured. As per the given example, the correct configuration should be: 
    Connection Name: foo-p2
Host WWNN = 200000E0-8B1C0A65
Host WWPN = 210000E0-8B1C0A65
Profile Name = Linux
Unit Offset = 0
Controller 1 Port 1 Status = Online

Connection Name: foo-p1
Host WWNN = 200100E0-8B3C0A65
Host WWPN = 210100E0-8B3C0A65
Profile Name = Linux
Unit Offset = 0
Controller 2 Port 1 Status = Online
Bugzilla #449648
Red Hat discourages the use of quota on EXT3 file systems. This is because in some cases, doing so can cause a deadlock.
Testing has revealed that kjournald can sometimes block some EXT3-specific callouts that are used when quota is running. As such, Red Hat does not plan to fix this issue in Red Hat Enterprise Linux 4, as the modifications required would be too invasive.
Note that this issue is not present in Red Hat Enterprise Linux 5.
Bugzilla #451164
Hardware testing for the Mellanox MT25204 has revealed that an internal error occurs under certain high-load conditions. When the ib_mthca driver reports a catastrophic error on this hardware, it is usually related to an insufficient completion queue depth relative to the number of outstanding work requests generated by the user application.
Although the driver will reset the hardware and recover from such an event, all existing connections at the time of the error will be lost. This generally results in a segmentation fault in the user application. Further, if opensm is running at the time the error occurs, then you need to manually restart it in order to resume proper operation.
Bugzilla #452578
The Desktop Sharing connection icon displays its context menu when you double-click it, not when you right-click it. All other icons display their context menus when you right-click on them.
Bugzilla #451873
If the ib_ehca InfiniBand driver is loaded in port auto-detection mode (using module parameter nr_ports=-1), the IP-over-InfiniBand network interfaces (ibX) might become available too late. When this occurs, the ifup ibX command issued from the openibd startup script will fail; consequently, the ibX interface will not become available.
When this occurs, use the command rcnetwork restart to fix the problem.
Bugzilla #451873
In the IBM Redbook "Implementing InfiniBand in IBM System p (SG247351) manual, Table 6-3 (on page 220 of the PDF version) describes debug code bit definitions, where several HCA error indicator bits are also described.
Note that with eHCA2 adapters, bits 46 and 47 of these error indicator bits might return false positives.
Bugzilla #366961
On HP ICH10 workstations, audio is only enabled through the front 3.5mm jacks. As such, to receive any audio output or use recording, you should plug in your headphones, speakers, or microphones to the front jacks. At present, the rear jacks, internal speaker, and master volume for this workstation do not work.
Bugzilla #429727
With this update, the default PCI detection and ordering mode for the following models have changed:
  • HP Proliant DL 580 G5
  • HP Proliant DL 385 G2
  • HP Proliant DL 585 G2
These models use a device scanning and enumeration mode which is not the default for Red Hat Enterprise Linux 4 or 5. The mode used by these HP Proliant models could result in add-on cards being detected and added prior to onboard/internal devices. This unexpected ordering could cause difficulties when installing new instances of Red Hat Enterprise Linux, adding hardware, and maintenance.
The numbering of network interface cards (NIC) for the aforementioned HP Proliant models may change when they are updated with the Red Hat Enterprise Linux 4.7 kernel. The installer changes NIC numbering if the HWADDR=MAC ADDRESS parameter is not defined in /etc/sysconfig/network-scripts/ifcfg-eth[X] for each installed NICs. As such, Red Hat recommends that you ensure this parameter is defined in order to avoid any problems arising from an unexpected NIC enumeration.
In addition, to avoid any NIC enumeration changes after updating these HP Proliant models to Red Hat Enterprise Linux 4.7, add the kernel boot parameter pci=nobfsort to /boot/grub/grub.conf.
Bugzilla #232499
When a volume group contains a mirror or snapshot, issuing the lvchange command with a volume group parameter may result in the following error messages: 
Unable to change mirror log LV fail_secondary_mlog directly
Unable to change mirror image LV fail_secondary_mimage_0 directly
Unable to change mirror image LV fail_secondary_mimage_1 directly
These messages can be safely ignored.
Bugzilla #441870
Dell PowerEdge SC1435s systems may hang during boot-up. To avoid this, edit the terminal line in grub.conf and replace the string serial console with console serial.
Bugzilla #456533
The updated ixgbe driver does not support the Intel 82598AT (Copper Pond 10GbE).
Bugzilla #454872
Red Hat Enterprise Linux 4.8 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.
Bugzilla #479467
There is a known memory leak with the res_n* family of resolver routines (i.e. res_nquery, res_nsearch and res_nmkquery). Programs that use these functions will leak memory over time. It has been fixed in newer versions of glibc, however, the fix is too invasive to be applied to Red Hat Enterprise Linux 4. Programs that use these functions may need to be restarted occasionally to free memory.
Bugzilla #452513
The number of devices that can be handled during installation of Red Hat Enterprise Linux 4 depends on the size of the installation initrd image. Therefore, in situations where there are many devices attached to a machine (such as heavily populated Fibre Channel setups) installation will not be possible unless number of visible devices is reduced.
Bugzilla #438895
The aacraid driver update that was first introduced in Red Hat Enterprise Linux 4.7 requires up to date Adaptec PERC3/Di firmware. Subsequent updates of Red Hat Enterprise Linux 4 (including this 4.8 update) require, that the PERC3/Di firmware is at version 2.8.1.7692, A13 or newer. The firmware may be obtained at the following location:
http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R168387&SystemID=PWE_PNT_PIII_1650&servicetag=&os=WNET&osl=en&deviceid=1375&devlib=0&typecnt=0&vercnt=9&catid=-1&impid=-1&formatcnt=4&libid=35&fileid=228550
Bugzilla #492371
During installation anaconda may not remove all the Logical Volume Manager (LVM) metadata that exists on a system prior to installation. This extra metadata may cause LVM tools to report missing volume groups or logical volumes after installation. To work around this issue, remove the stale LVM metadata after the installation is complete.
Bugzilla #481190
multipath does not silence the error messages printed by any of it's callout programs. Therefore, if multipath is run when paths are down, various error messages may be displayed. The messages that are displayed depend on the specific callout programs that multipath is using. For example, if multipath is run while there are failed scsi devices, scsi_id will print 
lt;H>:<B>:<T>:<L>:Unable to get INQUIRY vpd 1 page 0x0.
lt;H>:<B>:<T>:<L>:sg_io failed status 0x0 0x1 0x0 0x0
Or, if multipath -ll is run while an EMC CLARiiON is down, the mpath_prio_emc priority callout will print query command indicates error