Re: [OSR-devel] Bug Report in rhel5/hardware-lib.sh

[Reiner R. <rot...@at...>]

Hi Gordan,

First of all I have great respect for your work and would like to thank you 
for your effort!

Regarding the update of the initrd you may have a look at the comoonics 
enterprise copy tool (com-ec) which is able to inject a new cluster.conf in 
the existing initrd by re-cpio'ing it.

The usage is quite simple. You need to install the following RPMs:

comoonics-ec-py-0.1-36
comoonics-cs-xsl-ec-0.5-19

Then in /etc/comoonics/enterprisecopy/ there is a XML file called 
updateinitrd.xml. There you need to specify where your boot-device resides 
and what to mount.

For your requirements you may need to adapt the XML file. e.g. to skip the 
mounting of boot and simply stating the location of your initrd.

Best regards,

Reiner

-- 
Gruss / Regards,
Dipl.-Ing. (FH) Reiner Rottmann

ATIX Informationstechnologie und Consulting AG
Einsteinstr. 10 
85716 Unterschleissheim
Deutschland/Germany

Phone: +49-89 452 3538-12     Fax: +49-89 990 1766-0
Email: rot...@at...       PGP Key-ID: 0xCA67C5A6
       www.atix.de  |  www.open-sharedroot.org

Vorstaende: Marc Grimme, Mark Hlawatschek, Thomas Merz (Vors.)
Vorsitzender des Aufsichtsrats: Dr. Martin Buss
Registergericht: Amtsgericht Muenchen
Registernummer: HRB 168930
USt.-Id.: DE209485962

----------------------------------------------------------------------
*** Besuchen Sie uns auf dem ATIX IT Solution Day:
Linux Cluster-Technolgien, am 05.02.2009 in Neuss b. Koeln/Duesseldorf!
www.atix.de/event-archiv/atix-it-solution-day-linux-neuss  ***
----------------------------------------------------------------------

On Wednesday 21 January 2009 02:52:57 am Gordan Bobic wrote:
> Hi,
>
> It would appear that
> /opt/atix/comoonics-bootimage/boot-scripts/etc/rhel5/hardware-lib.sh has
> gone through a few changes in the past few months, which, unfortunately,
> break it for me.
>
> The problem is in the ordering of the detected NICs. On one of my
> systems I have a dual e1000 built into the mobo, and an e100 as an
> add-in card. /etc/modprobe.conf lists eth0 and eth1 as the e1000s, and
> eth2 as e100. This works fine with hardware-lib.sh v1.5, but with v1.7
> the ordering seems to be both unstable (about 1/10 of the time it'll
> actually get the NIC ordering as expected and specified in cluster.conf
> and the rest of the time it'll do something different) and inconsistent
> with what is in cluster.conf and modprobe.conf.
>
> The last version that works for me is v1.5, and the latest released
> version (I'm talking about CVS version numbers here) appears to be v1.7
> for this file (in the comoonics-bootimage-1.3-40.noarch.rpm release).
>
> Needless to say, trying to boot off an iSCSI shared root with the NIC
> not starting because eth designation doesn't match the MAC doesn't get
> very far. :-/
>
> On a separate note, would it perhaps be a good idea to also have an
> updinitrd script? After a few versions of the clustering tools and OSR
> tools, it's impossible to tell what bugs could be introduced that break
> things. Granted, indiscriminately doing "yum update" is a bad idea, but
> it happens to the best of us that we miss something that we really ought
> to exclude. But what could be done instead is to have an updinitrd
> script that opens the current initrd and just modifies the handful of
> files that need changing (e.g. adding a service to cluster.conf) before
> re-cpio-ing it. Any thoughts on this idea? I know that in the ideal
> world it shouldn't be needed, but this is exactly what I ended up having
> to do yesterday because new initrds just wouldn't boot (there was an
> additional problem _just_ before mounting the GFS off DRBD where it
> fails and drops to the prompt - I haven't gotten to the bottom of that
> one yet). Interestingly, the latest tools work just fine for GlusterFS.
>
> Gordan
>
> ---------------------------------------------------------------------------
>--- This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Open-sharedroot-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel