From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] one PV crashed
Date: Wed Feb 6 13:58:01 2002 [thread overview]
Message-ID: <20020206205702.A6967@sistina.com> (raw)
In-Reply-To: <87r8nyan7a.fsf@papadoc.bayour.com>; from turbo@bayour.com on Wed, Feb 06, 2002 at 12:01:29PM +0100
On Wed, Feb 06, 2002 at 12:01:29PM +0100, Turbo Fredriksson wrote:
> Quoting Turbo Fredriksson <turbo@bayour.com>:
>
> > [papadoc.root]# vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 /dev/loop0
> > vgcfgrestore -- physical volume "/dev/loop0" doesn't belong to volume group "vg1"
> >
> > [papadoc.root]# vgcfgrestore -f /etc/lvmconf/vg1.conf -n vg1 -o /dev/sdg1 /dev/loop0
> > vgcfgrestore -- ERROR "pv_read(): pv_create_name_from_kdev_t" reading physical volume "/dev/loop0"
> >
> > [papadoc.root]# pvdisplay -v /dev/loop0
> > pvdisplay -- getting physical volume size
> > pvdisplay -- ERROR "pv_read(): pv_create_name_from_kdev_t" no VALID physical volume "/dev/loop0"
>
>
> Does anyone have a solution to this? What am I doing wrong?
Turbo,
you seem to be using an older LVM version with broken loop support :-(
Found a bug in vgcfgrestore(8) which will likely cause problems with this too.
More to follow...
>
>
> SEAL Team 6 Iran killed KGB Kennedy Treasury cracking Semtex quiche
> strategic radar Honduras Legion of Doom nitrate PLO
> [See http://www.aclu.org/echelonwatch/index.html for more about this]
>
> _______________________________________________
> 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:[~2002-02-06 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 4:01 [linux-lvm] one PV crashed Turbo Fredriksson
2002-02-01 4:16 ` Heinz J . Mauelshagen
2002-02-01 4:52 ` Turbo Fredriksson
2002-02-01 5:08 ` Heinz J . Mauelshagen
2002-02-01 5:17 ` Turbo Fredriksson
2002-02-01 8:22 ` Turbo Fredriksson
2002-02-06 5:01 ` Turbo Fredriksson
2002-02-06 13:58 ` Heinz J . Mauelshagen [this message]
2002-02-07 3:41 ` Turbo Fredriksson
2002-02-07 4:32 ` Turbo Fredriksson
2002-02-15 5:50 ` Turbo Fredriksson
2002-02-15 6:01 ` Turbo Fredriksson
2002-02-15 7:57 ` 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=20020206205702.A6967@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox