Linux LVM users
 help / color / mirror / Atom feed
From: "Verloove, Olivier" <olivier_verloove@merck.com>
To: linux-lvm@msede.com
Subject: RE: [linux-lvm] Bonehead problem
Date: Thu, 11 Mar 1999 08:40:42 -0500	[thread overview]
Message-ID: <199903111341.OAA07416@e35.msede.com> (raw)

I have the same problem (Linux 2.2.2 + LVM 0.6).
With or without lvm module loaded, I get:
	vgscan -- invalid i/o protocol version

Is there another module which should be loaded at the same time ?
lsmod gives me:
	lvm	26960	0  (unused)

Thanks.
Olivier Verloove

> ----------
> From:
> ishamael@erroneous.demon.co.uk[SMTP:ishamael@erroneous.demon.co.uk]
> Sent: 	Thursday, 11 Mar, 1999 1:25
> To: 	linux-lvm@msede.com
> Subject: 	Re: [linux-lvm] Bonehead problem
> 
> Shawn Leas wrote:
> >When I upgraded to v0.6 from v0.5alpha, I end up having
> >to keep the old v0.5 version of vgscan around.
> >
> >Reason? Well, this is WEIRD... v0.6 vgscan always errs out
> >with 96, or, invalid IO/protocol version. Then, I use v0.5
> >vgscan, and the same happens. Then, I use v0.6 vgscan again,
> >and IT WORKED!
> >
> >What the hell is going on?
> 
> Did you build lvm as a module? _insmod lvm_ worked for me, after several
> hours 
> of profound confusion.
> 
> -michael
> -- 
> St michael (mainly) Erroneous   http://www.erroneous.demon.co.uk/
> "It's ok to be bitter and twisted,
>  Provided you don't mind leaving a nasty taste in your own mouth."
> 
> 

             reply	other threads:[~1999-03-11 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-11 13:40 Verloove, Olivier [this message]
1999-03-11 14:56 ` [linux-lvm] Bonehead problem Klaus Strebel
  -- strict thread matches above, loose matches on Subject: below --
1999-03-11 15:38 Verloove, Olivier
1999-03-11 15:27 Verloove, Olivier
1999-03-11 15:09 Steve_J_Brueggeman
1999-03-11 15:08 Steve_J_Brueggeman
1999-03-10 23:44 Shawn Leas
1999-03-11  0:25 ` ishamael

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=199903111341.OAA07416@e35.msede.com \
    --to=olivier_verloove@merck.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