Red Hat ENTERPRISE LINUX 5.5 - S 2010, Руководство пользователя

Страница: 316 / 470

Chapter 5. Known Issues
306
/dev/mapper/3600d0230003414f30000203a7bc41a00p1
/dev/mpath/3600d0230003414f30000203a7bc41a00
/dev/mpath/3600d0230003414f30000203a7bc41a00p1
(BZ#238421)
26
• 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
multipath
state without hanging the command, use
multipath -l
instead.
(BZ#214838)
27
5.6. dmraid
The dmraid packages contain the ATARAID/DDF1 activation tool that supports RAID device discovery,
RAID set activation, and displays properties for ATARAID/DDF1 formatted RAID sets on Linux kernels
using device-mapper.
• The
/etc/cron.d/dmeventd-logwatch
crontab file does not specify the user that the logwatch
process should be executed by. To work around this issue, the functional portion of this crontab
must be changed to:
* * * * * root -/usr/sbin/logwatch ---service dmeventd ---range today ---detail med
(BZ#516892)
28
• The installation procedure stores the name of RAID volume and partition in an initscript. When the
system boots, dmraid enables the RAID partition (that are named implicitly in the init script. This
action functions until the volume and partition names are changed. In these cases, the system may
not boot, and the user is given an option to reboot system and start the rebuild procedure in OROM.
OROM changes the name of RAID volume (as seen by dmraid) and dmraid cannot recognize
the array identified by previous name stored in initscript. The system no longer boots from RAID
partition, since it is not enabled by dmraid. In case of RAID 1 (mirror), the system may be booted
from disk that is part of RAID volume. However, dmraid does not allow to active or rebuild the
volume which component in mounted.
To work around this issue, do not rebuild the RAID array in OROM. Start the rebuild procedure by
dmraid in the operating system, which performs all the steps of rebuilding. dmraid does not change
the RAID volume name, therefore the system can be booted from RAID array without the need of
init script modification.
To modify init script after OROM has started rebuild:
1. Start the system in rescue mode from the installation disk, skip finding and mounting previous
installations.
2. At the command line, find and enable the raid volume that is to be booted from (the RAID
volume and partitions will be activated)
dmraid --ay isw_effjffhbi_Volume0