[Lustre-discuss] intrepid kernel on jaunty

[Papp Tamás]

hi All!

I'm trying to make an Ubuntu based patchless client.

I installed Intrepid's kernel 2.6.27 on jaunty, which originally has 2.6.28.

It's booting and working fine.

Also I installed the related headers.

The configure runs OK, but when I compile it:

make[3]: Entering directory `/usr/src/linux-headers-2.6.27-15-server'
LD /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/built-in.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/o2iblnd.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/o2iblnd_cb.o
CC [M]
/usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/o2iblnd_modparams.o
LD [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/ko2iblnd.o
LD /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/built-in.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/socklnd.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/socklnd_cb.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/socklnd_proto.o
CC [M]
/usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/socklnd_modparams.o
CC [M]
/usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/socklnd_lib-linux.o
LD [M] /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/socklnd/ksocklnd.o
LD /usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/built-in.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/linux/linux-tracefile.o
CC [M] /usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.o
cc1: warnings being treated as errors
/usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.c: In
function âprint_trace_warning_symbolâ:
/usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.c:216:
error: format not a string literal and no format arguments
make[6]: ***
[/usr/src/lustre/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.o] Error 1
make[5]: *** [/usr/src/lustre/lustre-1.8.1.1/lnet/libcfs] Error 2
make[4]: *** [/usr/src/lustre/lustre-1.8.1.1/lnet] Error 2
make[3]: *** [_module_/usr/src/lustre/lustre-1.8.1.1] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.27-15-server'
make[2]: *** [modules] Error 2
make[2]: Leaving directory `/usr/src/lustre/lustre-1.8.1.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/lustre/lustre-1.8.1.1'
make: *** [all] Error 2

The configure options:

./configure --with-linux=/usr/src/linux-headers-2.6.27-15-server
--disable-server --disable-test --disable-utils --disable-doc

Has anybody any susccess installing lustre patchless client on Jaunty?
Or on Intrepid, if I have now choice, I try to step back.

Also I tried to search bugzilla to patches to 2.6.28, but already they
are too old and cannot be applied to the HEAD. Also the HEAD fails to
compile with the headers of 2.6.28.

I'm doubt, what to do.

Thank you,

tamas
_______________________________________________
Lustre-discuss mailing list
Lustre-...@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

[Brian J. Murrell]

On Wed, 2009-10-28 at 19:37 +0100, Papp Tamás wrote:
> hi All!
>
> I'm trying to make an Ubuntu based patchless client.
>
> I installed Intrepid's kernel 2.6.27 on jaunty, which originally has 2.6.28.

Why not just use Jaunty's kernel?

$ uname -r
2.6.28-11-generic

$ cat /proc/fs/lustre/version
lustre: 1.8.1.50
kernel: patchless_client
build: b1_8-20090921170221-CHANGED-2.6.28-11-generic

> LD /usr/src/lustre/lustre-1.8.1.1/lnet/klnds/o2iblnd/built-in.o
^^^^^^^
Ahhhh. You really want to be using b1_8 for this. 1.8.1[.x] doesn't
have the required kernel support. Certainly you could find the relevant
bugs in bugzilla and do some backporting but it might be a bit of work.

Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
unsupported basis at this point) in /debian. Here are the installed
packages, built from the /debian in b1_8 from my client:

ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre Linux kernel module (kernel 2.6.28-11
ii lustre-tests 1.8.1.50-2 Test suite for the Lustre filesystem
ii lustre-utils 1.8.1.50-2 Userspace utilities for the Lustre filesyste

> Has anybody any susccess installing lustre patchless client on Jaunty?

Yes. With the Jaunty kernel even.

> Also I tried to search bugzilla to patches to 2.6.28, but already they
> are too old and cannot be applied to the HEAD. Also the HEAD fails to
> compile with the headers of 2.6.28.

You really don't want to be messing around with HEAD for anything other
than previewing technology. Certainly not for a production system.
b1_8 is the branch you are really looking for.

b.

[Papp Tamás]

Brian J. Murrell wrote, On 2009. 10. 28. 20:26:
> Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
> unsupported basis at this point) in /debian. Here are the installed
> packages, built from the /debian in b1_8 from my client:
>
> ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre Linux kernel module (kernel 2.6.28-11
> ii lustre-tests 1.8.1.50-2 Test suite for the Lustre filesystem
> ii lustre-utils 1.8.1.50-2 Userspace utilities for the Lustre filesyste
>

Thanks, it looks nice:)

>> Has anybody any susccess installing lustre patchless client on Jaunty?
>>
>
> Yes. With the Jaunty kernel even.
>
>
>> Also I tried to search bugzilla to patches to 2.6.28, but already they
>> are too old and cannot be applied to the HEAD. Also the HEAD fails to
>> compile with the headers of 2.6.28.
>>
>
> You really don't want to be messing around with HEAD for anything other
> than previewing technology. Certainly not for a production system.
> b1_8 is the branch you are really looking for.
>

Of course first of all I tried b1_8.

Right now b1_8:

debian/rules binary...

make[3]: Entering directory `/usr/src/lustre-head/lustre/lustre'
perl ../lustre/scripts/version_tag.pl .. .. > tmpver
Uncaught exception from user code:
Run make dep on
at ../lustre/scripts/version_tag.pl line 170
main::get_linuxdir() called at ../lustre/scripts/version_tag.pl line 258
make[3]: *** [lustre_build_version] Error 2
make[3]: Leaving directory `/usr/src/lustre-head/lustre/lustre'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/lustre-head/lustre'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/lustre-head/lustre'
make: *** [build-stamp] Error 2

With my own configure options:

./configure --with-linux=/usr/src/linux-headers-2.6.28-16-server/
--disable-server --disable-test --disable-utils --disable-doc

CC [M] /usr/src/lustre-head/lustre/lustre/llite/rw26.o
/usr/src/lustre-head/lustre/lustre/llite/rw26.c:422: error: unknown
field âprepare_writeâ specified in initializer

cc1: warnings being treated as errors

/usr/src/lustre-head/lustre/lustre/llite/rw26.c:422: error:
initialization from incompatible pointer type
/usr/src/lustre-head/lustre/lustre/llite/rw26.c:423: error: unknown
field âcommit_writeâ specified in initializer
/usr/src/lustre-head/lustre/lustre/llite/rw26.c:423: error:
initialization from incompatible pointer type
make[6]: *** [/usr/src/lustre-head/lustre/lustre/llite/rw26.o] Error 1
make[5]: *** [/usr/src/lustre-head/lustre/lustre/llite] Error 2
make[4]: *** [/usr/src/lustre-head/lustre/lustre] Error 2
make[3]: *** [_module_/usr/src/lustre-head/lustre] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.28-16-server'

make[2]: *** [modules] Error 2

make[2]: Leaving directory `/usr/src/lustre-head/lustre'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/usr/src/lustre-head/lustre'

make: *** [all] Error 2

Do I miss something, or it's just not OK right now?

[Papp Tamás]

Papp Tamás wrote, On 2009. 10. 28. 22:01:
> Brian J. Murrell wrote, On 2009. 10. 28. 20:26:
>
>> Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
>> unsupported basis at this point) in /debian. Here are the installed
>> packages, built from the /debian in b1_8 from my client:
>>
>> ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre Linux kernel module (kernel 2.6.28-11
>> ii lustre-tests 1.8.1.50-2 Test suite for the Lustre filesystem
>> ii lustre-utils 1.8.1.50-2 Userspace utilities for the Lustre filesyste
>>
>>

Somehow I could make the debs, but not the modules, only these:

liblustre_1.8.1.50-1_amd64.deb
lustre-dev_1.8.1.50-1_amd64.deb
lustre-tests_1.8.1.50-1_amd64.deb
linux-patch-lustre_1.8.1.50-1_all.deb
lustre-source_1.8.1.50-1_all.deb
lustre-utils_1.8.1.50-1_amd64.deb

Bye,

[Ralf Utermann]

Papp Tamás schrieb:

> Papp Tamás wrote, On 2009. 10. 28. 22:01:
>> Brian J. Murrell wrote, On 2009. 10. 28. 20:26:
>>
>>> Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
>>> unsupported basis at this point) in /debian. Here are the installed
>>> packages, built from the /debian in b1_8 from my client:
>>>
>>> ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre Linux kernel module (kernel 2.6.28-11
>>> ii lustre-tests 1.8.1.50-2 Test suite for the Lustre filesystem
>>> ii lustre-utils 1.8.1.50-2 Userspace utilities for the Lustre filesyste
>>>
>>>
>
> Somehow I could make the debs, but not the modules, only these:
>
> liblustre_1.8.1.50-1_amd64.deb
> lustre-dev_1.8.1.50-1_amd64.deb
> lustre-tests_1.8.1.50-1_amd64.deb
> linux-patch-lustre_1.8.1.50-1_all.deb
> lustre-source_1.8.1.50-1_all.deb
> lustre-utils_1.8.1.50-1_amd64.deb

then install lustre-source_1.8.1.50-1_all.deb, and build the modules
using 'm-a build lustre ' . You might need to chmod +x /usr/src/modules/lustre/debian/rules .

Bye, Ralf
--
Ralf Utermann
_____________________________________________________________________
Universität Augsburg, Institut für Physik -- EDV-Betreuer
Universitätsstr.1
D-86135 Augsburg Phone: +49-821-598-3231
SMTP: Ralf.U...@Physik.Uni-Augsburg.DE Fax: -3411

[Papp Tamás]

Ralf Utermann wrote, On 2009. 10. 29. 9:21:
> Papp Tamás schrieb:
>
>> Papp Tamás wrote, On 2009. 10. 28. 22:01:
>>
>>> Brian J. Murrell wrote, On 2009. 10. 28. 20:26:
>>>
>>>
>>>> Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
>>>> unsupported basis at this point) in /debian. Here are the installed
>>>> packages, built from the /debian in b1_8 from my client:
>>>>
>>>> ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre Linux kernel module (kernel 2.6.28-11
>>>> ii lustre-tests 1.8.1.50-2 Test suite for the Lustre filesystem
>>>> ii lustre-utils 1.8.1.50-2 Userspace utilities for the Lustre filesyste
>>>>
>>>>
>>>>
>> Somehow I could make the debs, but not the modules, only these:
>>
>> liblustre_1.8.1.50-1_amd64.deb
>> lustre-dev_1.8.1.50-1_amd64.deb
>> lustre-tests_1.8.1.50-1_amd64.deb
>> linux-patch-lustre_1.8.1.50-1_all.deb
>> lustre-source_1.8.1.50-1_all.deb
>> lustre-utils_1.8.1.50-1_amd64.deb
>>
>
> then install lustre-source_1.8.1.50-1_all.deb, and build the modules
> using 'm-a build lustre ' . You might need to chmod +x /usr/src/modules/lustre/debian/rules .
>

Yes, I'm a lame and you are right:)

Unfortunately still I get error after starting to build:

checking for external module build support...
yes â
â checking that modules can be
built at all... no â
â configure: WARNING: Consult
config.log for details. â
â configure: WARNING: If you are
trying to build with a kernel-source rpm, â
â consult
build/README.kernel-source â
â configure: error: Kernel
modules cannot be built. â
â make[1]: *** [kdist_config]
Error 1 â
â make[1]: Leaving directory
`/usr/src/modules/lustre' âŽ
â make: *** [kdist_build] Error
2 â

tamas

[Ralf Utermann]

Papp Tamás schrieb:
[...]

>
> Unfortunately still I get error after starting to build:
>
> checking for external module build support...
> yes â
> â checking that modules can be
> built at all... no â
> â configure: WARNING: Consult
> config.log for details. â
> â configure: WARNING: If you are
> trying to build with a kernel-source rpm, â
> â consult
> build/README.kernel-source â
> â configure: error: Kernel modules
> cannot be built. â
> â make[1]: *** [kdist_config]
> Error 1 â
> â make[1]: Leaving directory
> `/usr/src/modules/lustre' âŽ
> â make: *** [kdist_build] Error
> 2 â
>
>
> tamas

check modules/lustre/config.log to see, where it really goes wrong.

Bye, Ralf
--
Ralf Utermann
_____________________________________________________________________
Universität Augsburg, Institut für Physik -- EDV-Betreuer
Universitätsstr.1
D-86135 Augsburg Phone: +49-821-598-3231
SMTP: Ralf.U...@Physik.Uni-Augsburg.DE Fax: -3411

[Bernd Schubert]

On Thursday 29 October 2009, Ralf Utermann wrote:
> Papp Tamás schrieb:
> > Papp Tamás wrote, On 2009. 10. 28. 22:01:
> >> Brian J. Murrell wrote, On 2009. 10. 28. 20:26:
> >>> Additionally, b1_8 (aka 1.8.2) also has debian packaging support (on an
> >>> unsupported basis at this point) in /debian. Here are the installed
> >>> packages, built from the /debian in b1_8 from my client:
> >>>
> >>> ii lustre-client-modules-2.6.28-11-generic 1.8.1.50-2 Lustre
> >>> Linux kernel module (kernel 2.6.28-11 ii lustre-tests
> >>> 1.8.1.50-2 Test suite for the Lustre filesystem ii
> >>> lustre-utils 1.8.1.50-2 Userspace
> >>> utilities for the Lustre filesyste
> >
> > Somehow I could make the debs, but not the modules, only these:
> >
> > liblustre_1.8.1.50-1_amd64.deb
> > lustre-dev_1.8.1.50-1_amd64.deb
> > lustre-tests_1.8.1.50-1_amd64.deb
> > linux-patch-lustre_1.8.1.50-1_all.deb
> > lustre-source_1.8.1.50-1_all.deb
> > lustre-utils_1.8.1.50-1_amd64.deb
>
> then install lustre-source_1.8.1.50-1_all.deb, and build the modules
> using 'm-a build lustre ' . You might need to chmod +x
> /usr/src/modules/lustre/debian/rules .

I might be the only one complaining, but I think the method I proposed with
attachment 24529 (https://bugzilla.lustre.org/attachment.cgi?id=24529) was
more convenient, as least when you just want to build packages, e.g. in a
chroot. Just autotools support was missing to automatically do the sed steps.
And no, when Brian was working on this, I really didn't have the time to step
in, I had been already far above 16 hours per day that time.

--
Bernd Schubert
DataDirect Networks

[Papp Tamás]

Ralf Utermann wrote, On 2009. 10. 29. 10:03:
> check modules/lustre/config.log to see, where it really goes wrong.
>

Sorry for the late answer.

Actually I almost out of ideas.

Here is, what I did already:

Without deb specific steps. I'm sure, something is missing, or something
I do wrong, but I have no clue.
Basically I do what I would do on Fedora, except it's working there.

I tried it with the relevant linux-header*deb packages, but also I tried
to compile a kernel by myself from linux-source*deb package (linux
source + Ubuntu patches), and used that tree.

*Jaunty + b1_8* -> failure

/usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error: unknown

field âprepare_writeâ specified in initializer
cc1: warnings being treated as errors

/usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error:

initialization from incompatible pointer type

/usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error: unknown

field âcommit_writeâ specified in initializer

/usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error:

initialization from incompatible pointer type

make[6]: *** [/usr/src/lustre-b1_8/lustre/lustre/llite/rw26.o] Error 1
make[5]: *** [/usr/src/lustre-b1_8/lustre/lustre/llite] Error 2
make[4]: *** [/usr/src/lustre-b1_8/lustre/lustre] Error 2
make[3]: *** [_module_/usr/src/lustre-b1_8/lustre] Error 2
make[3]: Leaving directory `/usr/src/linux-source-2.6.28'

make[2]: *** [modules] Error 2

make[2]: Leaving directory `/usr/src/lustre-b1_8/lustre'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/usr/src/lustre-b1_8/lustre'

make: *** [all] Error 2

*Intrepid + 1.8.1.1* -> failure

make[3]: Entering directory `/usr/src/linux-headers-2.6.27-15-server'

CC [M] /root/1/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.o

cc1: warnings being treated as errors

/root/1/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.c: In function
âprint_trace_warning_symbolâ:
/root/1/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.c:216: error:

format not a string literal and no format arguments

make[6]: *** [/root/1/lustre-1.8.1.1/lnet/libcfs/linux/linux-debug.o]
Error 1
make[5]: *** [/root/1/lustre-1.8.1.1/lnet/libcfs] Error 2
make[4]: *** [/root/1/lustre-1.8.1.1/lnet] Error 2
make[3]: *** [_module_/root/1/lustre-1.8.1.1] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.27-15-server'

make[2]: *** [modules] Error 2

make[2]: Leaving directory `/root/1/lustre-1.8.1.1'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/root/1/lustre-1.8.1.1'

make: *** [all] Error 2

*Hardy +1.8.1.1* -> failure

make[3]: Entering directory `/usr/src/linux-headers-2.6.24-25-server'
CC [M] /root/1/lustre-1.8.1.1/lustre/llite/rw.o

cc1: warnings being treated as errors

/root/1/lustre-1.8.1.1/lustre/llite/rw.c: In function âll_file_lockless_ioâ:
/root/1/lustre-1.8.1.1/lustre/llite/rw.c:2376: warning: passing argument
1 of âremove_suidâ from incompatible pointer type
/root/1/lustre-1.8.1.1/lustre/llite/rw.c:2376: error: too many arguments
to function âremove_suidâ
make[6]: *** [/root/1/lustre-1.8.1.1/lustre/llite/rw.o] Error 1
make[5]: *** [/root/1/lustre-1.8.1.1/lustre/llite] Error 2
make[4]: *** [/root/1/lustre-1.8.1.1/lustre] Error 2
make[3]: *** [_module_/root/1/lustre-1.8.1.1] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.24-25-server'

make[2]: *** [modules] Error 2

make[2]: Leaving directory `/root/1/lustre-1.8.1.1'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/root/1/lustre-1.8.1.1'

make: *** [all] Error 2

The debian specific way:

# apt-get install [build-deps]
# debian/rules
# debian/rules binary

# dpkg -i *deb

# m-a build lustre -> view ->
"/usr/share/modass/overrides/lustre-source: 1: debian/rules: Permission
denied"

# ls -l /usr/src/modules/lustre/debian/rules
-rw-r--r-- 1 root root 13793 2009-10-30 14:51
/usr/src/modules/lustre/debian/rules

# chmod +x /usr/src/modules/lustre/debian/rules

# m-a build lustre -> Permission denied again

# ls -l /usr/src/modules/lustre/debian/rules
-rw-r--r-- 1 root root 13793 2009-10-30 14:51
/usr/src/modules/lustre/debian/rules

What do I wrong?

Please give me some advice:)

Thank you,

tamas

[Brian J. Murrell]

On Fri, 2009-10-30 at 16:02 +0100, Papp Tamás wrote:
>
> *Jaunty + b1_8* -> failure

Just now, I checked out a b1_8, added the following target to
build/autoMakefile.am.toplevel:

debs:
lversion=$$(sed -ne 's/^#define VERSION "\(.*\)"$$/\1/p' config.h); \
cversion=$$(sed -ne '1s/^lustre (\(.*\)-[0-9][0-9]*).*$$/\1/p' debian/changelog); \
if [ "$$lversion" != "$$cversion" ]; then \
echo -e "1i\nlustre ($$lversion-1) unstable; urgency=low\n\n * Automated changelog entry update\n\n -- Brian J. Murrell <br...@interlinx.bc.ca> $$(date -R)\n\n.\nwq" | ed debian/changelog; \
fi
dpkg-buildpackage || { \
[ $${PIPESTATUS[0]} != 1 ] && exit $${PIPESTATUS[0]}; \
true; \
}
export KPKG_DEST_DIR="$$(pwd)/.."; \
version=$$(sed -ne '1s/^lustre (\(.*\)).*$$/\1/p' debian/changelog); \
rm -rf modules-deb; \
mkdir modules-deb; \
cd modules-deb; \
dpkg -x ../../lustre-source_$${version}_all.deb $$(pwd); \
mkdir usr_src/; \
tar -C usr_src/ -xjvf usr/src/lustre.tar.bz2; \
chmod 755 usr_src/modules/lustre/debian/rules; \
m-a build $${KVERS:+-l $$KVERS} -i -u $$(pwd) lustre

(which I'm going to put into bug 19721 now that I've tested it out)

(and of course had the below mentioned patch applied)

and simply did "make debs" and I got as a result:

-rw-r--r-- 1 brian brian 744580 2009-10-30 17:18 liblustre_1.8.1.52-1_i386.deb
-rw-r--r-- 1 brian brian 501264 2009-10-30 17:17 linux-patch-lustre_1.8.1.52-1_all.deb
-rw-r--r-- 1 brian brian 821 2009-10-30 17:16 lustre_1.8.1.52-1.dsc
-rw-r--r-- 1 brian brian 3037 2009-10-30 17:18 lustre_1.8.1.52-1_i386.changes
-rw-r--r-- 1 brian brian 14277672 2009-10-30 17:16 lustre_1.8.1.52-1.tar.gz
-rw-r--r-- 1 brian brian 16493170 2009-10-30 17:24 lustre-client-modules-2.6.28-11-generic_1.8.1.52-1_i386.deb
-rw-r--r-- 1 brian brian 5111928 2009-10-30 17:18 lustre-dev_1.8.1.52-1_i386.deb
-rw-r--r-- 1 brian brian 11845920 2009-10-30 17:18 lustre-source_1.8.1.52-1_all.deb
-rw-r--r-- 1 brian brian 1097240 2009-10-30 17:18 lustre-tests_1.8.1.52-1_i386.deb
-rw-r--r-- 1 brian brian 693990 2009-10-30 17:18 lustre-utils_1.8.1.52-1_i386.deb

> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error: unknown
> field âprepare_writeâ specified in initializer
> cc1: warnings being treated as errors
> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error:
> initialization from incompatible pointer type
> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error: unknown
> field âcommit_writeâ specified in initializer
> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error:
> initialization from incompatible pointer type

Yeah. You need the patch in attachment 26155 in bug 20451. I am still
waiting for an inspection to get it landed.

b.

[Papp Tamás]

It's working for mee too, but without liblustre.

linux-patch-lustre_1.8.1.52-1_all.deb
lustre-dev_1.8.1.52-1_amd64.deb lustre-tests_1.8.1.52-1_amd64.deb
lustre-client-modules-2.6.28-16-server_1.8.1.52-1_amd64.deb
lustre-source_1.8.1.52-1_all.deb lustre-utils_1.8.1.52-1_amd64.deb

BTW I think it should not depend on linux-headers-generic, but
linux-headers, should?

>> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error: unknown
>> field âprepare_writeâ specified in initializer
>> cc1: warnings being treated as errors
>> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:422: error:
>> initialization from incompatible pointer type
>> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error: unknown
>> field âcommit_writeâ specified in initializer
>> /usr/src/lustre-b1_8/lustre/lustre/llite/rw26.c:423: error:
>> initialization from incompatible pointer type
>>
>
> Yeah. You need the patch in attachment 26155 in bug 20451. I am still
> waiting for an inspection to get it landed.
>

Thanks so much.

I don't know, why I didn't find it in bugzilla.

Thanks again,

[Brian J. Murrell]

On Sun, 2009-11-01 at 17:03 +0100, Papp Tamás wrote:
>
> It's working for mee too, but without liblustre.

Meaning you disabled liblustre just because you don't want it, or that
it failed to build for you? It built here fine.

> BTW I think it should not depend on linux-headers-generic, but
> linux-headers, should?

Well, on Ubuntu at least, linux-headers-generic is a virtual package
that depends on the latest versioned linux-headers. i.e.:

$ apt-cache depends linux-headers-generic
linux-headers-generic
Depends: linux-headers-2.6.28-16-generic

There is no linux-headers package in Ubuntu. Granted this is a
Ubuntuism, but I don't have a Debian system here to test any changes for
portability. Is your suggestion specific to Debian?

Ahhhh. In my development tree, I in fact have the following patch:

@@ -4,7 +4,7 @@
Maintainer: Brian J. Murrell <br...@interlinx.bc.ca>
Uploaders: Brian J. Murrell <br...@interlinx.bc.ca>
Standards-Version: 3.8.3
-Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch, automake, libsnmp-dev, bzip2, quilt, texlive-latex-recommended, linux-headers-generic | linux-headers, rsync
+Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch, automake1.7, libsnmp-dev, bzip2, quilt, texlive-latex-recommended, linux-headers-generic, rsync
Homepage: http://www.lustre.org/
Vcs-Cvs: -d :pserver:anon...@cvs.lustre.org:/lustre

Probably this needs to get landed.

b.

[Brian J. Murrell]

On Sun, 2009-11-01 at 17:03 +0100, Papp Tamás wrote:
>

> It's working for mee too, but without liblustre.

Meaning you disabled liblustre just because you don't want it, or that

it failed to build for you? It built here fine.

> BTW I think it should not depend on linux-headers-generic, but
> linux-headers, should?

Well, on Ubuntu at least, linux-headers-generic is a virtual package

that depends on the latest versioned linux-headers. i.e.:

$ apt-cache depends linux-headers-generic
linux-headers-generic
Depends: linux-headers-2.6.28-16-generic

There is no linux-headers package in Ubuntu. Granted this is a
Ubuntuism, but I don't have a Debian system here to test any changes for
portability. Is your suggestion specific to Debian?

Ahhhh. In my development tree, I in fact already have the following
patch:

@@ -4,7 +4,7 @@
Maintainer: Brian J. Murrell <br...@interlinx.bc.ca>
Uploaders: Brian J. Murrell <br...@interlinx.bc.ca>
Standards-Version: 3.8.3

-Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch, automake1.7, libsnmp-dev, bzip2, quilt, texlive-latex-recommended, linux-headers-generic, rsync
+Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch, automake, libsnmp-dev, bzip2, quilt, texlive-latex-recommended, linux-headers-generic | linux-headers, rsync

Homepage: http://www.lustre.org/
Vcs-Cvs: -d :pserver:anon...@cvs.lustre.org:/lustre

b.

[Andreas Dilger]

On 2009-11-02, at 11:41, Brian J. Murrell wrote:
> Ahhhh. In my development tree, I in fact have the following patch:
>
> @@ -4,7 +4,7 @@
> Maintainer: Brian J. Murrell <br...@interlinx.bc.ca>
> Uploaders: Brian J. Murrell <br...@interlinx.bc.ca>
> Standards-Version: 3.8.3
> -Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch,
> automake, libsnmp-dev, bzip2, quilt, texlive-latex-recommended,
> linux-headers-generic | linux-headers, rsync
> +Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch,
> automake1.7, libsnmp-dev, bzip2, quilt, texlive-latex-recommended,
> linux-headers-generic, rsync

You mean the reverse of this should land, right? Lustre doesn't
depend on automake1.7 specifically (it can work on any version up to
1.10).

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

[Brian J. Murrell]

On Mon, 2009-11-02 at 13:25 -0700, Andreas Dilger wrote:
> On 2009-11-02, at 11:41, Brian J. Murrell wrote:
> > Ahhhh. In my development tree, I in fact have the following patch:
> >
> > @@ -4,7 +4,7 @@
> > Maintainer: Brian J. Murrell <br...@interlinx.bc.ca>
> > Uploaders: Brian J. Murrell <br...@interlinx.bc.ca>
> > Standards-Version: 3.8.3
> > -Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch,
> > automake, libsnmp-dev, bzip2, quilt, texlive-latex-recommended,
> > linux-headers-generic | linux-headers, rsync
> > +Build-Depends: libreadline-dev, debhelper (>=5.0.0), dpatch,
> > automake1.7, libsnmp-dev, bzip2, quilt, texlive-latex-recommended,
> > linux-headers-generic, rsync
>
>
> You mean the reverse of this should land, right? Lustre doesn't
> depend on automake1.7 specifically (it can work on any version up to
> 1.10).

Yeah. I thought I pasted in the properly directionalized patch. I know
I did make it because I had to correct the first one I pasted. Maybe I
pasted it and then erroneously deleted it thinking I was deleting the
wrong one.

In any case, yes, the reverse of that patch.

b.

[Papp Tamás]

First of all I think, module-assistant as a build dependency is missing
from the file control.
Also something wrong about the newest b1_8:

Here is the end of output after I installed module-assistant:

gcc -g -Wall -fPIC -D_GNU_SOURCE -Wall -g -O2 -O2 -Werror
-L../../lnet/utils -Wl,-Bsymbolic-functions -o lshowmount lshowmount.o
nidlist.o
make[5]: *** No rule to make target `ll_decode_filter_fid.o', needed by
`ll_decode_filter_fid'. Stop.
make[5]: Leaving directory `/data/src/lustre/lustre/utils'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/data/src/lustre/lustre'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/data/src/lustre'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/data/src/lustre'
make[1]: *** [build-stamp] Error 2
make[1]: Leaving directory `/data/src/lustre'
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
export KPKG_DEST_DIR="$(pwd)/.."; \
version=$(sed -ne '1s/^lustre (\(.*\)).*$/\1/p' debian/changelog); \

rm -rf modules-deb; \
mkdir modules-deb; \
cd modules-deb; \

dpkg -x ../../lustre-source_${version}_all.deb $(pwd); \

mkdir usr_src/; \
tar -C usr_src/ -xjvf usr/src/lustre.tar.bz2; \
chmod 755 usr_src/modules/lustre/debian/rules; \

m-a build ${KVERS:+-l $KVERS} -i -u $(pwd) lustre
dpkg-deb: failed to read archive
`../../lustre-source_1.8.1.52-1_all.deb': No such file or directory
tar: usr/src/lustre.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
chmod: cannot access `usr_src/modules/lustre/debian/rules': No such file
or directory
The source tarball could not be found!
Package lustre-source not installed?
Running "m-a -f get lustre-source" may help.
The source tarball could not be found!
Package lustre-source not installed?
Running "m-a -f get lustre-source" may help.
make: *** [debs] Error 7

So I built an older version, and liblustre*deb has been created. I don't
know, why not before.

Thank you,

tamas

[Brian J. Murrell]

On Tue, 2009-11-03 at 18:48 +0100, Papp Tamás wrote:
>
> First of all I think, module-assistant as a build dependency is missing
> from the file control.

No. Because dpkg-buildpackage in the lustre directory doesn't actually
invoke m-a at all. My "make debs" make target does. That does not
equate to a build dependency for lustre/debian though.

> Also something wrong about the newest b1_8:
>
> Here is the end of output after I installed module-assistant:
>
> gcc -g -Wall -fPIC -D_GNU_SOURCE -Wall -g -O2 -O2 -Werror
> -L../../lnet/utils -Wl,-Bsymbolic-functions -o lshowmount lshowmount.o
> nidlist.o
> make[5]: *** No rule to make target `ll_decode_filter_fid.o', needed by
> `ll_decode_filter_fid'. Stop.

Yes. This looks like a bungled commit of bug 21244. I have alerted the
developer responsible.

In the meanwhile you can just remove ll_decode_filter_fid from
sbin_PROGRAMS in lustre/utils/Makefile.am

b.

[Papp Tamás]

Brian J. Murrell wrote, On 2009. 11. 03. 21:57:
> No. Because dpkg-buildpackage in the lustre directory doesn't actually
> invoke m-a at all. My "make debs" make target does. That does not
> equate to a build dependency for lustre/debian though.
>

Yes, you're right.

> Yes. This looks like a bungled commit of bug 21244. I have alerted the
> developer responsible.
>
> In the meanwhile you can just remove ll_decode_filter_fid from
> sbin_PROGRAMS in lustre/utils/Makefile.am
>

Thanks.

tamas

[Frank Heckes]

Hi all,

I downloaded lustre version 1.8.1.1 and the associated patched kernel
for SLES 11. Compilation works smoothly, but I 'unfortunatly' the kernel
is named vmlinuz-2.6.27.29-0.1-default, initrd, systemmap... and modules
are installed in /lib/modules/2.6.27.29-0.12.6.27.29-0.1-default.
As there's a standart kernel already installed on the system I like to
keep the installation will conflict with the build result.

Question is: Is there a way to rename the build result to a different
target say vmlinuz-2.6.27.29-0.1_lustre-1.8.1.1-default
and /lib/modules/2.6.27.29-0.1_lustre-1.8.1.1-default?

Many thank in advance.

-Frank

------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

[Brian J. Murrell]

On Thu, 2009-11-26 at 10:26 +0100, Frank Heckes wrote:
> Hi all,

Hi Frank,

> I downloaded lustre version 1.8.1.1 and the associated patched kernel
> for SLES 11. Compilation works smoothly, but I 'unfortunatly' the kernel
> is named vmlinuz-2.6.27.29-0.1-default

For the patched kernel? That's not what the patched kernel's
version/release should be.

> modules
> are installed in /lib/modules/2.6.27.29-0.12.6.27.29-0.1-default.

That's not right either. For the patched kernel, the version-release
string should have "_lustre" embedded in it.

> As there's a standart kernel already installed on the system I like to
> keep the installation will conflict with the build result.

This is why we do embed "_lustre" into the version/release string.

I am looking at
kernel-lustre-default-base-2.6.27.29-0.1_lustre.1.8.1.1.x86_64.rpm right
now and I see modules being installed into:

/lib/modules/2.6.27.29-0.1_lustre.1.8.1.1-default

with firmware going into:

/lib/firmware/2.6.27.29-0.1_lustre.1.8.1.1-default

and with all of the /boot/ files named:

/boot/System.map-2.6.27.29-0.1_lustre.1.8.1.1-default
/boot/config-2.6.27.29-0.1_lustre.1.8.1.1-default
/boot/symsets-2.6.27.29-0.1_lustre.1.8.1.1-default.tar.gz
/boot/symtypes-2.6.27.29-0.1_lustre.1.8.1.1-default.gz
/boot/symvers-2.6.27.29-0.1_lustre.1.8.1.1-default.gz
/boot/vmlinux-2.6.27.29-0.1_lustre.1.8.1.1-default.gz
/boot/vmlinuz-2.6.27.29-0.1_lustre.1.8.1.1-default

Are you sure you are using the correct RPM(s)? What does:

$ rpm -qip <file>.rpm

report about the RPM you are trying to install? If it's a Sun built RPM
for the patches Lustre kernel for SLES11 it should say:

Name : kernel-lustre-default-base Relocations: (not relocatable)
Version : 2.6.27.29 Vendor: (none)
Release : 0.1_lustre.1.8.1.1 Build Date: Tue 06 Oct 2009 06:43:49 AM MDT
Install Date: (not installed) Build Host: x86-build-1.co.cfs
Group : System/Kernel Source RPM: kernel-lustre-default-2.6.27.29-0.1_lustre.1.8.1.1.nosrc.rpm
Size : 67685941 License: GPL v2 only
Signature : (none)
URL : http://www.kernel.org/
Summary : Base Modules of the Standard Kernel
Description :
The standard kernel for both uniprocessor and multiprocessor systems.

This package contains only the base modules, required in all installs.

Source Timestamp: 2009-08-15 17:53:59 +0200
GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
GIT Branch: SLE11_BRANCH

Cheers,
b.

[Frank Heckes]

Hello Brian,

>
> Are you sure you are using the correct RPM(s)? What does:
>
> $ rpm -qip <file>.rpm
>

Well, I downloaded two 'source' files:

-1- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.src.rpm
-2- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.x86_64.rpm

I used the second for the compilation since the first only install stuff
in /usr/src/packages/SOURCE and some more complicated procedure has to
be used for compilation.
Entries for /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1
and /lib/modules-2.6.27.29-0.1_lustre.1.8.1.1
will be created when installing rpm '-2-'. Running 'make rpm' leads to
an RPM with the specified install pathes inside the RPM.

So kernel '-2-' shouldn't be used for compilation?

BR

-Frank

Signature 'kernel -2-'
#######################################################################################
rpm -qip kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.x86_64.rpm
Name : kernel-lustre-source Relocations: /usr/src

Version : 2.6.27.29 Vendor: (none)
Release : 0.1_lustre.1.8.1.1 Build Date: Tue 06 Oct 2009

02:45:56 PM CEST

Install Date: (not installed) Build Host:
x86-build-1.co.cfs

Group : Development/Sources Source RPM:
kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.src.rpm
Size : 307849497 License: GPL v2 only

Signature : (none)
URL : http://www.kernel.org/

Summary : The Linux Kernel Sources
Description :
Linux kernel sources with many fixes and improvements.

Authors:
--------
Linus Torvalds <torv...@osdl.org>

see /usr/src/linux/CREDITS for more details.

Source Timestamp: 2009-08-15 17:53:59 +0200
GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
GIT Branch: SLE11_BRANCH

Distribution: (none)
#######################################################################################

Signature kernel -1-
#######################################################################################
heckes@zam1178:/tmp/lustre> rpm -qip
kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.src.rpm
Name : kernel-lustre-source Relocations: (not

relocatable)
Version : 2.6.27.29 Vendor: (none)

Release : 0.1_lustre.1.8.1.1 Build Date: Fri 30 Oct 2009
10:24:50 PM CET

Install Date: (not installed) Build Host:
x86-build-1.co.cfs

Group : Development/Sources Source RPM: (none)
Size : 71216064 License: GPL v2 only

Signature : (none)
URL : http://www.kernel.org/

Summary : The Linux Kernel Sources
Description :
Linux kernel sources with many fixes and improvements.

Authors:
--------
Linus Torvalds <torv...@osdl.org>

see /usr/src/linux/CREDITS for more details.

Source Timestamp: 2009-08-15 17:53:59 +0200
GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
GIT Branch: SLE11_BRANCH

Distribution: (none)
####################################################################

> report about the RPM you are trying to install? If it's a Sun built RPM
> for the patches Lustre kernel for SLES11 it should say:
>
> Name : kernel-lustre-default-base Relocations: (not relocatable)
> Version : 2.6.27.29 Vendor: (none)
> Release : 0.1_lustre.1.8.1.1 Build Date: Tue 06 Oct 2009 06:43:49 AM MDT
> Install Date: (not installed) Build Host: x86-build-1.co.cfs
> Group : System/Kernel Source RPM:
> kernel-lustre-default-2.6.27.29-0.1_lustre.1.8.1.1.nosrc.rpm
> Size : 67685941 License: GPL v2 only
> Signature : (none)
> URL : http://www.kernel.org/
> Summary : Base Modules of the Standard Kernel
> Description :
> The standard kernel for both uniprocessor and multiprocessor systems.
>
> This package contains only the base modules, required in all installs.
>
>
>
> Source Timestamp: 2009-08-15 17:53:59 +0200
> GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
> GIT Branch: SLE11_BRANCH
>
> Cheers,
> b.
>

[Brian J. Murrell]

On Thu, 2009-11-26 at 15:37 +0100, Frank Heckes wrote:
> Hello Brian,

Hi,

> Well, I downloaded two 'source' files:

Hrm. Why are you dealing with source files? Does our already-built
binary kernel RPMs not suit your environment for some reason?

> -1- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.src.rpm
> -2- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.x86_64.rpm
>
> I used the second for the compilation since the first only install stuff
> in /usr/src/packages/SOURCE and some more complicated procedure has to
> be used for compilation.

The first is a source rpm which is built using the rpmbuild command.

> Entries for /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1

Yes.

> and /lib/modules-2.6.27.29-0.1_lustre.1.8.1.1

Well, just the /lib/modules/2.6.27.29-0.1_lustre.1.8.1.1-default/source
symlink so this is really quite irrelevant. It's
the /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1 tree that you are
interested in.

> will be created when installing rpm '-2-'.

> Running 'make rpm' leads to
> an RPM with the specified install pathes inside the RPM.

Can you tell me what the first 10 lines
of /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1-obj/x86_64/default/Makefile say? You might need to adjust some of those lines to make the version say what you want it to say.

But most definitely, things are a lot easier if you can use our binary
RPM packages. I'd be interested in knowing why they are not suitable
for you.

> So kernel '-2-' shouldn't be used for compilation?

That should be fine.

b.

[Frank Heckes]

Hello Brian,

first of all thanks for your patience and answers so far.

> On Thu, 2009-11-26 at 15:37 +0100, Frank Heckes wrote:
> > Hello Brian,
>
> Hi,
>
> > Well, I downloaded two 'source' files:
>
> Hrm. Why are you dealing with source files? Does our already-built
> binary kernel RPMs not suit your environment for some reason?
>

No, no I like the idea a lot, but unfortunately the kernel didn't boot
on the hardware we trying to install them (IBM pizzaboxes), even after
rebuilding the initrd, Systemmap... to extend the (initial) driver list.
So I decided to built the kernel from source. Here the system boots as
it should after installing it to one of the nodes of the (test)
cluster.
And of course there's also a small piece of (childlike) curiosity, too.

> > -1- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.src.rpm
> > -2- kernel-lustre-source-2.6.27.29-0.1_lustre.1.8.1.1.x86_64.rpm
> >
> > I used the second for the compilation since the first only install stuff
> > in /usr/src/packages/SOURCE and some more complicated procedure has to
> > be used for compilation.
>
> The first is a source rpm which is built using the rpmbuild command.
>
> > Entries for /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1
>
> Yes.
>
> > and /lib/modules-2.6.27.29-0.1_lustre.1.8.1.1
>
> Well, just the /lib/modules/2.6.27.29-0.1_lustre.1.8.1.1-default/source
> symlink so this is really quite irrelevant. It's
> the /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1 tree that you are
> interested in.
>
> > will be created when installing rpm '-2-'.
>
> > Running 'make rpm' leads to
> > an RPM with the specified install pathes inside the RPM.
>
> Can you tell me what the first 10 lines
> of /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1-obj/x86_64/default/Makefile say? You might need to adjust some of those lines to make the version say what you want it to say.
>
> But most definitely, things are a lot easier if you can use our binary
> RPM packages. I'd be interested in knowing why they are not suitable
> for you.
>

I fully agree. I would to the ready made RPM's if it would be possible.
(see above).

Here're the Makefile's first 10 lines:

node006:~ # head
-10 /usr/src/linux-2.6.27.29-0.1_lustre.1.8.1.1-obj/x86_64/default/Makefile
# Automatically generated
by ../../../linux-2.6.27.29-0.1_lustre.1.8.1.1/scripts/mkmakefile: don't
edit

VERSION = 2
PATCHLEVEL = 6

lastword = $(word $(words $(1)),$(1))
makedir := $(dir $(call lastword,$(MAKEFILE_LIST)))

MAKEARGS := -C ../../../linux-2.6.27.29-0.1_lustre.1.8.1.1
MAKEARGS += O=$(if $(patsubst /%,,$(makedir)),$(CURDIR)/)$(patsubst %/,
%,$(makedir))

> > So kernel '-2-' shouldn't be used for compilation?
>
> That should be fine.
>

Okay. That's the one I used.

[Brian J. Murrell]

On Mon, 2009-11-30 at 13:21 +0100, Frank Heckes wrote:
> Hello Brian,

Hi Frank,

> first of all thanks for your patience and answers so far.

NP.

> No, no I like the idea a lot, but unfortunately the kernel didn't boot
> on the hardware we trying to install them (IBM pizzaboxes), even after
> rebuilding the initrd, Systemmap... to extend the (initial) driver list.

Hrm. Does the Suse-supplied kernel boot those machines or does it have
the same problems? I just want to isolate whether this is a problem
unique to our kernel build or whether it's a problem with the upstream
(Suse supplied) kernel.

> So I decided to built the kernel from source. Here the system boots as
> it should after installing it to one of the nodes of the (test)
> cluster.

What do you do differently than is being done by our build? Do you
change anything in the source-tree before you build? Probably it would
be great to have a complete transcript of what you do once you have
downloaded the kernel-lustre-source package from our download site.

> And of course there's also a small piece of (childlike) curiosity, too.

:-)

> I fully agree. I would to the ready made RPM's if it would be possible.
> (see above).

Indeed. In fact rather than copying what could be some very copious
data to this list, can you open a bug in our bugzilla and report back
here for me (and the rest of the readers) what the ticket number is?

> Here're the Makefile's first 10 lines:

Unfortunately it was not enough. Once you have opened the ticket as per
above, please attach the complete Makefile.

b.