From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Partition Recovery in LVM
Date: Mon, 16 Aug 2010 15:25:00 +0100 [thread overview]
Message-ID: <4C694A3C.3090007@redhat.com> (raw)
In-Reply-To: <AANLkTikk+_fTX1EhLMyM2hcy0pc0D10DDjSOb_PHS16v@mail.gmail.com>
On 08/16/2010 02:02 PM, Romeo Theriault wrote:
> On Mon, Aug 16, 2010 at 13:45, Andrew Ragone <ajr9166@rit.edu> wrote:
>>
>> I�ve been searching like crazy to find an answer to this question to no avail: when you restore a backup of LVM does the backup contain partition table information as well?
>
> What kind of backup are you taking? Agent Client based or SAN snapshot based?
>
>>
>> I recently recovered an LVM that had a partition inside of it, but it has since been unable to mount. Most recovery utilities such as TestDisk will only find the LVM so I�m unsure of how to proceed and �recover� the partition.
>>
>>
>
> I don't know the exact lvm commands off the top of my head, but first
> I think you need to import the VG with something like 'vgimportclone'
Only if you're backing up the VG by cloning the storage (SAN clone/snap,
dd image, MD split mirror etc.).
> and then once the volume group is imported you should be able to see
> the partitions that reside in the VG. Not sure but you may need to run
> a 'kpartx -a' to get the kernel to see the new partitions that are
> available in the VG. Then I think it should be a matter of mounting
> the partition in /dev/mapper/<VG>
This is only needed if the LVs contain partition tables themselves (e.g.
VM storage). Any partitions containing PVs on the cloned storage should
be detected automatically by the kernel.
Regards,
Bryn.
prev parent reply other threads:[~2010-08-16 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 4:45 [linux-lvm] Partition Recovery in LVM Andrew Ragone
2010-08-16 13:00 ` Bryn M. Reeves
2010-08-16 13:02 ` Romeo Theriault
2010-08-16 14:25 ` 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=4C694A3C.3090007@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;
as well as URLs for NNTP newsgroup(s).