Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to remove a logical volume 1

Status
Not open for further replies.

KPKIND

Technical User
Sep 8, 2003
130
IN
Hi *,

We have had a disk replaced in the rootvg. Before I have replaced the disk, I have done the below given tasks.

1.Unmirroredvg, to take out failing disk

2.Tried to reducevg, but failed as it had a sysdump lv, so changed the dump device and removed this lv, got a confirmation saying lv removed

3.Changed the boot list to take out the failing disk

4.Then got the disk replaced,since it was a internal disk had to bring down the server.

5.Got the new disk in,added the disk to the rootvg,mirrored the vg, created boot image on both the disks, changed the bootlist to reflect the new disk

6.Now tried to add lv of the type sysdump (for replacing the one I have deleted before) with the same name of the previous one, now it comes out and says there is already an lv with that name.

7. When I do a lslv on that lv the below is the output

LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 0044dc9a00004c00000000f00b056095.10 PERMISSION: ?
VG STATE: active/complete LV STATE: ?
TYPE: sysdump WRITE VERIFY: ?
MAX LPs: ? PP SIZE: ?
COPIES: ? SCHED POLICY: ?
LPs: ? PPs: ?
STALE PPs: ? BB POLICY: ?
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: ?
EACH LP COPY ON A SEPARATE PV ?: yes

So, tried to do a synclvodm - did not help

tried to get the details from the lvcb - getlvcb -AT lg_dumplv - Did not return any details

tried ldeletepv -l <LVID> (Which I have got from the above output) it gives an error saying as below

# ldeletelv -l 0044dc9a00004c00000000f00b056095.10
0516-022 ldeletelv: Illegal parameter or structure value.
#

I understand that this is a ODM corruption. If it was a non-root VG i would have exported it and umported it back, but unfortunate that it is in rootvg

Finally for now, I have created another dump dev and gone ahead but wanted to know what is the problem and how do I get rid of this unrealistic lv from the rootvg

TIA
KPKIND
 
Hi,

Pl find the outputs you have requested.


vbwsc03> lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 32 64 2 open/syncd N/A
hd8 jfs2log 1 2 2 open/syncd N/A
hd4 jfs2 1 2 2 open/syncd /
hd2 jfs2 17 34 2 open/syncd /usr
hd9var jfs2 2 4 2 open/syncd /var
hd3 jfs2 2 4 2 open/syncd /tmp
hd1 jfs2 1 2 2 open/syncd /home
hd10opt jfs2 1 2 2 open/syncd /opt
paging00 paging 32 64 2 open/syncd N/A
hd20 jfs2 2 4 2 open/syncd /usr/local
hd21 jfs2 10 20 2 open/syncd /Titan
lg_dumplv1 sysdump 16 16 1 open/syncd N/A
loglv00 jfslog 1 2 2 closed/syncd N/A
vbwsc03> lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0044dc9a00004c00000000f00b056095
VG STATE: active PP SIZE: 64 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1084 (69376 megabytes)
MAX LVs: 256 FREE PPs: 862 (55168 megabytes)
LVs: 14 USED PPs: 222 (14208 megabytes)
OPEN LVs: 12 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no
vbwsc03> lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 0044dc9a00004c00000000f00b056095.10 PERMISSION: ?
VG STATE: active/complete LV STATE: ?
TYPE: sysdump WRITE VERIFY: ?
MAX LPs: ? PP SIZE: ?
COPIES: ? SCHED POLICY: ?
LPs: ? PPs: ?
STALE PPs: ? BB POLICY: ?
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: ?
EACH LP COPY ON A SEPARATE PV ?: yes
vbwsc03>


TIA
KPKIND
 
maybe you should first try to remove "dead" entries from ODM? as the LV was removed its entries/stanzas should not be there in ODM. If there are then try remove them manually.

# odmget -q name=lg_dumplv CuDv

CuDv:
name = "lg_dumplv"
status = 1
chgstatus = 1
ddins = ""
location = ""
parent = "rootvg"
connwhere = ""
PdDvLn = "logical_volume/lvsubclass/lvtype"

# odmget -q name=lg_dumplv CuAt

CuAt:
name = "lg_dumplv"
attribute = "lvserial_id"
value = "00cc2baf00004c000000010707eadd4d.10"
type = "R"
generic = "D"
rep = "n"
nls_index = 648

CuAt:
name = "lg_dumplv"
attribute = "stripe_width"
value = "0"
type = "R"
generic = "DU"
rep = "r"
nls_index = 1100

CuAt:
name = "lg_dumplv"
attribute = "type"
value = "sysdump"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639

CuAt:
name = "lg_dumplv"
attribute = "size"
value = "20"
type = "R"
generic = "DU"
rep = "r"
nls_index = 647
 
Perhaps the /dev/lg_dumplv and/or /dev/rlg_dumplv names need to be removed?

HTH,

p5wizard
 
Thank you all for the info.

I dont have any entries in the /dev for the old lv. But definitely entries for this lv in the Customized object classess.. I'll try removing them and keep you posted.

Cheers
KPKIND
 
Thanks a lot ogniemi. You have solved my problem.

Cheers
KPKIND
 
IBM support gave me this when one of our DBA's deleted hd6. The equivalent to doing an exportvg/importvg for rootvg

Code:
PV=hdisk0                                                        
VG=rootvg                                                        
        cp /etc/objrepos/CuAt /etc/objrepos/CuAt.$$              
        cp /etc/objrepos/CuDep /etc/objrepos/CuDep.$$            
        cp /etc/objrepos/CuDv /etc/objrepos/CuDv.$$              
        cp /etc/objrepos/CuDvDr /etc/objrepos/CuDvDr.$$          
        lqueryvg -Lp $PV | awk '{print $2}' | while read LVname; 
        do                                                       
                odmdelete -q "name=$LVname" -o CuAt              
                odmdelete -q "name=$LVname" -o CuDv              
                odmdelete -q "value3=$LVname" -o CuDvDr          
        done                                                     
        odmdelete -q "name=$VG" -o CuAt                          
        odmdelete -q "parent=$VG" -o CuDv                        
        odmdelete -q "name=$VG" -o CuDv                          
        odmdelete -q "name=$VG" -o CuDep                         
        odmdelete -q "dependency=$VG" -o CuDep                   
        odmdelete -q "value1=10" -o CuDvDr                       
        odmdelete -q "value3=$VG" -o CuDvDr                      
        importvg -y $VG $PV  #ignore lvaryoffvg errors           
        varyonvg $VG
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top