[linux-lvm] Successful Upgrade to 1.0 with RH 7.1

[linux-lvm] Successful Upgrade to 1.0 with RH 7.1

[gerry]

I thought I'd share my experience with my upgrade from beta 7 to 1.0 on
Redhat's 2.4.3-12 kernel...

First, I had already patched the 2.4.3-12 kernel and successfully
installed lvm beta 7.  This went without problems following the
instructions in the PATCHES directory.

I downloaded the new lvm 1.0 tarball and tried to patch the existing
patched kernel source.  That didn't work very well so I immediately gave
up on that approach and started with a clean Redhat 2.4.3-12 kernel.  The
patch was created properly and installed without errors.

I then rebuilt the kernel using the saved .config file from the old
working kernel.  No problems with the kernel compile.  Being on a roll I
did the make file in the LVM/1.0 directory, then updated the existing pv's
using pvversion.  Finally, I did a make install and rebooted.

Everything came up without a single error.  I'm now running on lvm 1.0 and
all data is intact!

Great work and congratulations to the LVM team!

PS. Notice that I started with a clean Redhat 2.4.3-12 kernel NOT the
standard kernel.  Whatever changes have been made by Redhat do not affect
LVM.


Gerry
-- 
"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer

Re: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1

[Heinz J . Mauelshagen]

Gerry,

thanks a lot for your kind feedback.

FYI:
in order to make the upgrade to > 0.9.1 Beta 8 even smoother, my team came
up with a slicker solution avoiding the metadata upgrade process
completely, which caused sleepless nights ;-) for some users and Linux
distributors. Sorry folks!

Already announced and available at www.sistina.com as LVM 1.0.1-rc1.

FYI: users, who already have successfully updated to 1.0 *don't* need it
     but users who didn't can install 1.0.1-rc1 *and* run it with their given
     VGs without a seperate upgrade process (kudos to my team and Joe Thornber
     in particular :-)

Regards,
Heinz    -- The LVM Guy --


On Sun, Aug 19, 2001 at 05:39:26PM -0400, gerry@dorfam.ca wrote:
> I thought I'd share my experience with my upgrade from beta 7 to 1.0 on
> Redhat's 2.4.3-12 kernel...
> 
> First, I had already patched the 2.4.3-12 kernel and successfully
> installed lvm beta 7.  This went without problems following the
> instructions in the PATCHES directory.
> 
> I downloaded the new lvm 1.0 tarball and tried to patch the existing
> patched kernel source.  That didn't work very well so I immediately gave
> up on that approach and started with a clean Redhat 2.4.3-12 kernel.  The
> patch was created properly and installed without errors.
> 
> I then rebuilt the kernel using the saved .config file from the old
> working kernel.  No problems with the kernel compile.  Being on a roll I
> did the make file in the LVM/1.0 directory, then updated the existing pv's
> using pvversion.  Finally, I did a make install and rebooted.
> 
> Everything came up without a single error.  I'm now running on lvm 1.0 and
> all data is intact!
> 
> Great work and congratulations to the LVM team!
> 
> PS. Notice that I started with a clean Redhat 2.4.3-12 kernel NOT the
> standard kernel.  Whatever changes have been made by Redhat do not affect
> LVM.
> 
> 
> Gerry
> -- 
> "The lyfe so short, the craft so long to learne"  Geoffrey Chaucer
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

RE: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1

[Erick Calder]

> started with a clean Redhat 2.4.3-12 kernel

I'm running a stock 7.0 version and downloaded the above-named kernel...
patch and compilation went ok but I can't seem to make modules... I get a
ton of errors... I realised that I needed to install the kernel-headers for
this version but even after that I can't make the modules... I've seen a lot
of other guys out there suffering with this but no solutions... I even tried
changing the HOSTCC to "kgcc" in the Makefile but no dice.... so I'm
wondering what you did right... can you share?

(sorry everyone else that isn't running RH)

-----Original Message-----
From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of gerry@dorfam.ca
Sent:	Sunday, August 19, 2001 2:39 PM
To:	linux-lvm@sistina.com
Subject:	[linux-lvm] Successful Upgrade to 1.0 with RH 7.1

I thought I'd share my experience with my upgrade from beta 7 to 1.0 on
Redhat's 2.4.3-12 kernel...

First, I had already patched the 2.4.3-12 kernel and successfully
installed lvm beta 7.  This went without problems following the
instructions in the PATCHES directory.

I downloaded the new lvm 1.0 tarball and tried to patch the existing
patched kernel source.  That didn't work very well so I immediately gave
up on that approach and started with a clean Redhat 2.4.3-12 kernel.  The
patch was created properly and installed without errors.

I then rebuilt the kernel using the saved .config file from the old
working kernel.  No problems with the kernel compile.  Being on a roll I
did the make file in the LVM/1.0 directory, then updated the existing pv's
using pvversion.  Finally, I did a make install and rebooted.

Everything came up without a single error.  I'm now running on lvm 1.0 and
all data is intact!

Great work and congratulations to the LVM team!

PS. Notice that I started with a clean Redhat 2.4.3-12 kernel NOT the
standard kernel.  Whatever changes have been made by Redhat do not affect
LVM.


Gerry
--
"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

RE: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1

[gerry]

On Sat, 25 Aug 2001, Erick Calder wrote:

> > started with a clean Redhat 2.4.3-12 kernel
>
> I'm running a stock 7.0 version and downloaded the above-named kernel...
> patch and compilation went ok but I can't seem to make modules... I get a
> ton of errors... I realised that I needed to install the kernel-headers for
> this version but even after that I can't make the modules... I've seen a lot
> of other guys out there suffering with this but no solutions... I even tried
> changing the HOSTCC to "kgcc" in the Makefile but no dice.... so I'm
> wondering what you did right... can you share?
>
> (sorry everyone else that isn't running RH)
>
Well, all I did was follow the install instructions that came with the LVM
tarball to create the patch.  I didn't do anything special.  I wasn't able
to successfully install the newly created patch until I replaced the
kernel source with a fresh "clean" rpm.

Are you running the 2.4 kernel or are you using 2.2?  That makes a big
difference as you need to add the raw.io patch to the 2.2 kernel.  Also, I
don't believe that the shipped RH kernel config enables LVM as a default.

I still have the patch for 2.4.3-12.  However, I doubt it would work for a
7.0 install since I'm using 7.1.


Gerry
-- 
"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer

[linux-lvm] troubled Guiness

[Erick Calder]

Hi all,

I'm running RH 7.0 (Guiness) with the 2.2.16-22 kernel and gcc-2.96-85 and
have downloaded the Linus 2.4.9 stock kernel which I'm trying to make... I
built the patch and applied it with no apparent problem but when I try to
build the kernel I get the errors in the log below.

has anyone been here before?

1k thx - e

make[2]: Leaving directory `/usr/src/linux/drivers/ide'
make -C md
make[2]: Entering directory `/usr/src/linux/drivers/md'
make all_targets
make[3]: Entering directory `/usr/src/linux/drivers/md'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-tri
graphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpre
ferred-stack-boundary=2 -march=i586    -c -o lvm.o lvm.c
lvm.c:2329:71: macro "min" requires 3 arguments, but only 2 given
lvm.c:2343:59: macro "min" requires 3 arguments, but only 2 given
lvm.c: In function `__extend_reduce':
lvm.c:2329: `min' undeclared (first use in this function)
lvm.c:2329: (Each undeclared identifier is reported only once
lvm.c:2329: for each function it appears in.)
lvm.c:2280: warning: `end' might be used uninitialized in this function
lvm.c:2339: warning: `end' might be used uninitialized in this function
make[3]: *** [lvm.o] Error 1
make[3]: Leaving directory `/usr/src/linux/drivers/md'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/drivers/md'
make[1]: *** [_subdir_md] Error 2
make[1]: Leaving directory `/usr/src/linux/drivers'
make: *** [_dir_drivers] Error 2

-----Original Message-----
From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of gerry@dorfam.ca
Sent:	Sunday, August 26, 2001 6:21 AM
To:	linux-lvm@sistina.com
Subject:	RE: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1

On Sat, 25 Aug 2001, Erick Calder wrote:

> > started with a clean Redhat 2.4.3-12 kernel
>
> I'm running a stock 7.0 version and downloaded the above-named kernel...
> patch and compilation went ok but I can't seem to make modules... I get a
> ton of errors... I realised that I needed to install the kernel-headers
for
> this version but even after that I can't make the modules... I've seen a
lot
> of other guys out there suffering with this but no solutions... I even
tried
> changing the HOSTCC to "kgcc" in the Makefile but no dice.... so I'm
> wondering what you did right... can you share?
>
> (sorry everyone else that isn't running RH)
>
Well, all I did was follow the install instructions that came with the LVM
tarball to create the patch.  I didn't do anything special.  I wasn't able
to successfully install the newly created patch until I replaced the
kernel source with a fresh "clean" rpm.

Are you running the 2.4 kernel or are you using 2.2?  That makes a big
difference as you need to add the raw.io patch to the 2.2 kernel.  Also, I
don't believe that the shipped RH kernel config enables LVM as a default.

I still have the patch for 2.4.3-12.  However, I doubt it would work for a
7.0 install since I'm using 7.1.


Gerry
--
"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer


_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Re: [linux-lvm] troubled Guiness

[Glenn Shannon]

Erick Calder wrote:

>Hi all,
>
>I'm running RH 7.0 (Guiness) with the 2.2.16-22 kernel and gcc-2.96-85 and
>have downloaded the Linus 2.4.9 stock kernel which I'm trying to make... I
>built the patch and applied it with no apparent problem but when I try to
>build the kernel I get the errors in the log below.
>
>has anyone been here before?
>
>1k thx - e
>
>make[2]: Leaving directory `/usr/src/linux/drivers/ide'
>make -C md
>make[2]: Entering directory `/usr/src/linux/drivers/md'
>make all_targets
>make[3]: Entering directory `/usr/src/linux/drivers/md'
>gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-tri
>graphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpre
>ferred-stack-boundary=2 -march=i586    -c -o lvm.o lvm.c
>lvm.c:2329:71: macro "min" requires 3 arguments, but only 2 given
>lvm.c:2343:59: macro "min" requires 3 arguments, but only 2 given
>lvm.c: In function `__extend_reduce':
>lvm.c:2329: `min' undeclared (first use in this function)
>lvm.c:2329: (Each undeclared identifier is reported only once
>lvm.c:2329: for each function it appears in.)
>lvm.c:2280: warning: `end' might be used uninitialized in this function
>lvm.c:2339: warning: `end' might be used uninitialized in this function
>make[3]: *** [lvm.o] Error 1
>make[3]: Leaving directory `/usr/src/linux/drivers/md'
>make[2]: *** [first_rule] Error 2
>make[2]: Leaving directory `/usr/src/linux/drivers/md'
>make[1]: *** [_subdir_md] Error 2
>make[1]: Leaving directory `/usr/src/linux/drivers'
>make: *** [_dir_drivers] Error 2
>
>-----Original Message-----
>From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
>Behalf Of gerry@dorfam.ca
>Sent:	Sunday, August 26, 2001 6:21 AM
>To:	linux-lvm@sistina.com
>Subject:	RE: [linux-lvm] Successful Upgrade to 1.0 with RH 7.1
>
>On Sat, 25 Aug 2001, Erick Calder wrote:
>
>>>started with a clean Redhat 2.4.3-12 kernel
>>>
>>I'm running a stock 7.0 version and downloaded the above-named kernel...
>>patch and compilation went ok but I can't seem to make modules... I get a
>>ton of errors... I realised that I needed to install the kernel-headers
>>
>for
>
>>this version but even after that I can't make the modules... I've seen a
>>
>lot
>
>>of other guys out there suffering with this but no solutions... I even
>>
>tried
>
>>changing the HOSTCC to "kgcc" in the Makefile but no dice.... so I'm
>>wondering what you did right... can you share?
>>
>>(sorry everyone else that isn't running RH)
>>
>Well, all I did was follow the install instructions that came with the LVM
>tarball to create the patch.  I didn't do anything special.  I wasn't able
>to successfully install the newly created patch until I replaced the
>kernel source with a fresh "clean" rpm.
>
>Are you running the 2.4 kernel or are you using 2.2?  That makes a big
>difference as you need to add the raw.io patch to the 2.2 kernel.  Also, I
>don't believe that the shipped RH kernel config enables LVM as a default.
>
>I still have the patch for 2.4.3-12.  However, I doubt it would work for a
>7.0 install since I'm using 7.1.
>
>
>Gerry
>--
>"The lyfe so short, the craft so long to learne"  Geoffrey Chaucer
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
Actually, I got this same problem with the 2.4.9 kernel...I fixed it by 
installing clean source and using lvm1.0-rc1 instead.

Hope this helps.

Glenn

[linux-lvm] core dumps with rc1

[Erick Calder]

Whoa!  I just went to sistina.com (looking for the mailing-list archives)
and thought I had it wrong, I tried sistina.org but no dice, then realised
you guys have redesigned the page!

nice job!! it looks great.

Now for my predicament: As I previously posted, I successfully built LVM
1.0.1rc1 with the Linus 2.4.9 kernel on a Guiness box (RH 7.0).

I've followed the instructions in the INSTALL file except for:

> 10. Add a "vgscan" and a "vgchange -a y" to your startup files
>     (/sbin/init.d/boot with SuSE for eg.) so that the actual volume
>     group configuration is online after each reboot.
>
>     Put a "vgchange -a n" into your shutdown script (/sbin/init.d/halt for
eg.)
>     after dismounting all filesystems.

since I'm not certain of how this is done in RedHat.  I don't know whether
the right thing is to put these commands in /etc/rc.d/rc.sysinit (probably),
/etc/rc.d/rc.local (less likely) or to create an lvm file in
/etc/rc.d/inet.d with links in the /etc/rc?.d (which runlevel to put it in?
I'm so clueless!!).

For now I've just run them manually:

# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group

# vgchange -a y
vgchange -- no volume groups found

I've set the type to 8e of a couple of partitions in a couple of drives as
follows:

Disk /dev/hda: 128 heads, 63 sectors, 589 cylinders
Units = cylinders of 8064 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1         5     20128+  83  Linux
/dev/hda2             6       589   2354688   8e  Linux LVM

Disk /dev/hdc: 16 heads, 63 sectors, 39870 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1   *         1     18266   9206032+  83  Linux
/dev/hdc2         18267     39870  10888416    5  Extended
/dev/hdc5         18267     18787    262552+  83  Linux
/dev/hdc6         18788     19308    262552+  83  Linux
/dev/hdc7         19309     19829    262552+  82  Linux swap
/dev/hdc8         19830     39870  10100632+  8e  Linux LVM

although, in each instance, after "writing" the modifications I got error
messages as follows:

> Command (m for help): w
> The partition table has been altered!
>
> Calling ioctl() to re-read partition table.
> Re-read table failed with error 16: Device or resource busy.
> Reboot your system to ensure the partition table is updated.
>
> WARNING: If you have created or modified any DOS 6.x
> partitions, please see the fdisk manual page for additional
> information.
> Syncing disks.

the above looks worrisome but I've found a number of tutorials that talk
about using fdisk and all of them show the same error message without
reference to what it means... so presumably it's spurious?

anyway, then:

# pvcreate /dev/hda2 /dev/hdc8
Segmentation fault (core dumped)

yikes!

I've looked through the mailing list archives but only found:

http://lists.sistina.com/pipermail/linux-lvm/2001-August/008469.html

what next?

1k thx - e

Re: [linux-lvm] troubled Guiness

[AJ Lewis]

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

On Sun, Aug 26, 2001 at 02:36:44PM -0700, Erick Calder wrote:
> I'm running RH 7.0 (Guiness) with the 2.2.16-22 kernel and gcc-2.96-85 and
> have downloaded the Linus 2.4.9 stock kernel which I'm trying to make... I
> built the patch and applied it with no apparent problem but when I try to
> build the kernel I get the errors in the log below.
> 
> has anyone been here before?

I just responded to Peter Druck about this same problem.  See the thread
with subject "Problems compiling lvm 1.0 and 2.4.x kernel" on this list.

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
This message has been brought to you by the language C and the number F.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

RE: [linux-lvm] troubled Guiness - no longer!

[Erick Calder]

thank you guys for the help and all the work that has gone into this
software.

I got the rc1 version and everything went swimmingly.  I finally have LVM
compiled!!! (yes I did fill out the survey).

now I have to figure out how to use it :)  I'll be working on packaging this
as RPMs next.

- e r i c k

-----Original Message-----
From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of AJ Lewis
Sent:	Monday, August 27, 2001 7:29 AM
To:	linux-lvm@sistina.com
Subject:	Re: [linux-lvm] troubled Guiness

 << File: ATT00036.dat >> On Sun, Aug 26, 2001 at 02:36:44PM -0700, Erick
Calder wrote:
> I'm running RH 7.0 (Guiness) with the 2.2.16-22 kernel and gcc-2.96-85 and
> have downloaded the Linus 2.4.9 stock kernel which I'm trying to make... I
> built the patch and applied it with no apparent problem but when I try to
> build the kernel I get the errors in the log below.
>
> has anyone been here before?

I just responded to Peter Druck about this same problem.  See the thread
with subject "Problems compiling lvm 1.0 and 2.4.x kernel" on this list.

--
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
This message has been brought to you by the language C and the number F.
-----End Obligatory Humorous Quote------------------------------------------

Re: [linux-lvm] troubled Guiness - no longer!

[AJ Lewis]

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

On Mon, Aug 27, 2001 at 12:17:59PM -0700, Erick Calder wrote:
> thank you guys for the help and all the work that has gone into this
> software.
> 
> I got the rc1 version and everything went swimmingly.  I finally have LVM
> compiled!!! (yes I did fill out the survey).

Woohoo!  Thanks!

> now I have to figure out how to use it :)  I'll be working on packaging this
> as RPMs next.

Cool.

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Computer Science: solving today's problems tomorrow.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]