topic Re: stale extent sync in Operating System - HP-UX

stale extent sync

masood bt — Wed, 24 Feb 2010 18:18:24 GMT

Just discovered, in PV with key 0 all are stale
in another PE with Key 1, only one LE is stale.

How to convert this particular LE as current?

# lvdisplay -v -k /dev/vg00/lvol1
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c4t6d0s2":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 512
Current LE 32
Allocated PE 64
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c0t6d0s2 32 32

--- Logical extents ---
LE PV1 E1 Status 1 PV2 PE2 Status 2
00000 0 00000 current 1 00000 stale
00001 0 00001 stale 1 00001 current
00002 0 00002 stale 1 00002 current
00003 0 00003 stale 1 00003 current
00004 0 00004 stale 1 00004 current
00005 0 00005 stale 1 00005 current
00006 0 00006 stale 1 00006 current
00007 0 00007 stale 1 00007 current
00008 0 00008 stale 1 00008 current
00009 0 00009 stale 1 00009 current
00010 0 00010 stale 1 00010 current
00011 0 00011 stale 1 00011 current
00012 0 00012 stale 1 00012 current
00013 0 00013 stale 1 00013 current
00014 0 00014 stale 1 00014 current
00015 0 00015 stale 1 00015 current
00016 0 00016 stale 1 00016 current
00017 0 00017 stale 1 00017 current
00018 0 00018 stale 1 00018 current
00019 0 00019 stale 1 00019 current
00020 0 00020 stale 1 00020 current
00021 0 00021 stale 1 00021 current
00022 0 00022 stale 1 00022 current
00023 0 00023 stale 1 00023 current
00024 0 00024 stale 1 00024 current
00025 0 00025 stale 1 00025 current
00026 0 00026 stale 1 00026 current
00027 0 00027 stale 1 00027 current
00028 0 00028 stale 1 00028 current
00029 0 00029 stale 1 00029 current
00030 0 00030 stale 1 00030 current
00031 0 00031 stale 1 00031 current

I used
lvreduce -m 0 -A n –k /dev/vg00/lvol1 0, got the o/p which is understable

"Physical extents on remaining physical volumes are stale"

how to get rid of this one stale PE in disk with key 1

# lvreduce -m 0 -A n -k /dev/vg00/lvol1 0
Physical extents on remaining physical volumes are stale or
Remaining physical volumes are not responding.
lvreduce: The LVM device driver failed to reduce mirrors on
the logical volume "/dev/vg00/lvol1".
#

Re: stale extent sync

Torsten. — Wed, 24 Feb 2010 18:36:57 GMT

Consider to use your backup, since LEs on both disks are stale.

Re: stale extent sync

Steven E. Protter — Wed, 24 Feb 2010 19:53:35 GMT

Shalom,

You might have been able to clear this up with lvsync.

That tool is designed to update stale PE's.

If its not too late, I'd try that. Because of the layout of stale PE's I question the ability of lvreduce to work.

SEP

Re: stale extent sync

masood bt — Thu, 25 Feb 2010 10:59:24 GMT

I will continue this is LVM section's thread.

http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1410438

could you please join me there? thank you.

Re: stale extent sync

Torsten. — Thu, 25 Feb 2010 11:08:46 GMT

Result will not change ...

Re: stale extent sync

Jupinder Bedi — Thu, 25 Feb 2010 11:11:34 GMT

try with

vgsync vg00

Good luck

Re: stale extent sync

masood bt — Thu, 25 Feb 2010 11:16:19 GMT

hi....

I need to le tyou all know this.

This server which I am trying to boot up has only one disk..not two.

This disk is actually a mirror made from another runnin server.

When I try to boot this new server with this new mirrored disk....

The server assumes there are two disks, not one.

When I boot the server, it gives the INIT respawning errors and says "the system is ready" but with no (login) prompt.

I booted it in single user mode.

vgdisplay etc informs me that it couldnt query c4t6d0...
c4t6d0 is not in the server at all!
c0t6d0 is present.only one disk is present.

I conclude this from ioscan and PVname at the bottom of the vgdisplay o/p.

I tried to remove the 'not existing' disk by removing the mirror

# lvreduce -m 0 -A n /dev/vg00/lvol1 /dev/dsk/c4t6d0
lvreduce: Warning: couldn't query physical volume "/dev/dsk/c4t6d0s2":
The specified path does not correspond to physical volume attached to
this volume group
lvreduce: Warning: couldn't query all of the physical volumes.
lvreduce: Physical volume "/dev/dsk/c4t6d0" does not belong
to volume group "/dev/vg00".
Logical volume "/dev/vg00/lvol1" is not reduced.
#

then i try using the PV key instead of PV name (here key is 0)

# lvreduce -m 0 -A n -k /dev/vg00/lvol1 0
Physical extents on remaining physical volumes are stale or
Remaining physical volumes are not responding.
lvreduce: The LVM device driver failed to reduce mirrors on
the logical volume "/dev/vg00/lvol1".
#

I noticed the o/p here
"Physical extents on 'remaining physical' volumes are stale"

that means there are stale extents in the existing disk(c0t6d0) too.

# lvdisplay -v -k /dev/vg00/lvol1
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c4t6d0s2":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 512
Current LE 32
Allocated PE 64
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c0t6d0s2 32 32

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 0 00000 current 1 00000 stale
00001 0 00001 stale 1 00001 current
00002 0 00002 stale 1 00002 current
00003 0 00003 stale 1 00003 current
00004 0 00004 stale 1 00004 current

extent @ 0000 in PV2 too is stale.

When I check lvol3, lvol4 etc, there are more than one stale extents in existing PV with key1

All are stale extents in the non existing PV with key 0

as suggesting by you guys, restoring the backup is god, but i do not have!

Now what could be solution for me so as to boot the server.

Re: stale extent sync

masood bt — Thu, 25 Feb 2010 11:21:44 GMT

# vgsync vg00
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol1".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol2".
Resynchronized logical volume "/dev/vg00/lvol3".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol4".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol5".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol6".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol7".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol8".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol9".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol10".
vgsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
vgsync: Couldn't resynchronize logical volume "/dev/vg00/lvol11".
vgsync: Couldn't resynchronize volume group "vg00".
#

# lvsync /dev/vg00/lvol1
lvsync: Couldn't re-synchronize stale partitions of the logical volume:
I/O error
lvsync: Couldn't resynchronize logical volume "/dev/vg00/lvol1".
#

Re: stale extent sync

Torsten. — Thu, 25 Feb 2010 13:02:50 GMT

Again, "stale" means bad.

You cannot "convert" a bad disk into a good disk.

If you find a way to do this, let me know ...

;-)

Re: stale extent sync

masood bt — Thu, 25 Feb 2010 13:08:28 GMT

points for humour too

:-)

Re: stale extent sync

Torsten. — Thu, 25 Feb 2010 13:14:35 GMT

If this disk is taken from a mirror from another server, use a new disk, mirror again and start over.

Re: stale extent sync

masood bt — Fri, 26 Feb 2010 10:18:45 GMT

Thanks to all here. I will pass on this for now. I shall close this thread tomorrow.

Re: stale extent sync

masood bt — Thu, 04 Mar 2010 18:22:33 GMT

the disk has stale extents..need to re mirror