linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Callahan <callahant@tessco.com>
To: urgrue <urgrue@bulbous.org>
Cc: linux-admin@vger.kernel.org
Subject: Re: lvm ate my hamster
Date: Tue, 20 Dec 2005 09:31:01 -0500	[thread overview]
Message-ID: <43A815A5.3040605@tessco.com> (raw)
In-Reply-To: <1135066013l.24521l.0l@hyttynen>

If you used pvcreate to recreate the pv, and/or vgcreate to recreate the
vg when you moved the disk, you probably have effectively lost the
data.... Not sure about any recovery utilities... sorry

The correct way, would have been to add the disk to the new machine, and
then issue pvchange -ax y, then vgscan, then vgchange -a y

Thanks,

Tom Callahan
TESSCO Technologies
(443)-506-6216
callahant@tessco.com

A real engineer only resorts to documentation when the keyboard dents on the forehead get too noticeable.



urgrue wrote:

> I had a single hard drive, containing a single PV, a single VG, and a 
> single LV (ext3) move from one computer to another. Im trying to 
> reconstruct the LVM on the new computer with no luck. Currently I
> have  the PV And VG, but no LV's are to be found. I'm assuming the
> metadata  has somehow been corrupted.
> Is there a way to re-create the LV without erasing the existing data
> on  the disk? A utility to scan the disk and rebuild the metadata? Or,
> is  there a way to "dismantle" the LVM and turn it into a normal
> ext2/3  filesystem?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2005-12-20 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20  8:06 lvm ate my hamster urgrue
2005-12-20 14:31 ` Tom Callahan [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=43A815A5.3040605@tessco.com \
    --to=callahant@tessco.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=urgrue@bulbous.org \
    /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).