From: Morten Torstensen <morten@mortent.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove obliterates filesystem (Opensuse 10.2, x86-64)
Date: Thu, 18 Oct 2007 00:11:38 +0200 [thread overview]
Message-ID: <4716889A.6020206@mortent.org> (raw)
In-Reply-To: <20071017012858.GW10006@agk.fab.redhat.com>
> [snip pvmove problems]
This is why, imo, why lvm on linux needs to virtualize PE in lVm... a LV
only maps to LE (logical extents) that can themselves be mapped to one
or more PEs. Then you can pvmove by adding maps and removing old maps
after verifying that the new mapping is ok.
This is basically how LVM is implemented in AIX. Is this a too big NIH
problem for LVM on Linux? I am amazed that LVM on Linux doesn't steal
more ideas from LVM on AIX, as that is without doubt the best LVM
implementation you have out there. Big words, yes... if anyone can argue
why I am wrong I am happy to hear why :) (and gladly accept defeat if
that is required)
//Morten
next prev parent reply other threads:[~2007-10-17 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 23:27 [linux-lvm] pvmove obliterates filesystem (Opensuse 10.2, x86-64) Brian Strand
2007-10-17 1:28 ` Alasdair G Kergon
2007-10-17 22:11 ` Morten Torstensen [this message]
2007-10-20 17:12 ` Stuart D. Gathman
2007-10-17 23:52 ` [linux-lvm] " Brian Strand
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=4716889A.6020206@mortent.org \
--to=morten@mortent.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.