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] Repairing LVM installations
Date: Mon Oct 28 09:52:01 2002	[thread overview]
Message-ID: <20021028164912.A18086@sistina.com> (raw)
In-Reply-To: <1035810145.11532.117.camel@defiant>; from storm@tux.org on Mon, Oct 28, 2002 at 08:02:24AM -0500

On Mon, Oct 28, 2002 at 08:02:24AM -0500, Bradley Alexander wrote:
> On Mon, 2002-10-28 at 04:08, Heinz J . Mauelshagen wrote:
> > 
> > Bradley,
> > 
> > looks like Norton defrag toasted your physical volume :(
> 
> Yep.
>  
> > There might be a slight chance to get it back, if you have an LVM
> > metadata backup at hand (/etc/lvmconf/vg00.conf) and use vgcfgrestore
> > to restore it to the physical volume.
> 
> I tried this and when I tried listing the file, I got the same
> consistency error message:
> 
> [defiant /etc/lvmconf]# vgcfgrestore -f /etc/lvmconf/vg00.conf.2.old -l
> -n vg00
> vgcfgrestore -- ERROR "vg_cfgrestore(): pv_check_consistency" restoring
> volume group "vg00"

"pvcreate -ff ..." on the PV first.

> 
> vg00.conf.2.old should be the one immediately prior to the "incident".
> 
> When I tried an actual restore, it groused about changing an active
> volume group, so I guess I'll go single-user and try it again.
> 
> > But I guess Norton damaged more than just the LVM metadata area which sits
> > at the beginning of the drive.
> > You should try restoring the metadata though.
> 
> Not knowing what Norton has cabbaged, I would be happy if I could just
> move the active extents from the damaged volume to another one long
> enough to remobe, rebuild and reactivate it.

Well, if the vgcfgrestore brings your VG back it is still questionable what
data is toasted. If any the move won't help either and you want to
go for your backup media :(


> 
> > Hopefully you've got an actual backup of your logical volumes!
> 
> I'm using the one prior to the drive getting nortoned. :)
> 
> -- 
> --Brad
> ============================================================================
> Bradley M. Alexander                |   storm [at] debian.org
> Debian Developer, Security Engineer |   storm [at] tux.org
> Debian/GNU Linux Developer          | Visit the 99th VFS website at:
> 99th VFS 'Tuskegee Airmen'          |   http://99thvfs-ta.org
> ============================================================================
> Key fingerprints:
> DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
> RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34
> ============================================================================
> If guns are outlawed, can we use swords?
> 
> 
> _______________________________________________
> 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:[~2002-10-28  9:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 23:56 [linux-lvm] Repairing LVM installations Bradley M Alexander
2002-10-28  3:11 ` Heinz J . Mauelshagen
2002-10-28  7:03   ` Bradley Alexander
2002-10-28  9:52     ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 11:32 Bradley M Alexander

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=20021028164912.A18086@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.