topic LVM Mirroring to different size LUNS in Operating System - HP-UX

LVM Mirroring to different size LUNS

John Goetz — Fri, 29 Apr 2005 13:05:40 GMT

Can I do LVM mirroring to devices that are different in sizes? If this can be done, how would you do it and what are the risks?

We are going from an EMC Sym to EMC DMX storage system and all of the LUN / Device sizes are different.

Re: LVM Mirroring to different size LUNS

Jeff Schussele — Fri, 29 Apr 2005 13:09:17 GMT

Hi John,

Yes you can do it..BUT....the mirror size will be limited to the capacity of the smaller LUN.
This will effectively waste a lot of space on the new LUNs.
Your EMC people should have planned this better & presented the same size LUNs on the new DMX.

To get full capacity you'll need to transfer the data some other way besides mirroring - via tape or rcp or ftp or such.

Rgds,
Jeff

Re: LVM Mirroring to different size LUNS

Florian Heigl (new acc) — Fri, 29 Apr 2005 13:40:31 GMT

this should not be any trouble, but You should use PVGs and PVG-strict allocation to avoid mirrors ending up on the same disk.

if Your host is dual-pathed to both arrays, You might want to take the 'risk' of simply using pvmove, but in the end, anything works.

Re: LVM Mirroring to different size LUNS

Devender Khatana — Sat, 30 Apr 2005 01:48:07 GMT

Hi,

It is not advised to mirror it this way if difference of Size between two LUNs is too large. Just see the following VG parameters before going ahead as these parameters might now allow you to use the full size of new LUNs in existing VG's.

MAX PE Per PV
PE Size

Max PE per PV * PE Size = Max Physical Volume (Here LUN) Size utilized by VG.

This way you can find out the maximum space of one LUN that can be utilized in your existing VG.

Altough you can add LUNs of more than this size but it will be utilizd upto this limit only.

HTH,
Devender

Re: LVM Mirroring to different size LUNS

Bill Hassell — Sat, 30 Apr 2005 12:33:48 GMT

Mirroring is done at the lvol level and when you mirror a disk, you can specify exactly what physical disk (or LUN) to use. Where you put the extents and in what order is completely controllable by the lvextend command. lvextend doesn't care whether the destination disk/LUN is much larger--the extents are just added at the first available locations. If you specify two or three or more destinations disks, the extents are allocated in order up to the end of each disk.

Mirroring doesn't actually care about the various disks or their physical size. In fact, you can use pvmove to move mirrored extents to other disks or even to the same primary disk (a very dumb idea).

The concept of volume groups is to eliminate the concept of physical disks/LUNs y simply creating a pool of disk space. You then allocate the space as needed. You can mirror a 36Gb disk to a bunch of 2Gb disks with no problem. The LVM code looks up every extent as needed so there's no real shortcuts by having the mirror extents on different disks or even in random order.

Oh, but there's the issue of performance. Ideally, the disks would be similar in performance. When the disks aren't really disks but carved out space in an array, this issue is meaningless because all the disk space performs at about the same level (assuming reasonable management of the array parameters).