Bug 528097 - /sbin/dmraid needs possibly unmounted /usr/lib
Summary: /sbin/dmraid needs possibly unmounted /usr/lib
Alias: None
Product: Fedora
Classification: Fedora
Component: dmraid
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
Whiteboard: NeedsRetesting
: 528426 (view as bug list)
Depends On:
Blocks: F12Blocker, F12FinalBlocker
TreeView+ depends on / blocked
Reported: 2009-10-09 03:25 UTC by Bruce Jerrick
Modified: 2009-10-30 17:19 UTC (History)
11 users (show)

Clone Of:
Last Closed: 2009-10-30 17:19:20 UTC

Attachments (Terms of Use)

Description Bruce Jerrick 2009-10-09 03:25:53 UTC
Description of problem:
At boot time, if /usr is a separate filesystem, /sbin/dmraid (invoked by
rc.sysinit) fails because it needs /usr/lib/libdmraid.so.1.0.0.rc16, which
is not available until /usr is mounted later in rc.sysinit .

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot an F12 system with /usr on a separate filesystem (suggestion: boot
     single-user mode; message will stay on screen then).
2. Observe error message from /sbin/dmraid.
1. ldd /sbin/dmraid | grep /usr
Actual results:
Error message shortly after "Welcome to Fedora":
    /sbin/dmraid: error while loading shared libraries: \
	/usr/lib/libdmraid.so.1.0.0.rc16: cannot open shared object file: \
	No such file or directory
The ldd command will show one .so file under /usr/lib .

Expected results:
No error message.

Additional info:
Changing the dmraid spec file to install libdmraid.so into /lib will probably
suffice to fix this.  (BTW, libdmraid.so used to be in dmraid-libs .)

/sbin/dmraid.static is not the answer; it's just a symlink to the
dynamically-linked version (presumably for "compatibility").

The problem doesn't happen in F11 because its /sbin/dmraid
(dmraid-1.0.0.rc15-7.fc11) does not use libdmraid.so .

Comment 1 Michal Hlavinka 2009-10-12 08:27:13 UTC
*** Bug 528426 has been marked as a duplicate of this bug. ***

Comment 2 Jim Meyering 2009-10-12 14:17:22 UTC
This burned me, too.
In a few minutes I'll try using the nodmraid boot option, since I have no raid-related devices.

Comment 3 Hans de Goede 2009-10-20 06:06:40 UTC
This is fixed in dmraid-1.0.0.rc16-4.fc12:

Rel-eng nominating this for F12Blocker, as without this fix any raidsets not
brought up by the initrd (so not used for /) will not be available after boot, worse in case of mirrors the system may use a single disk of the mirror instead, causing corruption of the mirror without marking it dirty!

Comment 4 Adam Williamson 2009-10-21 17:08:24 UTC
That dmraid has been tagged into F12 Final. Bruce, once it's available from your mirror, can you please test and confirm the fix? Thanks.

Fedora Bugzappers volunteer triage team

Comment 5 Adam Williamson 2009-10-30 17:19:20 UTC
As discussed at last week's blocker meeting, we're closing this as fixed, can't wait for feedback forever. Please re-open if you still have trouble. Thanks.

Fedora Bugzappers volunteer triage team

Note You need to log in before you can comment on or make changes to this bug.