Linux LVM users
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@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: Thu, 18 Mar 2004 17:21:05 +0100	[thread overview]
Message-ID: <20040318162105.GA31188@redhat.com> (raw)
In-Reply-To: <1079553784.28897.49.camel@rockley.barbados>

On Wed, Mar 17, 2004 at 08:03:04PM +0000, Nick Gushlow wrote:
> On Wed, 2004-03-17 at 14:31, Heinz Mauelshagen wrote:
> 
> > 
> > Deactivate the VG and rerun pvcreate/vgcfgrestore on the pvremoved disk,
> > vgscan and "vgchange -ay vg2" afterwards.
> > 
> 
> Excellent that did the trick. :-) 
> 
> The only way I found to get rid of the "VGDA in kernel and lvmtab are
> NOT consistent: please run vgscan" error when running 'vgchange -an vg2"
> was to reboot.
> 
> For future reference, is there a better/proper method to get rid of that
> error?

If you are able to deactivate the VG without a reboot, which is rather unlikely
because you've got filesystems on LVs mounted etc., do that.

Unless the LVM metadata gets overwritten externally,
LVM will keep both (metadata on disk and in kernel) in sync.

> 
> Nick.

> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2004-03-18 16:21 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
2004-03-17 20:03       ` Nick Gushlow
2004-03-18 16:21         ` Heinz Mauelshagen [this message]

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=20040318162105.GA31188@redhat.com \
    --to=mauelshagen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox