Red Hat Bugzilla – Bug 168321
rc.sysinit call dynamicly linked multipath rather than multipath.static
Last modified: 2014-03-16 22:55:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Firefox/1.0.6
Description of problem:
In the LVM2 initialization section of rc.sysinit the system checks for and, if required, calls /sbin/multipath rather than /sbin/multipath.static. Because the multipath tool is dependent on /usr/lib/libsysfs.so.1 this causes errors on systems that mount /usr on another volume since /usr is not normally mounted at this point.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a system with seperate root and /usr volumes
2. Create a multipath.conf file for multipath devices
3. Boot the system and see errors
Actual Results: Errors about missing /usr/lib/libsysfs.so.1 when multipath is run during init and, because of this, improper building of multipath LVM's.
Expected Results: No errors and proper multipath setup before LVM scan.
The proper fix seems obvious to me, call multipath.static rather than multipath. The script does call lvm.static already. I suppose another option is to relocate libsysfs.so.1 to /lib, but that seems technically incorrect.
I set this to high severity since, without this fix, LVM devices can be unknowingly improperly configured on top of their physical devices rather than the multipath devices meaning that users may think multipath is setup because they see the multipath devices, but the reality is the volumes are activated on a single path.
*** Bug 171895 has been marked as a duplicate of this bug. ***
Built in 7.93.21.EL-1.
*** Bug 174367 has been marked as a duplicate of this bug. ***
*** Bug 175179 has been marked as a duplicate of this bug. ***
*** Bug 178419 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.