[linux-lvm] lvm2 + kernel 2.4.26

[linux-lvm] lvm2 + kernel 2.4.26

[duverger]

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

LVM version:     2.00.16 (2004-05-24)
Library version: 1.00.19-ioctl (2004-07-03)
Driver version:  4.1.0

Lords,

I'm currently testing lvm2. It works well with a 2.6.6 kernel using an
"initrd" created by the "lvm2create_initrd" script.

Problems appear when i use a 2.4.26 kernel (the initrd is created the
same way that for 2.6 kernel). I think it's more related with initrd
kernel code and not lvm code, but maybe with your experience you already
have encoutered that kind of situation.

First strange thing is that even if i create a "linuxrc" executable file
on the root of my initrd, it is never processed. But the "/sbin/init" is
searched and found first instead. It's not the case when i create the
initrd with debian mkinitrd.

"/sbin/init" is a shell script, the problem appears when bash needs to
be launched.

/bin/bash: libdl.so.2 ... no such file or directory ....

"ldd bash" gives me entries to /lib/tls/libc.so.6 and
/lib/tls/libdl.so.2. These two libs are in the right place on the initrd
filesystem.

So, it seems that kernel is able to find the "init" binary on the initrd
file system but not the libs. I thought about lib path problems.

I have created a fake "/sbin/init" staticaly linked that only does a
printf() and an execve(/sbin/init_real) passing LD_LIBRARY_PATH in new
environment (but normally ld.so also checks default directories such as
/lib as it is said in the manpage). My "init" is correctly executed so
this justifies that kernel is able to read the initrd filesystem, enter
in sbin directory and launch a binary.

I've also tried to put library files wherever i could (/, /bin/, ...)
but no effect.

Why it couldn't find files in /lib directory ?
Is there any special patch to apply on 2.4.26 kernel ?


Best regards,

stephane

[-- Attachment #2: Type: text/html, Size: 2232 bytes --]