Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pecopy or lecopy
Date: Fri May 24 11:26:15 2002	[thread overview]
Message-ID: <20020524164815.A16749@sistina.com> (raw)
In-Reply-To: <20020417013928.I27907@progsoc.uts.edu.au>; from wildfire@progsoc.uts.edu.au on Wed, Apr 17, 2002 at 01:39:28AM +1000

[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]


Hi Anand.

On Wed, Apr 17, 2002 at 01:39:28AM +1000, Anand Kumria wrote:
> Hi there,
> 
> Quite some time ago, Heinz assisted me with a partial recovery of
> data from one of my LVM volumes. In the meantime I've managed to
> reconstruct a lot of it but have discovered there are one or two
> items I need to get back from the original.
> 
> I'm using LVM tool 1.1rc1 reports:
> caliban:~# vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "caliban"
> vgscan -- only found 11364 of 11520 LEs for LV /dev/caliban/h2
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume group
> 
> If I try and mount the h2 filesystem my kernel opps as the first 150
> PE<->LE mappings don't exist. Has anyone written a tool that copies
> either PEs or LEs from disk without mounting the affected partition?

Not that I am aware if.

A tool to extract accessable LEs of a LV basically needs to:

- run "lvdisplay -Dv /dev/caliban/h2" in order to retrieve all
  physical volumes and extents of the LV

- pvdisplay -v on all of the PVs to get the mapping and run
  dd commands for every extend which name the output files per le

Attached script, which *needs* 1.1-rc tools to run, tries this:

Tell me, if it is of any use for you.

Regards,
Heinz    -- The LVM Guy --

> 
> That would allow me to salvage more of the data. I'm at the point where
> writing the code myself is an option if only I got some pointers. I'm
> unclear on where the mapping from LE<->PE<->disk blocks is stored. Plus
> I'm finding it confusing trying to see which version of the on-disk metadata
> LVM is using.
> 
> Thanks,
> Anand
> 
> -- 
>  `` We are shaped by our thoughts, we become what we think.
>  When the mind is pure, joy follows like a shadow that never
>  leaves. '' -- Buddha, The Dhammapada
> 
> _______________________________________________
> 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

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[-- Attachment #2: save_les.sh --]
[-- Type: application/x-sh, Size: 968 bytes --]

  reply	other threads:[~2002-05-24 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 10:44 [linux-lvm] pecopy or lecopy Anand Kumria
2002-05-24 11:26 ` Heinz J . Mauelshagen [this message]
2002-05-24 13:35   ` Alasdair G Kergon

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=20020524164815.A16749@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