From: Heinz Mauelshagen <heinzm@redhat.com>
To: nick@gushlow.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM Problems when moving data off a PV
Date: Wed, 17 Mar 2004 15:31:06 +0100 [thread overview]
Message-ID: <20040317143106.GA14348@redhat.com> (raw)
In-Reply-To: <1079478248.28877.6.camel@rockley.barbados>
On Tue, Mar 16, 2004 at 11:04:09PM +0000, Nick Gushlow wrote:
> On Mon, 2004-03-15 at 12:34, Heinz Mauelshagen wrote:
>
> >
> > You need to select the last valid metadata backup of vg2 from /etc/lvmconf
> > (check it with vgcfgrestore -ll -f /etc/lvmconf/vg2.conf[.#.old]; see
> > 'man vgcfgrestore for metadata archive file names) and restore it.
> >
> > Say vg.conf.1.old is the valid one:
> >
> > for dev in AllPVsOfVG2 # list all PVs reported by vgcfgrestore -ll above
> > do
> > pvcreate -ff $dev
> > vgcfgrestore -f /etc/lvmconf/vg.conf.1.old $dev
> > done
> > vgscan
> > vgchange -ay vg2
> >
>
>
> That did the trick thanks. :-)
>
> Of course in a moment of not concentrating I messed things up again. I
> still had pvremove on the disk from when I previously installed the lvm2
> tools, and although I wanted to do a vgreduce I did a pvremove. Even
> when it kicked up an error I just followed what it said and typed
> pvremove -ff. oops :-/
>
> Now I get a a similar error as before with vgscan, and other tools give
> a 'VGDA in kernel and lvmtab are NTO consistent: please run vgscan'
> error.
>
> I tried re-running what you suggested above but vgcfgrestore gives a
> 'can't restore part of active volume group "vg2"' error.
>
> Is there anyway to recover from my stupidity (other than a lobotomy!)?
:)
Deactivate the VG and rerun pvcreate/vgcfgrestore on the pvremoved disk,
vgscan and "vgchange -ay vg2" afterwards.
>
>
>
> _______________________________________________
> 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 GmbH
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-03-17 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 13:32 [linux-lvm] LVM Problems when moving data off a PV Nick Gushlow
2004-03-15 12:34 ` Heinz Mauelshagen
2004-03-15 21:02 ` Nick Gushlow
2004-03-16 23:04 ` Nick Gushlow
2004-03-17 14:31 ` Heinz Mauelshagen [this message]
2004-03-17 20:03 ` Nick Gushlow
2004-03-18 16:21 ` 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=20040317143106.GA14348@redhat.com \
--to=heinzm@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=nick@gushlow.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.