Linux LVM users
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] recovering data from inside a partitioned lv
Date: Mon, 22 Jun 2009 18:42:09 +0100	[thread overview]
Message-ID: <1245692529.18101.470.camel@breeves.fab.redhat.com> (raw)
In-Reply-To: <104D56B6-A5AA-44BC-A1A6-EDCF2FC098A8@merit.edu>

On Mon, 2009-06-22 at 13:23 -0400, Anthony Clark wrote:
> Hi,
> 
> The following stupid mistake was made :(  A pv, vg and lv were  
> created, and then the documentation was misread, and a partition was  
> created inside the lv.  Said partition mounted fine, and allowed fs  
> creation along with large amounts of data to be copied.  Partition was  
> accessible via /dev/vg1/lv1p1.
> 
> Server has been rebooted, and now only /dev/vg1/lv1 is shown.  parted  
> can open the lv and shows 1 partition inside, but doesn't understand  
> ext3 volumes, so can't copy the partition to another disk.  tune2fs  
> can't see /dev/vg1/lv1p1, or I'd use that to change the fs type to ext2.
> 
> Is there a way to undo the stupid mistake and get at the partition  
> inside the logical volume?  That is to say, mount the partition, copy  
> the data out and then create the filesystem correctly.  Is there a way  
> to force /dev/vg1/lv1p1 to show up again?

kpartx -a /dev/vg1/lv1

Will create maps for all the partitions defined inside the LV. See man
kpartx for the remaining options.

Cheers,
Bryn.

      parent reply	other threads:[~2009-06-22 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 17:23 [linux-lvm] recovering data from inside a partitioned lv Anthony Clark
2009-06-22 17:32 ` Christian Völker
2009-06-22 17:57   ` Anthony Clark
2009-06-22 17:42 ` Bryn M. Reeves [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=1245692529.18101.470.camel@breeves.fab.redhat.com \
    --to=bmr@redhat.com \
    --cc=linux-lvm@redhat.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