[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: switch from 2.4.24 lvm1 to 2.6.10 lvm 2 problems



On Thu, Feb 03, 2005 at 11:33:08AM +0100, Benedict Verheyen wrote:
> Pigeon wrote:
> > I've just set up a root on LVM - under 2.4.24 - and had a lot of
> > problems similar to this most of which turned out to be due to the LVM
> > shared libraries and the executables in /lib/lvm-10 not being included
> > on the initrd. I too was finding mkinitrd wasn't behaving quite as I
> > expected in certain places. I ended up listing the contents of
> > /lib/lvm-10 and /lib/modules/2.4.24 explicitly in /etc/mkinitrd/files.
> 
> Hhhm. Haven't done that either. It will be /lib/lvm-200 in my case and 
> /lib/modules/2.6.9
> Is it ok to set the dirs or do you have to put all the files in there? 

AIUI you have to list the files explicitly.

> If so, is there a handy script
> to run through the dirs and include them?

Not that I know of; I just redirected the output from 'find', as on
http://pigeon.dyndns.org/stuff/lvm-root/lvm-root.html.

> At work i managed a while ago to get lvm2 up and running on a 2.6.7
> kernel. But that's different
> as i installed sarge which comes with a 2.6.7 kernel.
> I thought, well i can build the kernel already here, install it, and
> then run the scripts from your
> site to include the necessary files in exe and files under /et/mkinitrd.
> Now AGAIN, mkinitrd says this:
>
> cribbage# mkinitrd -o initrd.img-2.6.10.03feb2005-skas3-v7 -r
> /dev/main/lv_root 2.6.10.03feb2005-skas3-v7
> /usr/sbin/mkinitrd: /dev/mapper/main-lv_root: Kernel does not support LVM
>
> cribbage# grep "DM" /boot/config-2.6.10.03feb2005-skas3-v7
> ...
> CONFIG_BLK_DEV_DM=y
> ...
>
> WTF. This must be a mkinitrd bug surely?
> I included it in the kernel, i will to list DM again as module and see
> if that make mkinitrd behave.

I'm using woody, and the woody version of mkinitrd doesn't have that
error message... I downloaded the sarge/sid version from
packages.debian.org and had a (quick) look at the script ('mkinitrd'
is a shell script), and from that quick look it does look like a bug;
it seems to check if the modules exist and if they don't it assumes
the kernel doesn't support LVM, without checking whether the support
has actually been compiled in.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F

Attachment: signature.asc
Description: Digital signature


Reply to: