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

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

RHBA-2010:0295: bug fix and enhancement update
171
SCSI device, being written to the
/init
script preventing the system from booting. The local
variable has been renamed to avoid the conflict. Running
mkinitrd
on a multipath boot system
now results in a successful boot of the system. (
BZ#503567
1466
)
•
mkinitrd
runs
nash
on each logical volume. The
block_find_fs_by_key()
method calls
the
nashDmGetDevName()
method for each logical volume. The
nash
command does not run to
completion in a reasonable time-frame as the
nashDmGetDevName()
recurses through all devices
each time it is called. This update allows
nashDmGetDevName()
to cache its results, so
nash
no
longer uses 100% of the CPU when installing
RPM
s. (
BZ#516047
1467
)
•
mkinitrd
copied the
lvm.conf
file verbatim to the initrd without parsing it properly. If the logical
volume manager (LVM) was configured to use host tags,
Red Hat Enterprise Linux
would not boot
because a host name could not be set at initrd time.
lvm --dumpconfig
is now used to retrieve
the LVM configuration file. (
BZ#517868
1468
)
•
mkinitrd
attempted to explicitly activate the subsets of a nested RAID 10 set. Error messages
would then be printed to the log during boot. These messages could safely be ignored. They have
now been removed to avoid confusion. (
BZ#526246
1469
)
•
mkinitrd
copied the symbolic link of a bootpath driver instead of the actual bootpath driver. This
caused kernel panic due to an unavailable driver on first boot of the operating system.
mkinitrd
now checks the full path of symbolically linked drivers. (
BZ#540641
1470
)
• when the root file system was on the logical volume manager (LVM), as is the default installation
option,
nash
received a segmentation fault reference if some modules did not load during post-
installation reboot. This caused unwarranted kernel panic. Kernel panic no longer occurs as a result
of the non-loading of modules. (
BZ#560567
1471
)
• several virtio modules were missing from the previous version of
mkinitrd
. This meant that
mkinitrd
built incorrectly upon installation if virtio block or network devices were used within the
Kernel Based Virtual Machine
(KVM). The final result was kernel panic. These updated packages
contain the required modules which allow
mkinitrd
to build and install correctly. (
BZ#560672
1472
)
As well, these updated packages add the following enhancements:
• the
scsi_dh_rdac
module is needed to support many LSI Engenio based (IBM and non-IBM)
storage devices. With the inclusion of a module such as the
scsi_dh_rdac
module in initrd,
the time to boot a system with multiple rdac devices is minimized. A patch has been applied to
mkinitrd
to load every
scsi_dh_*
module in the event that multipath devices are detected. The
patch currently succeeds in loading
xscsi_dh_rdac
modules for installations on DS4K storage
and further work is being undertaken to ensure the successful loading of modules independent of
the host device. (
BZ#460899
1473
)
•
mkinitrd
is responsible for ensuring that all drivers, applications, and configuration information
needed to mount the root filesystem are packaged into each kernel's initrd. Unlike the Logical
Volume Manager (LVM) component of
mkinitrd
, multipath operates on only the
logical volume
associated with the root filesystem and not the
volume group
containing the root filesystem. As a
consequence, when installing a system with multipath devices, only disks currently in use by the
root's logical volume have multipath configured within the initrd. A patch has been applied that
wraps the
find_mpath_deps
in a loop that iterates through every primary volume in the root
volume group. Non-LVMs are handled in a separate case by runnning
find_mpath_deps
against
the root device. Installing a system with multipath devices will now result in the primary volumes in
the root virtual group being on multipath devices. (
BZ#501535
1474
)