Operating System - HP-UX
1753926 Members
9255 Online
108810 Solutions
New Discussion

Re: LV PVG Strict -Distributed Volume resize messup

 
jerrym
Trusted Contributor

LV PVG Strict -Distributed Volume resize messup

I believe I broke my volume resizing it.

 

1. This is a cluster.

2. The LV was set to:   Allocation     PVG-strict/distributed

3. HP-UX 11.31

 

vgdisplay is:

 

--- Volume groups ---
VG Name                     /dev/vgoracle
VG Write Access             read/write
VG Status                   available, exclusive
Max LV                      255
Cur LV                      2
Open LV                     2
Max PV                      16
Cur PV                      3
Act PV                      3
Max PE per PV               4315
VGDA                        6
PE Size (Mbytes)            16
Total PE                    12945
Alloc PE                    9344
Free PE                     3601
Total PVG                   0
Total Spare PVs             0
Total Spare PVs in use      0
VG Version                  1.0
VG Max Size                 1104640m
VG Max Extents              69040

   --- Logical volumes ---
   LV Name                     /dev/vgoracle/lvdbload
   LV Status                   available/syncd
   LV Size (Mbytes)            102400
   Current LE                  6400
   Allocated PE                6400
   Used PV                     3

   LV Name                     /dev/vgoracle/lvoracle
   LV Status                   available/syncd
   LV Size (Mbytes)            47104
   Current LE                  2944
   Allocated PE                2944
   Used PV                     3


   --- Physical volumes ---
   PV Name                     /dev/disk/disk58
   PV Status                   available
   Total PE                    4315
   Free PE                     773
   Autoswitch                  On
   Proactive Polling           On

   PV Name                     /dev/disk/disk59
   PV Status                   available
   Total PE                    4315
   Free PE                     1414
   Autoswitch                  On
   Proactive Polling           On

   PV Name                     /dev/disk/disk60
   PV Status                   available
   Total PE                    4315
   Free PE                     1414
   Autoswitch                  On
   Proactive Polling           On

 

 

lvdisplay was:

 

--- Logical volumes ---
LV Name                     /dev/vgoracle/lvoracle
VG Name                     /dev/vgoracle
LV Permission               read/write
LV Status                   available/syncd
Mirror copies               0
Consistency Recovery        MWC
Schedule                    parallel
LV Size (Mbytes)            35840
Current LE                  2240
Allocated PE                2240
Stripes                     0
Stripe Size (Kbytes)        0
Bad block                   on
Allocation                  PVG-strict/distributed
IO Timeout (Seconds)        default

  

   --- Distribution of logical volume ---
   PV Name                 LE on PV  PE on PV
   /dev/disk/disk58        768       768
   /dev/disk/disk59        768       768
   /dev/disk/disk60        768       768

.

Don't have reset of output before change. And disks# 768 768 should be similar like other 36GB lv

evenly distributed.

 

 

I could not do:

 

lvextend -l 2944 /dev/vgoracle/lvoracle

 

Got message about not enough extends.

 

 

Took out:  PVG-strict/distributed

 

lvchange -s n /dev/vgoracle/lvoracle

lvchange -D n /dev/vgoracle/lvoracle

 

Did:

 

lvextend -l 2944 /dev/vgoracle/lvoracle

 

Did:

 

lvchange -s g /dev/vgoracle/lvoracle

 

But could not do:

 

lvchange -D y /dev/vgoracle/lvoracle

 

lvchange: Can not set the Distributed allocation policy because
LV "/dev/vgoracle/lvoracle" currently has at least two consecutive physical
extents on the same physical volume.

 

 

Now LV is:

 

--- Logical volumes ---
LV Name                     /dev/vgoracle/lvoracle
VG Name                     /dev/vgoracle
LV Permission               read/write
LV Status                   available/syncd
Mirror copies               0
Consistency Recovery        MWC
Schedule                    parallel
LV Size (Mbytes)            47104
Current LE                  2944
Allocated PE                2944
Stripes                     0
Stripe Size (Kbytes)        0
Bad block                   on
Allocation                  PVG-strict
IO Timeout (Seconds)        default

   --- Distribution of logical volume ---
   PV Name                 LE on PV  PE on PV
   /dev/disk/disk58        1408      1408
   /dev/disk/disk59        768       768
   /dev/disk/disk60        768       768

   --- Logical extents ---
   LE    PV1                     PE1   Status 1
   00000 /dev/disk/disk58        02134 current
   00001 /dev/disk/disk59        02133 current
   00002 /dev/disk/disk60        02133 current
   00003 /dev/disk/disk58        02135 current
   00004 /dev/disk/disk59        02134 current
   00005 /dev/disk/disk60        02134 current
   00006 /dev/disk/disk58        02136 current
   00007 /dev/disk/disk59        02135 current

.

.

.

 

Don't know how to fix this. It allocated the extra space on disk58 only.

Could not put it back the way it was. I messed up.

 

5 REPLIES 5
Torsten.
Acclaimed Contributor

Re: LV PVG Strict -Distributed Volume resize messup

PVG strict make sense only while mirroring.

 

Distributed means the first extend on the first disk, second extend on second disk, ... but now you have the new extends on a single disk only, so you cannot go back to distributed, unless you re-create the lvol and restore the data.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
jerrym
Trusted Contributor

Re: LV PVG Strict -Distributed Volume resize messup

So what would have been the process to increase this lvol and still have it distributed?

Torsten.
Acclaimed Contributor

Re: LV PVG Strict -Distributed Volume resize messup

You need to extend all 3 "disks" (PVs) in order to extend the LVOL.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: LV PVG Strict -Distributed Volume resize messup

The question is, does it really matter?

For real disks for sure, but for an array (let's say an EVA) it probably does not.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
jerrym
Trusted Contributor

Re: LV PVG Strict -Distributed Volume resize messup

Well, I am missing something here. I was able to extend the lvol. But I will have to lookup how to extend all the

pv's. Unless I can't since I took out Distributed before the change and now it is set to those extents on the one

disk. I tried to resize down but could not. I assume if I had not taken the Distributed parm out, then it would have distributed across all the disks.

 It is EMC storage.