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] vgchange -a y /dev/System fails
Date: Mon Jan 28 03:47:01 2002	[thread overview]
Message-ID: <20020128104258.A24830@sistina.com> (raw)
In-Reply-To: <20020125233533.GK26045@merlins.org>; from marc_lvm@merlins.org on Fri, Jan 25, 2002 at 03:35:33PM -0800

Marc,

I am afraid you need to figure out the last metadata backup in /etc/lvmconf/
which *doesn't* contain the flaky snapshot(s).

You didn't mention the name of you VG so let's say it was 'A'.

You can do that with "vgcfgrestore -f /etc/lvmconf/A.conf.1.old -n A -ll".
Replace the '1' in the metadata backup filename above with 2, 3 and so on
(you should have a default of up to 9).
After you found one (say #3), remember all you PVs belonging to that VG and run

pvcreate -yff /dev/AllYourPVsBelongingToA
for pv in /dev/AllYourPVsBelongingToA
do
   vgcfgrestore -f /etc/lvmconf/A.conf.3.old -n A $pv
done
vgscan
vgchange -ay A

That should be it (crossing fingers ;-)


On Fri, Jan 25, 2002 at 03:35:33PM -0800, Marc MERLIN wrote:
> It fails and says:
> parameter error setting up snapshot copy on write exception
> 
> So yes, I have  snapshots in there, but I can't delete  the snapshots if the
> volume isn't active, and I can't activate the volume because of a snapshot.
> 
> To make things worse, /dev/System contains /usr and /var.
> 
> The snapshots were created with 1.0.1rc4 on 2.4.14 and I now run 2.4.17 with
> 1.0.1rc4-ish
> 
> What's the magic override I need to use to make the volume active again?
> 
> Thanks
> Marc
> -- 
> Microsoft is to operating systems & security ....
>                                       .... what McDonalds is to gourmet cooking
>   
> Home page: http://marc.merlins.org/   |   Finger marc_f@merlins.org for PGP key
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-01-28  3:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25 17:36 [linux-lvm] vgchange -a y /dev/System fails Marc MERLIN
2002-01-28  3:47 ` Heinz J . Mauelshagen [this message]
2002-01-29 15:58   ` Marc MERLIN
2002-01-30  6:17     ` Heinz J . Mauelshagen
2002-01-30 21:04       ` Marc MERLIN
2002-01-31  5:19         ` Heinz J . Mauelshagen
2002-02-01 15:10           ` Marc MERLIN
2002-02-11 13:01             ` Marc MERLIN
2002-01-29 18:25 ` Adrian Head
2002-01-30  6:20   ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-29 16:02 Marc MERLIN

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=20020128104258.A24830@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.