From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvversion failure
Date: Wed, 25 Jul 2001 21:48:00 +0200 [thread overview]
Message-ID: <20010725214800.D27765@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107251710580.10117-100000@greebo.foobarhouse.com>; from jamesp@foobarhouse.com on Wed, Jul 25, 2001 at 05:11:42PM +0100
On Wed, Jul 25, 2001 at 05:11:42PM +0100, James Pattinson wrote:
> Oops - hate to reply to my own message, but I just noticed the -1 in my
> pvversion command. To clarify, I get the same behaviour if I use -2 as
> well.
Yes, I guessed that already.
My guess is, that the long device pathes trigger a regex bug we didn't hit
during our tests.
Could you switch devfs of and retry pvversion in order
to work around that assumed flaw?
>
> James
>
> On Wed, 25 Jul 2001, James Pattinson wrote:
>
> > Hi
> >
> > Trying to upgrade from beta7 to beta8. I have 2 PVs, neither of which are
> > empty, that belong to a single VG, vg00.
> >
> > When trying to upgrade the PVs to version 2, I get:
> >
> > ./pvversion -1 /dev/ide/host2/bus0/target0/lun0/part1
> > pvversion -- created dummy LV "/dev/vg00/pvversionpart19519" on empty PV
> > "/dev/ide/host2/bus0/target0/lun0/part1"
> > pvversion -- ERROR: pv_display() failed again
> > pvversion -- giving up on "/dev/ide/host2/bus0/target0/lun0/part1"
> >
> > [root@greebo tools]# lvmdiskscan | grep LVM
> > lvmdiskscan -- /dev/ide/host2/bus0/target0/lun0/part1 [ 16.02 GB]
> > Primary LVM partition [0x8E]
> > lvmdiskscan -- /dev/ide/host2/bus1/target0/lun0/part1 [ 16.02 GB]
> > Primary LVM partition [0x8E]
> > lvmdiskscan -- 2 LVM physical volume partitions
> > [root@greebo tools]#
> >
> > It seems the pvversion program thinks my PV is empty, and tries to create
> > a dummy LV on it. But of course it's not empty.
> >
> > I created my PVs, VG and LVs using beta7 kernel and tools not too long
> > ago. Im using devfs as you can see.
> >
> > Any ideas?
> >
> > James
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-07-25 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 15:14 [linux-lvm] pvversion failure James Pattinson
2001-07-25 16:11 ` James Pattinson
2001-07-25 19:48 ` Heinz J . Mauelshagen [this message]
2001-07-25 22:02 ` James Pattinson
2001-07-26 11:07 ` James Pattinson
2001-08-14 13:56 ` Heinz J . 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=20010725214800.D27765@sistina.com \
--to=mauelshagen@sistina.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.