From: "Eric M. Hopper" <hopper@omnifarious.mn.org>
To: Adam Crews <acrews@cisco.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] invalid i/o protocal version
Date: Thu, 13 Jul 2000 19:42:29 -0500 [thread overview]
Message-ID: <20000713194229.A32516@omnifarious.mn.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0007131531430.3258-100000@scooby.cisco.com>; from acrews@cisco.com on Thu, Jul 13, 2000 at 03:55:07PM -0700
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Thu, Jul 13, 2000 at 03:55:07PM -0700, Adam Crews wrote:
> I have re-compiled the lvm tools against the 2.2.16 src and libs, but
> I get the same message.
>
> How can I fix this, or what other info is needed to figure out what is
> happening?
I'm betting you didn't install the older versions of the
executables. Look carefully at which version of the LVM you're patching
your kernel to, and make sure that's the version of the utilities you're
using.
The error message you're getting means that the utility versions
don't match up with the kernel module/patch version.
Have fun (if at all possible),
--
Its name is Public Opinion. It is held in reverence. It settles everything.
Some think it is the voice of God. Loyalty to petrified opinion never yet
broke a chain or freed a human soul. ---Mark Twain
-- Eric Hopper (hopper@omnifarious.mn.org http://www.omnifarious.org/~hopper) --
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-07-14 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 12:11 [linux-lvm] *** LVM patch for kernel 2.2.16 is avaible !! *** Andreas Rey
2000-06-22 14:54 ` Christoph Hellwig
2000-06-23 5:39 ` Andreas Rey
[not found] ` <005101c000cd$f3be3b00$17d235c3@miguel>
2000-07-10 9:55 ` Andreas Rey
2000-07-13 22:55 ` [linux-lvm] invalid i/o protocal version Adam Crews
2000-07-14 0:42 ` Eric M. Hopper [this message]
2000-07-14 1:31 ` Brian Poole
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=20000713194229.A32516@omnifarious.mn.org \
--to=hopper@omnifarious.mn.org \
--cc=acrews@cisco.com \
--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