[ ssic-linux-Bugs-1635696 ] Debian mkinitrd doesn't find all modules when using drbd
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.linux.cluster.ssic.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #1635696, was opened at 2007-01-15 04:30 Message generated for change (Comment added) made by rogertsang You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=1635696&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.2 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Debian mkinitrd doesn't find all modules when using drbd Initial Comment: If the root filesystem is on a drbd mkinitrd makes no attempt to work out what modules are needed for the underlying block device. getroot needs to recursively call itself to work out the modules for the "low level device" (shown by "drbdadm sh-ll-dev $RESOURCE") and the metadevice (shown by "drbdadm sh-md-dev $RESOURCE"). Work out RESOURCE by doing a "drbdadm sh-resources" then for each resource check the /dev/drbd# against "drbdadm sh-dev $RESOURCE". ---------------------------------------------------------------------- >Comment By: Roger Tsang (rogertsang) Date: 2007-08-12 19:55 Message: Logged In: YES user_id=1246761 Originator: NO Fixed in 1.9.3 ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2007-01-15 05:06 Message: Logged In: YES user_id=166336 Originator: NO Fixed by my commit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=1635696&group_id=32541 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/