From: James Pattinson <jamesp@aethos.co.uk>
To: linux-lvm@msede.com
Subject: [linux-lvm] vgscan -- invalid i/o protocol version
Date: Wed, 30 Jun 1999 16:42:41 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.10.9906301639130.2611-100000@fuse.aethos.co.uk> (raw)
Anyone seen this error msg before?
I'm running RH6 with kernel 2.2.10 and the LVM patches applied. I
originially tried to follow the HOWTO but on the first command i got:
pvcreate -- ERROR: "/etc/lvmtab" doesn't exist; please run vgscan
so i ran vgscan and got the message in the subject line. It's possible I'm
being really thick and I don't really know what I'm doing. Do I need the
devfs patches too?
I'm new to lvm-on-linux but I love it on HP-UX.
Cheers!
James
next reply other threads:[~1999-06-30 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-30 15:42 James Pattinson [this message]
1999-06-30 22:43 ` [linux-lvm] vgscan -- invalid i/o protocol version Rolf Jakob
1999-07-01 11:35 ` Heinz Mauelshagen
2020-11-27 16:16 ` Michael Marxmeier
1999-07-01 9:17 ` James Pattinson
1999-07-01 11:46 ` Heinz Mauelshagen
[not found] <852567A1.0047037F.00@USCOMM02.aholdusa.com>
1999-07-01 16:04 ` 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=Pine.LNX.4.10.9906301639130.2611-100000@fuse.aethos.co.uk \
--to=jamesp@aethos.co.uk \
--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).