LVM and VxVM
Showing results for 
Search instead for 
Do you mean 

11iv2 (or 11iv3) nonroot lvol - lvol is spread across several disks

SOLVED
Go to Solution
Super Advisor

11iv2 (or 11iv3) nonroot lvol - lvol is spread across several disks

WE are migration to new storage. 

My question concerns all NONROOT VGs/LVs and using lvextend.

 

if i have an LV that currently is spread accros 2 PVs.   We created 2 new PVS. equal size  and the host is also mapped to these now.

 

Using mirroring how do you mirror the lvol over to the 2 new PVs..(new pvs are cytydy and cztzdz)

 

Just specifying lvextend -m 1 /dev/vgxx/lvxx /dev/dsk/cytydy   will be not work as this lvol will fill up this PV and the lvol needs more space (thus use the second new PV and run lvextend again????).

What other options are on the lvextend that I may not be aware of?

 

 

 

2 REPLIES
Honored Contributor [Founder]

Re: 11iv2 (or 11iv3) nonroot lvol - lvol is spread across several disks

You are going to want to create a PV Group.   See the vgextend man page, but the -g pvg_name option is what you will be looking for.  

 

You will then use the PVG name when running the lvextend command.

 

Also see the lvmpvg man page.

 

 

-Bob

----------------
Was this helpful? Like this post by giving me a thumbs up below!
Highlighted
Honored Contributor [Founder]

Re: 11iv2 (or 11iv3) nonroot lvol - lvol is spread across several disks

For a bunch of PVs, PVGs are the way to go. But for just 2 or 3, the lvextend command allows multiple PVs on the same line:

 

 lvextend -m 1 /dev/vgxx/lvxx /dev/dsk/cytydy /dev/dsk/cztzdz

 

You can also take advantage of the shell's filename matching and specify 5 or 10 PVs like this:

 

 lvextend -m 1 /dev/vgxx/lvxx /dev/dsk/cyty*

 

I do this when adding alternate links. The controller is usually the same and using [ ] patterns, you can specify ranges:

 

lvextend -m 1 /dev/vgxx/lvxx /dev/dsk/c6t[0-4]*

 

which sends these PVs to the lvextend command:

 

c6t0d0 c6t0d1 c6t1d0 c6t1d1 and so on...

 

Since this is a one time storage migration, your PVG will only be temporary so lvextend may be simpler.