Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM ate my data!
Date: Tue Feb 26 04:45:02 2002	[thread overview]
Message-ID: <20020226114538.A13520@sistina.com> (raw)
In-Reply-To: <Pine.OSF.4.05.10202252007450.18015-100000@cpca7.uea.ac.uk>; from W.B.Hill@uea.ac.uk on Mon, Feb 25, 2002 at 08:18:10PM +0000

On Mon, Feb 25, 2002 at 08:18:10PM +0000, wbh wrote:
> Wahey - I got my data back, thankyou!
> 
> > pvcreate -yff /dev/hda[34]
> > vgcfgrestore -n YourVGName /dev/hda3
> > vgcfgrestore -n YourVGName /dev/hda4
> > vgscan
> > vgchange -ay
> 
> What I did, from .bash_history
> rm -rf /etc/lvmtab /etc/lvmtab.d /dev/pvg # I had backed up already.
> ~/LVM/1.0.3/tools/vgscan
> ~/LVM/1.0.3/pvcreate -yff /dev/hda[34]
> vgcfgrestore -n pvg /dev/hda3
> vgcfgrestore -n pvg /dev/hda4
> ~/uuid_fixer/uuid_fixer /dev/hda3 /dev/hda4
> ~/LVM/1.0.3/tools/vgscan
> ~/LVM/1.0.3/tools/vgchange -ay
> mount -treiserfs /dev/pvg/1 /mnt/dat
> 
> Don't know how much of that was needed...

All of that probably.
uuid_fixer covers a bug in older vgcfgrestore versions which prevented correct
restores of the PV UUID tables to all PVs.

> 
> I had been playing with snapshots recently, but they didn't seem to work
> with my ancient (2.4.3) kernel. Could that have been the cause?

In case you haven't patched in the newest LVM driver code following the 
instrcutions in PATCHES/README contained in the LVM distro -> yes.

> 
> Thanks!
>     Bill
> 
> 
> _______________________________________________
> 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-02-26  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 12:09 [linux-lvm] LVM ate my data! lvm-mail
2002-02-25 12:28 ` Heinz J . Mauelshagen
2002-02-25 13:14   ` wbh
2002-02-26  4:47     ` Heinz J . Mauelshagen
2002-02-25 14:18   ` wbh
2002-02-26  4:45     ` Heinz J . 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=20020226114538.A13520@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox