linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: lvm 1.0.3, kernel 2.4.17 and the libs...
Date: Wed Feb 27 03:17:01 2002	[thread overview]
Message-ID: <20020227101648.A19249@sistina.com> (raw)
In-Reply-To: <1014762518.12325.76.camel@dirac.cids.ca>; from dsavard@cids.ca on Tue, Feb 26, 2002 at 05:28:38PM -0500

On Tue, Feb 26, 2002 at 05:28:38PM -0500, Daniel Savard wrote:
> I managed to get the vgcfgrestore execute using the executable in the
> lvm-build tree. I still don't know why the installed executable is
> missing a definition for the opt_ignore (this is a variable that seems
> to be used by pv_move() and introduced around mid February according to
> the source files).

Yes.
Did you do a clean build?
That should avoid the missing definition.

> 
> The operation cannot be completed. I will explain my big mistake and I
> would like to know if something can be try to recover from this or if I
> must check this as an unrecoverable error.
> 
> I was making some changes in order to move my partitions to LV in my VG.
> The idea was to recover as much space as possible from my drive, making
> all remaining partitions continguous and creating a new partition marked
> for LVM and add the new partition to the VG in order to migrate as much
> stuff as possible into the VG.
> 
> So, I was to the point I needed to create a partition contiguous to the
> other one, move stuff on it, delete the old one and recover contiguous
> space for the future LVM partition to be added to the VG. I add just
> remove an obsolete partition, say /dev/sda6, my existing LVM partition
> was /dev/sda8, so the partition numbers were decreased by one for all
> partitions above 6 as usual, I then created a new partition which became
> /dev/sda8 and the LVM partition was the /dev/sda7. Everything would be
> just fine if I didn't forget to reboot the machine before proceeding
> with the following:
> 
> I did mkfs.ext2 on /dev/sda8 !!! However, this was still pointing to my
> LVM partition even if fdisk was not showing this.
> 
> The big question: Is it still possible to recover some data from the LVM
> partition which was the only partition in my VG?
> 
> If yes, HOW.
> 
> -- 
> 
> =======================================
> Daniel Savard
> 
> Internet: dsavard@cids.ca
> =======================================
> 
> 
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  parent reply	other threads:[~2002-02-27  3:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 16:28 [linux-lvm] Re: lvm 1.0.3, kernel 2.4.17 and the libs Daniel Savard
2002-02-26 16:56 ` Andreas Dilger
2002-02-27 11:28   ` Daniel Savard
2002-02-27 11:41     ` Heinz J . Mauelshagen
2002-02-27  3:17 ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27 12:31 Daniel Savard

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=20020227101648.A19249@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;
as well as URLs for NNTP newsgroup(s).