topic Re: stale extents and then good? in Operating System - HP-UX

stale extents and then good?

brian_31 — Sun, 18 Feb 2007 11:49:30 GMT

I have a situation where i am going to reboot this server and when i do a lvdisplay -v on the lvol1/lvol3 etc all are good. i ran a lvlnboot -R and after that i see that lvdisplay reports available/stale. what could have happenened.
# 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)
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c2t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0

before the lvlnboot -R both were showing as boot disk. how do i fix this? will this reboot OK. what shd i do to fix this

Thanks

Brian

Re: stale extents and then good?

Mel Burslan — Sun, 18 Feb 2007 13:03:38 GMT

Brian,

More than likely a reboot will not solve this problem, if not making it worse.

I am not sure how an

lvlnboot -R command can cause such an outcome but you may have lost the c1t2d0 disk a while back and when you try to do a sort of low level disk operation with the lvlnboot command, tha failure may have exhibited itself.

what does an

ioscan -fnC disk

command say ? Can you see bot disks as claimed devices ?

Re: stale extents and then good?

Steven E. Protter — Sun, 18 Feb 2007 14:04:39 GMT

Shalom,

If due to a sudden boot like an unplanned poweroff extents became stale, the lvsync process can and should fix this.

A boot will normally correct this, but it can be run manually.

But it seems your system is booted off its second disk, not its first boot disk. It woule appear that /dev/dsk/c1t2d0 (0/0/1/1.2.0) may be in a bit of trouble if not totally offline.

ioscan

mstm/cstm or xstm check it out carefully.

I'd try and get an emergency ignite make_tape_recovery before booting just in case it doesn't.

SEP

Re: stale extents and then good?

Emil Velez — Sun, 18 Feb 2007 20:54:22 GMT

Could you have lost a disk, replaced it and then did a bunch of lvextends without a lvcreate -B and a couple of mkboot commands before you did a lvextend -m 1

It looks like the data is mirrored on the disk but the OS does not recognize the boot structures.

The best way to fix this probably is to lvextend -m 0 of all the LVs, remove the disk from vg00, pvcreate -B the disk,mkboot, mkboot -a, then lvextend -m of all of the LVs. if the boot structure is fixed then lvlnboot -v will show both disks with boot structures.

good luck..I would create a make_recovery tape/ignite image before doing anything and not reboot till I got the ignite image and get vg00 fixed up. You must plan for LVM to work. IT will not work unless you plan well. Do not just try stuff..

I wish you luck.
Emil