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
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