Installation guide

passphrase. T he init scripts, however, do not support this feature. When booting the system,
entering each individual passphrase for all encrypted devices will be required.
When upgrading openmpi using yum, the following warning may be returned:
cannot open `/tmp/openmpi-upgrade-version.*' for reading: No such file or
directory
The message is harmless and can be safely ignored.
Configuring IRQ SMP affinity has no effect on some devices that use message signalled interrupts
(MSI) with no MSI per-vector masking capability. Examples of such devices include Broadcom
NetXtreme Ethernet devices that use the bnx2 driver.
If you need to configure IRQ affinity for such a device, disable MSI by creating a file in
/etc/modprobe.d/ containing the following line:
options bnx2 disable_msi=1
Alternatively, you can disable MSI completely using the kernel boot parameter pci=nom si.
A bug in the updated /etc/udev/rules.d/50-udev.rules file prevents the creation of
persistent names for tape devices with numbers higher than 9 in their names. For example, a
persistent name will not be created for a tape device with a name of nst12.
To work around this, add an asterisk (*) after each occurrence of the string nst[0-9] in
/etc/udev/rules.d/50-udev.rules.
The smartctl tool cannot properly read SMART parameters from SATA devices.
A bug in previous versions of openm pi and lam may prevent you from upgrading these packages.
This bug manifests in the following error (when attempting to upgrade openm pi or lam :
error: %preun(openmpi-[version]) scriptlet failed, exit status 2
As such, you need to manually remove older versions of openm pi and lam in order to install their
latest versions. T o do so, use the following rpm command:
rpm -qa | grep '^openm pi-\|^lam-' | xargs rpm -e --noscripts --allmatches
When using dm -multipath, if features "1 queue_if_no_path" is specified in
/etc/multipath.conf then any process that issues I/O will hang until one or more paths are
restored.
To avoid this, set no_path_retry [N] in /etc/multipath.conf (where [N] is the number of
times the system should retry a path). When you do, remove the features "1
queue_if_no_path" option from /etc/multipath.conf as well.
If you need to use "1 queue_if_no_path" and experience the issue noted here, use dm setup to
edit the policy at runtime for a particular LUN (i.e. for which all the paths are unavailable).
To illustrate: run dm setup message [device] 0 "fail_if_no_path", where [device] is the
multipath device name (e.g. m path2; do not specify the path) for which you want to change the policy
from "queue_if_no_path" to "fail_if_no_path".
Enabling multiple installed versions of the same kernel module is not supported. In addition to this, a
bug in the way kernel module versions are parsed can sometimes result in enabling an older version
of the same kernel module.
Red Hat recommends that when you install a newer version of an installed kernel module, you should
delete the older one first.
Executing kdum p on an IBM Bladecenter QS21 or QS22 configured with NFS root will fail. T o avoid
this, specify an NFS dump target in /etc/kdump.conf.
9. Known Issues
37