linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: [linux-lvm] VG defragmenting and backing up the extent map
Date: Wed, 03 May 2006 21:39:36 -0400	[thread overview]
Message-ID: <1146706776.31003.136.camel@pc.local> (raw)

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

It has often occurred to me that the fact that a logical volume is not
contiguous will make recovery in the face of a partial disaster more
difficult.

For example, if I happen to lose the logical->physical extent map in the
LVM superblock (the single only place this information is kept AFAIK)
then I am pretty screwed with respect to getting my filesystems back off
the disk.

Compared with just losing the partition table from a traditionally
partitioned disk, I could use a tool like findsuper and losetup the
whole disk with offsets (losetup -o <offset> to retrieve the individual
filesystems.

This technique would even work with LVM given that I had lost the part
of the disk with the extent mapping except that my filesystems are not
contiguous if I have extended any of them.

So, the question is, has anyone developed a tool to "defragment" a
Volume Group so that all of the logical volumes in it are contiguous?

On a somewhat related note, what provisions can I take to mitigate the
loss of the extent map?  I am correct in that only one copy of it exists
at the head of a Physical Volume?  Can I make a backup of it in any way
so that it could be used at a later date to reconstruct logical volumes?

As you might have guessed, I have lost a small portion of a 160GB disk,
the portion which has the extent mapping for the whole PV and I want to
mitigate this problem in the future.

b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

                 reply	other threads:[~2006-05-04  1:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1146706776.31003.136.camel@pc.local \
    --to=brian@interlinx.bc.ca \
    --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).