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 11:41:02 2002 [thread overview]
Message-ID: <20020227184102.A21636@sistina.com> (raw)
In-Reply-To: <1014830883.13642.12.camel@dirac.cids.ca>; from dsavard@cids.ca on Wed, Feb 27, 2002 at 12:28:03PM -0500
On Wed, Feb 27, 2002 at 12:28:03PM -0500, Daniel Savard wrote:
> le mar 26-02-2002 à 17:56, Andreas Dilger a écrit :
> > On Feb 26, 2002 17:28 -0500, Daniel Savard wrote:
> > > 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?
> >
> > Well, mke2fs writes a LOT of data into the partition, being especially
> > careful to overwrite everything at the start of the disk. It might be
> > possible to recover this with "vgcfgrestore", but even then you have the
> > problem of overwriting the rest of the data on the disk. If the primary
> > ext2 superblock is overwritten on an LV inside this disk, you can use
> > "e2fsck -b 32768" or so to try and recover.
> >
> > Cheers, Andreas
> > --
> > Andreas Dilger
> > http://sourceforge.net/projects/ext2resize/
> > http://www-mddsp.enel.ucalgary.ca/People/adilger/
> >
>
> Since my LVM partition has been moved by the operations on the
> partitions with fdisk. I had to use the vgcfgrestore command as follow
> and getting the following error:
>
> [root@einstein sbin]# vgcfgrestore -n datavg -o /dev/sda9 /dev/sda7
> vgcfgrestore -- INFO: using backup file "/etc/lvmconf/datavg.conf"
> vgcfgrestore -- ERROR "pv_read(): PV identifier invalid" reading physical volume "/dev/sda7"
>
> Is there still something I can try or should I forget it?
"pvcreate -ff /dev/sda7" before you try vgcfgrestore again.
>
> --
>
> =======================================
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-02-27 11:41 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 [this message]
2002-02-27 3:17 ` Heinz J . Mauelshagen
-- 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=20020227184102.A21636@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).