linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Stefan Helfert <stefan.helfert@mpi-hd.mpg.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] disk add means trouble: vgscan -- invalid i/o protocol version 5
Date: Mon, 16 Apr 2001 20:34:18 +0200	[thread overview]
Message-ID: <3ADB3B2A.B28AC133@mpi-hd.mpg.de> (raw)

Dear list,

I was running a stable configuration until yesterday:
several SCSI disks with standard partitions, two IDE disks, only one IDE
disk (Maxtor 40Gig /dev/hda) holding a LVM partition. LVM version that
of 
SuSE 7.0, that was lvm-0.8 Build 111 from SuSE.

When I added a 60 GB Maxtor IDE as primary slave, I found that vgscan
only
throws an "invalid i/o protocol" error. Upgrading to a SuSE 7.0 update
lvm did not help. Upgrading to the SuSE 7.1 lvm-0.9.1_beta-3 did not
help
except detailing the error "... protocol version 5".

When detaching the 60 GB disk, everything works again. (The 60 Gig disk 
is empty, it did not hold a partition table -- and it does not work with
a
partition table and some partition either.)

Any ideas ? (The 40Gig disk is in dire need of replacement, and this
configuration should be used over the weekend to move the data).

Let me stress this:
the configuration had been working flawlessly before, and I checked that
/dev/lvm is around.


Stefan

bash-2.04# vgscan -d                                                   
<1> lvm_get_iop_version -- CALLED
<22> lvm_check_special -- CALLED
<22> lvm_check_special -- LEAVING
<1> lvm_get_iop_version -- AFTER ioctl ret: 0 
<1> lvm_get_iop_version -- LEAVING with ret: 5   
vgscan -- invalid i/o protocol version 5

             reply	other threads:[~2001-04-16 18:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 18:34 Stefan Helfert [this message]
2001-04-16 19:28 ` [linux-lvm] disk add means trouble: vgscan -- invalid i/o protocol version 5 AJ Lewis
2001-04-17  9:53   ` Stefan Helfert
2001-04-19 23:28   ` Stefan Helfert
2001-04-20 10:49     ` Patrick Caulfield
2001-04-24 18:53       ` Stefan Helfert
2001-04-25  7:39         ` Patrick Caulfield

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=3ADB3B2A.B28AC133@mpi-hd.mpg.de \
    --to=stefan.helfert@mpi-hd.mpg.de \
    --cc=linux-lvm@sistina.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).