Skip to contentSkip to conversation

LVM-1.0.1-rc4 and kernel-2.2.19 patch

linux-lvm Philippe Lefevre 4 participants 4 messages Oct 20, 2001 – Oct 22, 2001

lore
Share & tools
lore
#0 lore raw

Hello all,

I had to update my current kernel (2.2.17) to 2.2.19 with ext3 but I totaly forget to check if a patch were created for it to support LVM-1.0.1-rc4 (which runs fine for me with K2.4.10, thank you LVM team !!)

I was able to build one using the rawio patch designed to 2.2.18 and easily fixing two small problems (two hunks were failed) but I'm tiedous to apply it like this.

What do you think about that ? are there any plans for a 2.2.19 patch
??
using 2.2.18 fragments coud it be a solution ?
shoud I getting back to Kernel 2.2.18 ?

Thanks for any answer,
PhiL

Signature · 4 lines
----------------------------------------------------------------------
Linux 2.2.17 | Philippe Lefevre   E-mail: [email protected] |  =°)
             |                                                |  /\\
----------------------------------------------------------------_\_V--
#1 lore raw

[linux-lvm] can't pvcreate more than 64 dasds on Linux/390

I am using lvm-0.9.1_beta7-1 with TurboLinux6.5(2.2.19) over IBM mainframe S/390. I tried to pvcreate 200 dasds(disks) together, than I'll make them a vg, totally disk space around 500G.
I can work with dasds whose major number is 94 (that is, 64 dasds in
total)all right. However, I fails to pvcreate those dasds whose major number is 253, 252.... The message is:

[root@host96 block]# pvcreate /dev/dasdb[st]1 pvcreate -- invalid physical volume name "/dev/dasdbs1"

I traced lvm kernel source and found that in
/usr/src/linux-2.2.19/include/linux/major.h, only dasd with major number 94 is defined. I think that's the reason pvcreate thought those dasds are invalid.
Any Solutions?

#2 lore raw
In reply to Philippe Lefevre
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Philippe" == Philippe Lefevre <[email protected]> writes:

Philippe> Hello all, I had to update my current kernel (2.2.17) Philippe> to 2.2.19 with ext3 but I totaly forget to check if a Philippe> patch were created for it to support LVM-1.0.1-rc4 Philippe> (which runs fine for me with K2.4.10, thank you LVM team Philippe> !!)

Philippe> I was able to build one using the rawio patch designed Philippe> to 2.2.18 and easily fixing two small problems (two Philippe> hunks were failed) but I'm tiedous to apply it like Philippe> this.

2.2.18 would work fine but there was a problem with a change in rc4 - check the archive; this is fixed in CVS but I haven't had any success in connecting to CVS yet so I haven't so what was required to fix it and nobody else seems to have had time yet either. My hope is that there will be a rc5 soon with this fix in.

Sincerely,

Adrian Phillips

Signature · 3 lines
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]
#3 lore raw
In reply to Philippe Lefevre
Quoted 7 lines · Philippe Lefevre

Hello all,

I had to update my current kernel (2.2.17) to 2.2.19 with ext3 but I totaly forget to check if a patch were created for it to support LVM-1.0.1-rc4 (which runs fine for me with K2.4.10, thank you LVM team !!)

Quoted 8 lines

I was able to build one using the rawio patch designed to 2.2.18 and easily fixing two small problems (two hunks were failed) but I'm tiedous to apply it like this.

What do you think about that ? are there any plans for a 2.2.19 patch
??
using 2.2.18 fragments coud it be a solution ?
shoud I getting back to Kernel 2.2.18 ?

The code in CVS patches cleanly against 2.2.19, though I'm not sure whether ext3 will affect it or not.

patrick