From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Lost free PV -> error reading VG
Date: Thu Feb 19 10:39:07 2004 [thread overview]
Message-ID: <20040219121317.GB32407@redhat.com> (raw)
In-Reply-To: <15173.1077120428@www19.gmx.net>
On Wed, Feb 18, 2004 at 05:07:08PM +0100, Stefan Jenkner wrote:
> Hi Folks!
>
> I had a vg "debian" with the pvs /dev/hda2 /dev/hda3 /dev/hda4
> I wanted to remove /dev/hda4, so i did: pvmove -v /dev/hda4
> Everything went well, so I removed /dev/hda4, but _without_ the use of:
> vgreduce debian /dev/hda4 :-(
D'oh!
> I also did: pvcreate /dev/hda4 , so /dev/hda4 seems to be an empty pv, and
> it does not know that it belongs
> to the vg "debian".
Must have been a "pvcreate -ff /dev/hda4" to achive the recreation,
while /dev/hda4 was a member of VG "debian" still.
>
> And now, I get:
>
> root@ttyp0[root]# vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of
> volume group "debian" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> group
>
> root@ttyp0[root]# pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hda2" is associated to unknown VG "debian" (run
> vgscan)
> pvscan -- inactive PV "/dev/hda3" is associated to unknown VG "debian" (run
> vgscan)
> pvscan -- inactive PV "/dev/hda4" is in no VG [23.85 GB]
> pvscan -- total: 3 [57.24 GB] / in use: 2 [33.38 GB] / in no VG: 1 [23.85
> GB]
>
> How can I recover my vg? There are no backups :-(
/me wonders how often we mentioned to take backups of /etc/lvmconf/* yet :->
> How can I tell the vg "debian" to do not use: the empty pv /dev/hda4?
> Or, how can I tell /dev/hda4 that it belongs to the vg "debian"?
> There is no lvmconf too :-(
lvm2 tools are able to reduce VGs by missing PVs.
Fetch and build them and run "vgreduce --removemissing debian".
Afterwards continue with LVM1 (unless you want to migrate to LVM2 anyway):
# vgscan -f
# vgchange -ay
>
> What additional information do you need to be able to help me?
>
> Thanks
> Stefan
>
> --
> GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
> jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat, Inc.
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-02-19 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 11:07 [linux-lvm] Lost free PV -> error reading VG Stefan Jenkner
2004-02-19 10:39 ` Heinz Mauelshagen [this message]
2004-02-19 12:51 ` Christian Reiss
2004-02-20 10:35 ` Heinz Mauelshagen
2004-02-20 3:20 ` Stefan Jenkner
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=20040219121317.GB32407@redhat.com \
--to=mauelshagen@redhat.com \
--cc=linux-lvm@redhat.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