KMP – BAFM

After some more tinkering, a lot more looking at the macros in /usr/lib/rpm/rpm-suse-kernel-module-subpackage and /usr/lib/rpm/suse_macros, I think I finally have a usable RPM’ified version of IBM’s Multipathing driver ready for use.

There is still one major annoyance left: each time you install a new ibm-rdac-ds4000-kmp RPM, you also need to reinstall the corresponding ibm-rdac-ds4000-initrd package, as the macros in /usr/lib/rpm don’t allow for custom %post or %postun.

As mentioned before, I’m gonna send them to LSI/IBM for review, and maybe, MAYBE they are actually gonna make use of that.

Without further delay, here’s the list of packages. Just a short explanation: you need mppUtil-%version, in order to install the ibm-rdac-ds4000-kmp.

mppUtil-09.03.0C05.0030-0.2 (i586, x86_64, ~~SRPM~~)
ibm-rdac-kmp-09.03.0C05.0030_2.6.16.60_0.37_f594963d-0.2 (SRPM)
- ibm-rdac-kmp-bigsmp (i586)
- ibm-rdac-kmp-debug (i586, x86_64)
- ibm-rdac-kmp-default (i586, x86_64)
- ibm-rdac-kmp-kdump (i586, x86_64)
- ibm-rdac-kmp-kdumppae (i586)
- ibm-rdac-kmp-smp (i586, x86_64)
- ibm-rdac-kmp-vmi (i586)
- ibm-rdac-kmp-vmipae (i586)
ibm-rdac-ds4000-initrd-09.03.0C05.0030_2.6.16.60_0.37_f594963d-0.2
- ibm-rdac-initrd-bigsmp (i586)
- ibm-rdac-initrd-debug (i586, x86_64)
- ibm-rdac-initrd-default (i586, x86_64)
- ibm-rdac-initrd-kdump (i586, x86_64)
- ibm-rdac-initrd-kdumppae (i586)
- ibm-rdac-initrd-smp (i586, x86_64)
- ibm-rdac-initrd-vmi (i586)
- ibm-rdac-initrd-vmipae (i586)

This package should be usable with System Storage DS4000 as well as System Storage DS3000 (they use the exact same source code).

I also know, that this solution isn’t really perfect. I’ve been looking at the %triggerin/%triggerun macros, but right now I can’t draw up a scenario (an easy one at that) to successfully use triggers in this situation. Only idea coming up looks like this:

Put the triggers into ibm-rdac-ds4000
When installing the kernel module packages, ~~write the kernelversion/-flavor into a temporary file~~ (impossible, since the macros don’t let you influence %post), and then let the trigger create/update the MPP initrd

If anyone knows a better solution (as in easier, without the writing to a separate file), I’m all ears.

Well, after yesterday’s lesson about getting the IBM RDAC to install for a not-yet-running kernel, I decided to take it a step further. Novell does have some documentation about KMP’s, which is actually rather good, especially the guide written by Andreas Grünbacher.

After a short tinkering, I got it actually working. I was kinda surprised, at how easily it actually is. One problem I still have to deal with, is modifying the %post, to generate the mpp-initrd image. For now, the KMP only contains the default %post, which updates the modules.* stuff.

Name:            ibm-rdac
License:         GPL
Group:           System/Kernel
Summary:         IBM Multipathing driver for DS4000 disk subsystems.

Version:         09.03.0C05.0030
Release:         0.1
Source0:         rdac-LINUX-%version-source.tar.gz
BuildRequires:   kernel-source kernel-syms
BuildRoot:       %{_tmppath}/%{name}-%{version}-build

Requires(post):    mppUtil-%{version}, module-init-tools
Requires(preun):   module-init-tools
Requires(postun):  module-init-tools

%suse_kernel_module_package um

%description
This is the Engenio Linux RDAC Driver Package for IBM DS4000
Storage Subsystems.

%package KMP
Group:     System/Kernel
Summary:   IBM Multipathing driver for DS4000 disk subsystems.

%description KMP
This is the Engenio Linux RDAC Driver Package for IBM DS4000
Storage Subsystems.

%prep
%setup -n linuxrdac-%{version}
set -- *
mkdir source
mv "$@" source/
mkdir obj

%build
export EXTRA_CFLAGS='-DVERSION="%version"'
for flavor in %flavors_to_build; do
    rm -rf obj/$flavor
    cp -r source obj/$flavor
    make -C /usr/src/linux-obj/%_target_cpu/$flavor modules 
            M=$PWD/obj/$flavor
done

%install
export INSTALL_MOD_PATH=$RPM_BUILD_ROOT
export INSTALL_MOD_DIR=updates
for flavor in %flavors_to_build; do
    make -C /usr/src/linux-obj/%_target_cpu/$flavor modules_install 
            M=$PWD/obj/$flavor
done

%changelog
* Thu May 07 2009 - 09.03.0C05.0030-0.1
  - Initial package.

Name: ibm-rdac

License: GPL

Group: System/Kernel

Summary: IBM Multipathing driver for DS4000 disk subsystems.

Version: 09.03.0C05.0030

Release: 0.1

Source0: rdac-LINUX-%version-source.tar.gz

BuildRequires: kernel-source kernel-syms

BuildRoot: %{_tmppath}/%{name}-%{version}-build

Requires(post): mppUtil-%{version}, module-init-tools

Requires(preun): module-init-tools

Requires(postun): module-init-tools

%suse_kernel_module_package um

%description

This is the Engenio Linux RDAC Driver Package for IBM DS4000

Storage Subsystems.

%package KMP

Group: System/Kernel

Summary: IBM Multipathing driver for DS4000 disk subsystems.

%description KMP

This is the Engenio Linux RDAC Driver Package for IBM DS4000

Storage Subsystems.

%prep

%setup -n linuxrdac-%{version}

set -- *

mkdir source

mv "$@" source/

mkdir obj

%build

export EXTRA_CFLAGS='-DVERSION="%version"'

for flavor in %flavors_to_build; do

rm -rf obj/$flavor

cp -r source obj/$flavor

make -C /usr/src/linux-obj/%_target_cpu/$flavor modules

M=$PWD/obj/$flavor

done

%install

export INSTALL_MOD_PATH=$RPM_BUILD_ROOT

export INSTALL_MOD_DIR=updates

for flavor in %flavors_to_build; do

make -C /usr/src/linux-obj/%_target_cpu/$flavor modules_install

M=$PWD/obj/$flavor

done

%changelog

* Thu May 07 2009 - 09.03.0C05.0030-0.1

- Initial package.

Now, I’m kinda asking myself, why don’t more vendors submit their drivers to Novell in form of KMP’s … Anyway, I’m gonna send mine the LSI/IBM way, maybe they’ll pick it up …

S	M	T	W	T	F	S
	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30

Tag: KMP

Novell KMP: Useable version of ibm-rdac-ds4000

Novell KMP: KMP’ing IBM’s RDAC driver