increased /stand problems

[Jairo Campana]

hello
finish increasing /stand /dev/vg00/lvol1 and and I obtain the following result
nms1 # lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Swap: ??? on: /dev/dsk/c1t2d0
Dump: ??? on: /dev/dsk/c1t2d0, 0

that I made bad

before:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0

I have mirror in disk.

in vgdisplay not see /dev/vg00/lvol2


I did the following :
boot in LVM maintenance mode
#vgchange -a y /dev/vg00
#lvrmboot -r /dev/vg00
#lvremove /dev/vg00/lvol2
extend /stand
#lvextend -L 96 /dev/vg00/lvol1
#extendfs /dev/vg00/rlvol1
create /swap
#lvcreate -C y -r n -L 1011 -n lvol2 /dev/vg00
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2
#lvlnboot -R
#reboot -r


before the increased /stand my logical volume :

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 84
Current LE 21
Allocated PE 42
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 512
Used PV 2

I I needed to increase /stand in 96MB , 13MB more

Thanks

[Sridhar Bhaskarla]

Hi Jairo,

Does your /sbin/lvdisplay /dev/vg00/lvol2 show up?.

-Sri

[A. Clay Stephenson]

Normally /stand cannot be extended because it must be contiguous. There is a method (which I guess you tried) that shrinks lvol2 (primary swap) and extends lvol1. This method must be done exactly right or chaos occurs. THe "approved" method is IgniteUX; I hope you did a make_tape_recovery before you started. You will need it.

[Jeff Schussele]

I agree w/Clay.
The only sure way to increase either / , /stand or swap/dump is Ignite.
I sure hope you created a make_tape_recovery tape.

Rgds,
Jeff

[Sridhar Bhaskarla]

Hi,

Try your "lvrmboot" sequence again followed by lvlnboots before you go for your make_tape_recovery. I wonder if you missed doing lvrmboot in the first place that kept it looking for lvol2 at the old starting location.

-Sri

[twang]

I have increased /stand by using ignite boot tape. I found it is easy and safe.
1. create boot tape with interactive ability:
# make_tape_recovery -AI
2. interactively change the size of LVs on vg00 when booting from the tape

[Fragon]

Hi all,
After remove /vg00/lvol2 and re-create it,can you make sure that lvol2 is contiguous?

Thanks!

[Jairo Campana]

I did a make_tape_recovery -A before of increase /stand

Sridhar Bhaskarla my lvdisplay:
nms1 # lvdisplay /dev/vg00/lvol2
--- Logical volumes ---
LV Name /dev/vg00/lvol2
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 1012
Current LE 253
Allocated PE 253
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

[Michael Steele_2 · Accepted solution]

This is a problem with either /etc/lvmtab or the copy in use by the kernel. So reboot first. If the problem persists then remake /etc/lvmtab using 'vgscan -a -v -p'. '-p' is for preview.

[Jairo Campana]

that great, execelent!!!! Michael Steele
I did reboot and nothing
try
#vgscan -a -p

vgscan: The physical volume "/dev/dsk/c1t2d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c2t2d0" is already recorded in the "/etc/lvmtab" file.
Couldn't stat physical volume "/dev/dsk/c0t1d0":
Invalid argument
/dev/vg00
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Scan of Physical Volumes Complete.
after reboot and I work ok the reconstruc
#lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0
#lvdisplay -v|more
.....
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1012
Current LE 253
Allocated PE 253
Used PV 1
....
my question is :
1.that I made bad in the procedure previously mentioned up.
with no need to do vgscan
2. if I do lvlnboot
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2

it is not necessary #lvlnboot -R

Thank to all

[Michael Steele_2]

No, but it won't hurt.