From: Stefan Helfert <Stefan.Helfert@mpi-hd.mpg.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] disk add means trouble: vgscan -- invalid i/o protocol version 5
Date: Tue, 24 Apr 2001 20:53:03 +0200 [thread overview]
Message-ID: <3AE5CB8F.C3449990@mpi-hd.mpg.de> (raw)
In-Reply-To: 20010420114908.C569@tykepenguin.com
Patrick Caulfield wrote:
>
> On Fri, Apr 20, 2001 at 01:28:42AM +0200, Stefan Helfert wrote:
> > I am reposting this, since I believe I have run into a serious condition
> > here:
> >
> > A stable, running configuration consisted of one IDE disk with one LVM
> > VG on it, and adding another IDE disk leads to a non-working vgscan. If
> > I go back to the one IDE disk configuration, the LVM gets discovered,
> > and adding the second disk again leads to non-working vgscan.
> > I cannot completely rule out any hardware issues here (since the disk
> > with the LVM VG is apparently having lots of SMART redirects and
> > significant access time increases), but I'd like to investigate this
> > vgscan problem further.
> > (Since it reduces my confidence in LVM very much, so much that I am
> > currently killing the LVM on my terabyte raid because I do not want to
> > see anything like that there.)
> >
> > So if anyone has an idea of how to investigate this, I am open to
> > experiments. If not, I'll send the disk back to the manufacturer for
> > replacement.
>
> The first thing to do is to get your kernel and user tools in sync so that
> you don't get th IOP message. If you have a kernel you like then node the LVM
> version number in that kernel and build the tools for that version.
>
> That should get vgscan working after some fashion. If the new disk still seems
> to be causing the problem then please post the error here so we can have a look
> at it.
>
> patrick
My kernel and user tools are in sync (lvm_0.8) and my initial problem
here is that I get the IOP message -- and I get this message out of the
blue. No software changes, no kernel changes, nothing else except adding
another disk drive, the configuration had been running stable since
ages. I do not see anything here except the vgscan error, and the output
of "vgscan -d" is here:
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
??
Stefan
next prev parent reply other threads:[~2001-04-24 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 18:34 [linux-lvm] disk add means trouble: vgscan -- invalid i/o protocol version 5 Stefan Helfert
2001-04-16 19:28 ` 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 [this message]
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=3AE5CB8F.C3449990@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).