From: Tom Dawes-Gamble <tmdg@avbrief.com>
To: Franken Klaus <Klaus.Franken@fth2.siemens.de>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] 2.2.15 Kernel LVM 0.8 vgscan -- invalid i/o proto
Date: Thu, 11 May 2000 17:50:50 +0000 (UTC) [thread overview]
Message-ID: <200005111750.RAA15892@lindbergh.avbrief.com> (raw)
In-Reply-To: <31A612FE6020D2119F6400A0C9B67EBB0381B0EF@FTHW901E> from "Franken Klaus" at May 11, 2000 06:01:41 PM
On Thu May 11 16:01:41 2000 Franken Klaus wrote:-
>
> > -----Original Message-----
> > From: Tom Dawes-Gamble [mailto:tmdg@avbrief.com]
> > Sent: Thursday, May 11, 2000 5:39 PM
> > To: linux-lvm@msede.com
> > Subject: [linux-lvm] 2.2.15 Kernel LVM 0.8 vgscan -- invalid i/o
> > protocol version
> >
> > So. now I'm out of things to try I tought about using a
> > 2.3.X kernel but
> > I really don't want to use a beta kernel.
> >
> > The distribution I'm using is RedHat 6.2 (Zoot).
> >
> > So what should I try next.
>
> You don't need a newer kernel. The format changed between <= 0.8 and 0.8final.
> You have to re-create your physical volumes and to re-compile the new lvm-utils.
>
I did some more digging and found the 2.2.13 patch only gives you
#define LVM_DRIVER_IOP_VERSION 5
The 0.8final requires
#define LVM_DRIVER_IOP_VERSION 6
So I grabed lvm_0.8-pre02.10.1999.tar.gz
That gave me the lvm tools that matched the kernel :-)
So now I have disk space to spare I will look at some of the 2.3.X patches
and see if they go on to the 2.2.15 kernel :-)
Regards,
Tom.
--
Tom Dawes-Gamble Email: tmdg@avbrief.com
next prev parent reply other threads:[~2000-05-11 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 16:01 [linux-lvm] 2.2.15 Kernel LVM 0.8 vgscan -- invalid i/o proto col version Franken Klaus
2000-05-11 17:50 ` Tom Dawes-Gamble [this message]
2020-11-27 16:17 ` [linux-lvm] 2.2.15 Kernel LVM 0.8 vgscan -- invalid i/o proto Michael Marxmeier
2000-05-12 8:14 ` Heinz Mauelshagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200005111750.RAA15892@lindbergh.avbrief.com \
--to=tmdg@avbrief.com \
--cc=Klaus.Franken@fth2.siemens.de \
--cc=linux-lvm@msede.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).