All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvmove errors
Date: Mon Apr 28 03:58:02 2003	[thread overview]
Message-ID: <20030428105154.B27830@sistina.com> (raw)
In-Reply-To: <GNEAKGKKMNLLGBACDNBJEEDGCGAA.carey@itfreedom.com>; from carey@itfreedom.com on Fri, Apr 25, 2003 at 10:46:08AM -0500

On Fri, Apr 25, 2003 at 10:46:08AM -0500, Carey Jung wrote:
> > 
> > Well, _if_ the mapping was bogus that will likely cause overwrites.
> > No way to redo from start then :(
> >
> 
> Granted.  I think it may have killed (-9) pvmove when it was running.
> 
> How should I have proceeded when I saw the problem?
> 
> Can vgck find and fix these kinds of errors?

vgck is a read only checker. You need to run vgcfgrestore to restore
valid metadata to your PVs. Because you weren't able to change the VG
configuration after the pvmove problem, you should get your most recent 
configuration before the move back (and therefore your data :)

Please upgrade to 1.0.7 (and think about using LVM2.0 which we'll release soon)

> 
> Thanks much,
> Carey
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.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                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-04-28  3:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:49 [linux-lvm] pvmove errors Carey Jung
2003-04-25  4:41 ` Heinz J . Mauelshagen
2003-04-25  8:14   ` Carey Jung
2003-04-25 10:03     ` Heinz J . Mauelshagen
2003-04-25 10:46       ` Carey Jung
2003-04-28  3:58         ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-31  7:17 Tom Lanyon
2006-01-31  8:10 ` Zac Slade
2006-01-31 23:26   ` Tom Lanyon
2006-02-01  4:03     ` Zac Slade

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=20030428105154.B27830@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.