Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Stale Partitions 4
- Thread starter Roomer
- Start date
-
2
- #3
Roomer,
Stale partitions occur when the second and/or third mirrored copies of data become out of sync. with the primary copy.
Look in the error report for the effected disk/s, if you cannot find the disk go through each volume group and run:
lsvg -l <vgname>
At the end of the line if you see :
open/stale
Then re-sync. this volume group:
syncvg -v <vgname>
Repeat the lsvg -l <vgname> command and all logical volumes should be:
open/syncd
Any more problems re-post - if that does not work your disk could be on the way out, or you may have a number of bad blocks and reorgvg may sort that out.
Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
Stale partitions occur when the second and/or third mirrored copies of data become out of sync. with the primary copy.
Look in the error report for the effected disk/s, if you cannot find the disk go through each volume group and run:
lsvg -l <vgname>
At the end of the line if you see :
open/stale
Then re-sync. this volume group:
syncvg -v <vgname>
Repeat the lsvg -l <vgname> command and all logical volumes should be:
open/syncd
Any more problems re-post - if that does not work your disk could be on the way out, or you may have a number of bad blocks and reorgvg may sort that out.
Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
-
1
- Thread starter
- #4
PSD - Any clues ? Error message when running syncvg ....
root@hqax03 / >syncvg -v oraclevg
0516-068 lresynclv: Unable to completely resynchronize volume. Run
diagnostics if neccessary.
0516-932 /usr/sbin/syncvg: Unable to synchronize volume group oraclevg.
root@hqax03 / >syncvg -v oraclevg
0516-068 lresynclv: Unable to completely resynchronize volume. Run
diagnostics if neccessary.
0516-932 /usr/sbin/syncvg: Unable to synchronize volume group oraclevg.
-
1
- #5
- Thread starter
- #6
Results from lsvg -p oraclevg ....
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 542 42 00..00..00..00..42
hdisk3 active 542 291 109..00..00..73..109
hdisk4 active 542 292 109..00..00..74..109
hdisk5 active 542 292 109..00..00..74..109
hdisk6 active 542 42 00..00..00..00..42
hdisk7 active 542 292 109..00..00..74..109
hdisk8 active 542 292 109..00..00..74..109
hdisk9 missing 542 292 109..00..00..74..109
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 542 42 00..00..00..00..42
hdisk3 active 542 291 109..00..00..73..109
hdisk4 active 542 292 109..00..00..74..109
hdisk5 active 542 292 109..00..00..74..109
hdisk6 active 542 42 00..00..00..00..42
hdisk7 active 542 292 109..00..00..74..109
hdisk8 active 542 292 109..00..00..74..109
hdisk9 missing 542 292 109..00..00..74..109
- Thread starter
- #8
Results ...
root@hqax03 / >lsdev -Cc disk
hdisk0 Available 40-60-00-4,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 40-60-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 40-61-00-0,0 16 Bit LVD SCSI Disk Drive
hdisk3 Available 40-61-00-1,0 16 Bit LVD SCSI Disk Drive
hdisk4 Available 40-61-00-2,0 16 Bit LVD SCSI Disk Drive
hdisk5 Available 40-61-00-3,0 16 Bit LVD SCSI Disk Drive
hdisk6 Available 40-61-00-4,0 16 Bit LVD SCSI Disk Drive
hdisk7 Available 40-61-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk8 Available 40-61-00-6,0 16 Bit LVD SCSI Disk Drive
hdisk9 Available 40-61-00-8,0 16 Bit LVD SCSI Disk Drive
root@hqax03 / >lsdev -Cc disk
hdisk0 Available 40-60-00-4,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 40-60-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 40-61-00-0,0 16 Bit LVD SCSI Disk Drive
hdisk3 Available 40-61-00-1,0 16 Bit LVD SCSI Disk Drive
hdisk4 Available 40-61-00-2,0 16 Bit LVD SCSI Disk Drive
hdisk5 Available 40-61-00-3,0 16 Bit LVD SCSI Disk Drive
hdisk6 Available 40-61-00-4,0 16 Bit LVD SCSI Disk Drive
hdisk7 Available 40-61-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk8 Available 40-61-00-6,0 16 Bit LVD SCSI Disk Drive
hdisk9 Available 40-61-00-8,0 16 Bit LVD SCSI Disk Drive
Roomer,
Are there any errors regarding hdisk9 in the error report?
lspv -l hdisk9
What does this return?
It is quite possible that the disk has failed. Post up any output from error report in relation to disk errors.
Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
Are there any errors regarding hdisk9 in the error report?
lspv -l hdisk9
What does this return?
It is quite possible that the disk has failed. Post up any output from error report in relation to disk errors.
Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
- Thread starter
- #11
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
varyonvg: Volume group oraclevg is varied on.
PV Status: hdisk2 005587da5c30ffe4 PVACTIVE
hdisk3 005587da5c31b702 PVACTIVE
hdisk4 005587da5c31b810 PVACTIVE
hdisk5 005587da5c31b911 PVACTIVE
hdisk6 005587da5c31ba10 PVACTIVE
hdisk7 005587da5c31bb0c PVACTIVE
hdisk8 005587da5c31bc0b PVACTIVE
hdisk9 005587da5c31bd07 PVMISSING
Before command completion, additional instructions may appear below.
varyonvg: Volume group oraclevg is varied on.
PV Status: hdisk2 005587da5c30ffe4 PVACTIVE
hdisk3 005587da5c31b702 PVACTIVE
hdisk4 005587da5c31b810 PVACTIVE
hdisk5 005587da5c31b911 PVACTIVE
hdisk6 005587da5c31ba10 PVACTIVE
hdisk7 005587da5c31bb0c PVACTIVE
hdisk8 005587da5c31bc0b PVACTIVE
hdisk9 005587da5c31bd07 PVMISSING
- Thread starter
- #13
root@hqax03 / >lspv
hdisk0 005587da309eaa13 rootvg
hdisk1 005587da9d18dbef rootvg
hdisk2 005587da5c30ffe4 oraclevg
hdisk3 005587da5c31b702 oraclevg
hdisk4 005587da5c31b810 oraclevg
hdisk5 005587da5c31b911 oraclevg
hdisk6 005587da5c31ba10 oraclevg
hdisk7 005587da5c31bb0c oraclevg
hdisk8 005587da5c31bc0b oraclevg
hdisk10 none None
root@hqax03 / >lsvg oraclevg
VOLUME GROUP: oraclevg VG IDENTIFIER: 005587da5c31aefe
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 4336 (69376 megabytes)
MAX LVs: 256 FREE PPs: 1835 (29360 megabytes)
LVs: 5 USED PPs: 2501 (40016 megabytes)
OPEN LVs: 0 QUORUM: 5
TOTAL PVs: 8 VG DESCRIPTORS: 8
STALE PVs: 1 STALE PPs: 27
ACTIVE PVs: 7 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
root@hqax03 / >lsvg -l oraclevg
oraclevg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
lv2 jfs 500 1000 2 closed/syncd /u01
loglv00 jfslog 1 1 1 closed/syncd N/A
lv3 jfs 250 500 2 closed/syncd /u02
lv4 jfs 250 500 2 closed/syncd /u03
lv5 jfs 250 500 2 closed/stale /u04
root@hqax03 / >lsvg -p oraclevg
oraclevg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 542 42 00..00..00..00..42
hdisk3 active 542 291 109..00..00..73..109
hdisk4 active 542 292 109..00..00..74..109
hdisk5 active 542 292 109..00..00..74..109
hdisk6 active 542 42 00..00..00..00..42
hdisk7 active 542 292 109..00..00..74..109
hdisk8 active 542 292 109..00..00..74..109
hdisk9 missing 542 292 109..00..00..74..109
hdisk0 005587da309eaa13 rootvg
hdisk1 005587da9d18dbef rootvg
hdisk2 005587da5c30ffe4 oraclevg
hdisk3 005587da5c31b702 oraclevg
hdisk4 005587da5c31b810 oraclevg
hdisk5 005587da5c31b911 oraclevg
hdisk6 005587da5c31ba10 oraclevg
hdisk7 005587da5c31bb0c oraclevg
hdisk8 005587da5c31bc0b oraclevg
hdisk10 none None
root@hqax03 / >lsvg oraclevg
VOLUME GROUP: oraclevg VG IDENTIFIER: 005587da5c31aefe
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 4336 (69376 megabytes)
MAX LVs: 256 FREE PPs: 1835 (29360 megabytes)
LVs: 5 USED PPs: 2501 (40016 megabytes)
OPEN LVs: 0 QUORUM: 5
TOTAL PVs: 8 VG DESCRIPTORS: 8
STALE PVs: 1 STALE PPs: 27
ACTIVE PVs: 7 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
root@hqax03 / >lsvg -l oraclevg
oraclevg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
lv2 jfs 500 1000 2 closed/syncd /u01
loglv00 jfslog 1 1 1 closed/syncd N/A
lv3 jfs 250 500 2 closed/syncd /u02
lv4 jfs 250 500 2 closed/syncd /u03
lv5 jfs 250 500 2 closed/stale /u04
root@hqax03 / >lsvg -p oraclevg
oraclevg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 542 42 00..00..00..00..42
hdisk3 active 542 291 109..00..00..73..109
hdisk4 active 542 292 109..00..00..74..109
hdisk5 active 542 292 109..00..00..74..109
hdisk6 active 542 42 00..00..00..00..42
hdisk7 active 542 292 109..00..00..74..109
hdisk8 active 542 292 109..00..00..74..109
hdisk9 missing 542 292 109..00..00..74..109
OK..as a previous post says...check the errpt. It looks like hdisk9 was lost. It may need to be replaced. Get a service call opened to IBM (or your hardware service folks) and have them take a look at it. Your LV's are mirrored, so your data is not at risk. Remove the bad mirrored copy. Hopefully you allocated your partitions properly.
# smitty rmlvcopy
Enter the LV name and set # copies to 1. Don't bother specifying an hdisk#.
If your partitions were allocated properly, you should be able to do this and should return to normal.
Bill.
# smitty rmlvcopy
Enter the LV name and set # copies to 1. Don't bother specifying an hdisk#.
If your partitions were allocated properly, you should be able to do this and should return to normal.
Bill.
- Thread starter
- #15
If the disks which are marked as 'stale' are available, then varyoffvg and varyonvg is the simplest you can do.
This will automatically solve your problem. However, this means that you need to stop all your applications/programs accessing the concerned volume groups.
However there is an un-convenitonal / work around approach:
check the mirroring is ok or not
lsvg -o <volume group>
lslv -m <lv name> ensure that the PPs are distributed
properly across the PVs.
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk41 0001 hdisk46
0002 0002 hdisk41 0002 hdisk46
0003 0003 hdisk41 0003 hdisk46
0004 0004 hdisk41 0004 hdisk46
......... .............. .............
0446 0446 hdisk41 0446 hdisk46
0447 0447 hdisk41 0447 hdisk46
0448 0448 hdisk41 0448 hdisk46
0449 0449 hdisk41 0449 hdisk46
0450 0450 hdisk41 0450 hdisk46
c. If a. and b. are ok
unmirrorvg <remove the missing disk>
reducevg <remove the missing disk>
extendvg <add the 'missed disk'>
mirrorvg <add the mirror copy with the 'missed disk'
[This disk is no longer missed now]
Choose -S option. The syncvg mirroring or re-silvering
will be done in the back ground.
This is a tried and tested procedure by me. It works. There is no problems.
This will automatically solve your problem. However, this means that you need to stop all your applications/programs accessing the concerned volume groups.
However there is an un-convenitonal / work around approach:
check the mirroring is ok or not
lsvg -o <volume group>
lslv -m <lv name> ensure that the PPs are distributed
properly across the PVs.
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk41 0001 hdisk46
0002 0002 hdisk41 0002 hdisk46
0003 0003 hdisk41 0003 hdisk46
0004 0004 hdisk41 0004 hdisk46
......... .............. .............
0446 0446 hdisk41 0446 hdisk46
0447 0447 hdisk41 0447 hdisk46
0448 0448 hdisk41 0448 hdisk46
0449 0449 hdisk41 0449 hdisk46
0450 0450 hdisk41 0450 hdisk46
c. If a. and b. are ok
unmirrorvg <remove the missing disk>
reducevg <remove the missing disk>
extendvg <add the 'missed disk'>
mirrorvg <add the mirror copy with the 'missed disk'
[This disk is no longer missed now]
Choose -S option. The syncvg mirroring or re-silvering
will be done in the back ground.
This is a tried and tested procedure by me. It works. There is no problems.
- Status