[linux-lvm] LVs corrupted after pvresize

[Larry Dickson]

I thought lvdisplay --maps gave you the PV to LV mappings.

Larry Dickson
Cutting Edge Networked Storage

On 10/21/08, Morten Torstensen <morten at mortent.org> wrote:
>
> 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 at mortent.org
> //IM: Cartoon at jabber.no morten.torstensen at 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.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-lvm/attachments/20081021/0ad71fb1/attachment.htm>