From what I see you are in mirror using 2 controllers : 0/10/0... and 1/10/0...
If you look, all your LV are like :
Code:
Current LE 256
Allocated PE 512
PE is twice the value of LE ... except the one giving you trouble... only Im a bit stressed now at work, will try to finish rapidly and if no one else had helped you, join back from my laptop at home...
Ah, yes, there are three disks in use on each controller. Whoever initially set this up wasn't thinking and didn't keep the mirrors on distinct controllers since some volumes have data on both sides but the mirror on the other. For instance:
Code:
# lvdisplay -v /dev/vg00/lvol5
--- Logical volumes ---
LV Name /dev/vg00/lvol5
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 3584
Current LE 896
Allocated PE 1792
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c5t5d0 583 583
/dev/dsk/c9t3d0 313 313
/dev/dsk/c9t5d0 896 896
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 /dev/dsk/c5t5d0 00818 current /dev/dsk/c9t5d0 00818 current
00001 /dev/dsk/c5t5d0 00819 current /dev/dsk/c9t5d0 00819 current
00002 /dev/dsk/c5t5d0 00820 current /dev/dsk/c9t5d0 00820 current
00003 /dev/dsk/c5t5d0 00821 current /dev/dsk/c9t5d0 00821 current
... (more of the same until)
00579 /dev/dsk/c5t5d0 02165 current /dev/dsk/c9t5d0 01397 current
00580 /dev/dsk/c5t5d0 02166 current /dev/dsk/c9t5d0 01398 current
00581 /dev/dsk/c5t5d0 02167 current /dev/dsk/c9t5d0 01399 current
00582 /dev/dsk/c5t5d0 02168 current /dev/dsk/c9t5d0 01400 current
00583 /dev/dsk/c9t3d0 00000 current /dev/dsk/c9t5d0 01401 current
00584 /dev/dsk/c9t3d0 00001 current /dev/dsk/c9t5d0 01402 current
00585 /dev/dsk/c9t3d0 00002 current /dev/dsk/c9t5d0 01403 current
00586 /dev/dsk/c9t3d0 00003 current /dev/dsk/c9t5d0 01404 current
... (and still more up to the stale PE)
00650 /dev/dsk/c9t3d0 00067 current /dev/dsk/c9t5d0 01468 current
00651 /dev/dsk/c9t3d0 00068 current /dev/dsk/c9t5d0 01469 current
00652 /dev/dsk/c9t3d0 00069 current /dev/dsk/c9t5d0 01470 stale
00653 /dev/dsk/c9t3d0 00070 current /dev/dsk/c9t5d0 01471 current
00654 /dev/dsk/c9t3d0 00071 current /dev/dsk/c9t5d0 01472 current
... (and on until the bottom)
00893 /dev/dsk/c9t3d0 00710 current /dev/dsk/c9t5d0 01711 current
00894 /dev/dsk/c9t3d0 00711 current /dev/dsk/c9t5d0 01712 current
00895 /dev/dsk/c9t3d0 00712 current /dev/dsk/c9t5d0 01713 current
So if I lose controller 1/10/0 I lose lvol5. But that's a whole other issue.
The pvdisplay is on the first page of this thread and looks fine to me, except for the one stale part.
I looked into the fact that it has a "strict" allocation policy and from what I glean from the lvchange command documentation, that just means that the mirror copies of extents cannot share the same physical volume, which makes sense because you wouldn't want your data mirrored on the same disk because if it failed ...
Code:
-s strict Set the strict allocation policy.
Mirror copies of a logical extent can be
allocated to share or not share the same
physical volume or physical volume
group. This option only makes sense
when the physical volumes of the volume
group that owns the specified logical
volume reside on different physical
disks. strict can have one of the
following values:
y Set a strict allocation policy.
Mirrors of a logical extent cannot
share the same physical volume.
g Set a PVG-strict allocation policy.
Mirrors of a logical extent cannot
share the same physical volume
group.
n Do not set a strict or a PVG-strict
allocation policy. Mirrors of a
logical extent can share the same
physical volume.
When a logical volume is mirrored, the
following changes are not allowed:
+ From nonstrict to strict
+ From nonstrict to PVG-strict
+ From strict to PVG-strict
I thought I was onto something when I saw the -C contiguous option so I could skip the bad extent but that's not available for the root volume group.
I never had stale on HP-UX... (cant say that of the aix's I was in charge...) So I am trying to interpolate from my bad AIX experience... About Contiguous - You do have some... HP-UX11.11 have in vg00 3 Lvols that use contiguous: the swap, root and stand, but its not the case here, how did you change disk? (what commands were passed...) because I think I did have something of the sort with a D class when I forgot to do a ??? forgot.. trying hard to remember you can help since I have no more documentation, you should do a ioscan ( full in doubt, not funC...) to update devs but there is something else I wonder if its not insf -e can you check what that does? because my idea would be to remove the disk if you are sure it is good with no bad blocks etc.. the rm all associated files /dev/rdsk/c.... then add the disk do an insf if its the right command and see if that changes after mirroring again
You do have a disk that is not like the others: c5t5d0 which has 2169 instead of 2170 so there is a bad block there and I wonder if that is not what is giving trouble
Hi everybody,
I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirror. After problem with SAN pathing of our one Datacenter, I have LV at stale state.
# lsvg cpsdata2vg
VOLUME GROUP: cpsdata2vg VG IDENTIFIER: 00fb518c00004c0000000169445f4c2c
VG STATE: ... (6 Replies)
Hi friends,
the paging lv hd6 is in stale condition
hd6 paging 48 96 2 open/stale N/A
And i'am getting the following alerts in the server 333BD283 0811044814 U S LVDD Bad block detected with no relocation al
333BD283 0811041114 U S LVDD ... (1 Reply)
Any package that I try to install, is giving an error of 'lock':
# pkgadd -d openssl-1.0.0g-sol10-sparc-local
The following packages are available:
1 SMCossl openssl
(sparc) 1.0.0g
Select package(s) you wish to process (or 'all' to process
all packages).... (2 Replies)
HP-UX B.11.23 U ia64
I've got two users that show in "w" with long idle times but if I search for their processes I find nothing (ps -ef | grep username )
I'm not sure why "w" still sees them and if there is anything (short of a reboot) that I can do to clean them out.
Ideas? (8 Replies)
my AIX server used to have scsi disk hdisk4. Now i removed that disk. But still it is still listed in lspv. So how can i remove the stale entry of it ? (6 Replies)
There are a filesystem /GWD/appbase/projects/GRIDDB
Under this filesystem there is a directory called backup.
But When I am trying to access the backup directory ,it is showing me the following error:
# cd /GWD/appbase/projects/GRIDDB
# cd backup
-bash: cd: backup: Stale NFS file handle
... (3 Replies)
hi All
I have one RP 3410 server with hp-ux 11.23 mirror disk
it's lvdislay -v /dev/vg00/lvol4 shows stale in some location
Actual is current
pls help me to resolve the probem
I have check with lvsync command and vgsync
but not working
re
Rajesh (1 Reply)
hi, i was trying to mirror root volume group and the command i was using didnt respond for a long time
mirrorvg -m rootvg hdisk1
I was checking rootvg and it gives below. how do i fix stale partitions?? it seems to be on hdisk1
LV NAME TYPE LPs PPs PVs LV STATE ... (2 Replies)
