From: Morten Torstensen <morten@mortent.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVs corrupted after pvresize
Date: Tue, 21 Oct 2008 13:13:11 +0200 [thread overview]
Message-ID: <48FDB947.3090509@mortent.org> (raw)
In-Reply-To: <1224528632.6013.66.camel@localhost.localdomain>
Peter Larsen wrote:
> Can you give an example or two on how the LVM differs on the
> user-friendliness areas?
Say you want to mirror a LV, then you just do a "mklvcopy mylvname 2" to
have 2 copies of data (one extra, like raid-1). If you want to migrate
your disks to a new system, add the new PV to your VG and do a "mklvcopy
mylvname 3 newpv", then when it finish remove your old mirrors and
delete the old PVs.
The AIX concept of physical extent/logical extent mapping is sorely
missed on linux.
Generally speaking, LVM on AIX is also more mature. Exporting and
importing VGs (to move VGs between systems) works better in my
experience, clustering is more stable, but that is also something where
YMMV can show.
Managing mirrors, data placement and hotspot detection are what I mainly
miss on Linux.
--
//Morten Torstensen
//Email: morten@mortent.org
//IM: Cartoon@jabber.no morten.torstensen@gmail.com
And if it turns out that there is a God, I don't believe that he is evil.
The worst that can be said is that he's an underachiever.
next prev parent reply other threads:[~2008-10-21 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 21:09 [linux-lvm] LVs corrupted after pvresize Christian Völker
2008-10-16 22:31 ` Stuart D. Gathman
2008-10-17 4:05 ` Christian Völker
2008-10-17 5:23 ` Peter Larsen
2008-10-20 15:41 ` Stuart D. Gathman
2008-10-20 18:50 ` Peter Larsen
2008-10-21 11:13 ` Morten Torstensen [this message]
2008-10-21 14:07 ` Larry Dickson
2008-10-21 14:44 ` Stuart D. Gathman
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=48FDB947.3090509@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.