This means that 3600d0230003414f30000203a7bc41a00 is mapped to two m path 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
Running the multipath command with the -ll option can cause the command to hang if one of the
paths is on a blocking device. Note that the driver does not fail a request after some time if the device
does not respond.
This is caused by the cleanup code, which waits until the path checker request either completes or
fails. To display the current m ultipath state without hanging the command, use m ultipath -l
instead.
Upgrading pm -utils from a Red Hat Enterprise Linux 5.2 Beta version of pm -utils will fail,
resulting in the following error:
error: unpacking of archive failed on file /etc/pm/sleep.d: cpio: rename
To prevent this from occurring, delete the /etc/pm /sleep.d/ directory prior to upgrading. If
/etc/pm /sleep.d contains any files, move those files to /etc/pm /hooks/.
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.
When installing Red Hat Enterprise Linux 5 on a guest, the guest is configured to explicitly use a
temporary installation kernel provided by dom 0. Once installation finishes, it can then use its own
bootloader. However, this can only be achieved by forcing the guest's first reboot to be a shutdown.
As such, when the Reboot button appears at the end of the guest installation, clicking it shuts down
the guest, but does not reboot it. T his is an expected behavior.
Note that when you boot the guest after this it will then use its own bootloader.
Running rpm build on the com piz source RPM will fail if any KDE or qt development packages
(for example, qt-devel) are installed. This is caused by a bug in the com piz configuration script.
To work around this, remove any KDE or qt development packages before attempting to build the
com piz package from its source RPM.
If your system has either ATI Radeon R500 or R600 graphics card equipped, firstboot will not run
after installation. T he system will go directly to the graphical login screen and skip firstboot
altogether. If you attempt to run firstboot manually (i.e. from a failsafe terminal), the X session will
crash.
This issue is caused by the driver used by the ATI Radeon R500/R600 hardware. The default driver
used by these graphics cards are still in technology preview. To work around this, backup your
/etc/X11/xorg.conf file; then, configure X to use the supported vesa driver instead using the
following command:
Kommentare zu diesen Handbüchern