1752359 Members
6300 Online
108787 Solutions
New Discussion юеВ

Re: lvextend

 
SOLVED
Go to solution
Torsten.
Acclaimed Contributor

Re: lvextend

This LVOL is still mirrored, even if the disk is missing.

The system wants to extend the LVOL on one disk and the mirror too.

No disk = no extends available.

Consider to use "vgreduce -f vg00" to fix.

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!   
masood bt
Regular Advisor

Re: lvextend

I think the two disks for this vg00 are c0t0d0s2 and c2t0d0s2...I conclude this from the vgdisplay -v /dev/vg00 output.

Also..I can see the c0t0d0s2 is present and c2t0d0s2 is missing.
how exactly should I remove the disk c2t0d0s2 from /dev/vg00

Before removing the disk from vg00 do I need to remove it from lv ?
It would be great if you explain me in steps. Thank you.


rc85odb2:/ # vgdisplay -v /dev/vg00 | more
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open LV 11
Max PV 8
Cur PV 2
Act PV 1
Max PE per PV 9200
VGDA 2
PE Size (Mbytes) 32
Total PE 4346
Alloc PE 2294
Free PE 2052
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 768
Current LE 24
Allocated PE 48
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/stale
LV Size (Mbytes) 16352
Current LE 511
Allocated PE 1022
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/stale
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/stale
LV Size (Mbytes) 512
Current LE 16
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/stale
LV Size (Mbytes) 6144
Current LE 192
Allocated PE 384
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/stale
LV Size (Mbytes) 4096
Current LE 128
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/stale
LV Size (Mbytes) 4096
Current LE 128
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/stale
LV Size (Mbytes) 6144
Current LE 192
Allocated PE 384
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/stale
LV Size (Mbytes) 16352
Current LE 511
Allocated PE 1022
Used PV 1

LV Name /dev/vg00/osmf
LV Status available/stale
LV Size (Mbytes) 1536
Current LE 48
Allocated PE 96
Used PV 1

LV Name /dev/vg00/lv-oracle-u01
LV Status available/stale
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 1024
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c0t0d0s2
PV Status available
Total PE 4346
Free PE 2052
Autoswitch On
Proactive Polling On


rc85odb2:/ #

Behind every Great fortune, there is a crime
masood bt
Regular Advisor

Re: lvextend

I did vgreduce -l

rc85odb2:/ # vgreduce -l /dev/vg00 /dev/dsk/c2t0d0s2
Volume group "/dev/vg00" has been successfully reduced.
rc85odb2:/ #

unmounted the fs but couldnt extend it.
rc85odb2:/ # lvextend -L 32768 /dev/vg00/lv-oracle-u01
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lv-oracle-u01" could not be extended.
Failure possibly caused by strict allocation policy
rc85odb2:/ #
Behind every Great fortune, there is a crime
Torsten.
Acclaimed Contributor
Solution

Re: lvextend

How about the vgdisplay and lvdisplay output now?

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!   
masood bt
Regular Advisor

Re: lvextend


Torsten,

rc85odb2:/ # strings /etc/lvmtab
/dev/vg00
fjI!O
/dev/dsk/c0t0d0s2
rc85odb2:/ #

The disk c2t0d0s2 has been removed from lvmtab after vgreduce -l



rc85odb2:/ # vgdisplay -v /dev/vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open LV 11
Max PV 8
Cur PV 2
Act PV 1
Max PE per PV 9200
VGDA 2
PE Size (Mbytes) 32
Total PE 4346
Alloc PE 2294
Free PE 2052
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 768
Current LE 24
Allocated PE 48
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/stale
LV Size (Mbytes) 16352
Current LE 511
Allocated PE 1022
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/stale
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/stale
LV Size (Mbytes) 512
Current LE 16
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/stale
LV Size (Mbytes) 6144
Current LE 192
Allocated PE 384
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/stale
LV Size (Mbytes) 4096
Current LE 128
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/stale
LV Size (Mbytes) 4096
Current LE 128
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/stale
LV Size (Mbytes) 6144
Current LE 192
Allocated PE 384
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/stale
LV Size (Mbytes) 16352
Current LE 511
Allocated PE 1022
Used PV 1

LV Name /dev/vg00/osmf
LV Status available/stale
LV Size (Mbytes) 1536
Current LE 48
Allocated PE 96
Used PV 1

LV Name /dev/vg00/lv-oracle-u01
LV Status available/stale
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 1024
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c0t0d0s2
PV Status available
Total PE 4346
Free PE 2052
Autoswitch On
Proactive Polling On


rc85odb2:/ # lvdisplay -v /dev/vg00/lv-oracle-u01
--- Logical volumes ---
LV Name /dev/vg00/lv-oracle-u01
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 1024
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c0t0d0s2 512 512

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 /dev/dsk/c0t0d0s2 01782 current ??? 01782 stale
00001 /dev/dsk/c0t0d0s2 01783 current ??? 01783 stale
00002 /dev/dsk/c0t0d0s2 01784 current ??? 01784 stale
00003 /dev/dsk/c0t0d0s2 01785 current ??? 01785 stale
00004 /dev/dsk/c0t0d0s2 01786 current ??? 01786 stale
-------------
-------------
-------------
Behind every Great fortune, there is a crime
Torsten.
Acclaimed Contributor

Re: lvextend

The lvol is still mirrored. Consider to use vgreduce -f or use the steps from here:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

in order to unmirror your lvols from a non-existing disk.

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!   
masood bt
Regular Advisor

Re: lvextend

Ahh.. this famous pdf
"When Good Disks Go Bad: Dealing with Disk Failures Under LVM"

Let me go thorugh this once again..Torsten..thx
Behind every Great fortune, there is a crime
masood bt
Regular Advisor

Re: lvextend

Dear Torsten

The solution is in the 19th page of the document When good disks go bad.

I am very happy. Leaving for the day now. I assigned you points to your earlier posts...
thank you very much.
Behind every Great fortune, there is a crime
masood bt
Regular Advisor

Re: lvextend

The PV has been removed from the VG
So lvreduce cant be done using the PV name.

lvdisplay -v -k /dev/vgxx/lvolxx gives the PV key(PV which has stale extents)

lvreduce -m 0 -A n -k /dev/vgxx/lvolxx

This successfully reduced the lvol.

The solution is in the 19th page
http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

Thanks to Torsten!
Behind every Great fortune, there is a crime