Posts tagged ·

varyonvg

·...

April 1, 2011 11:01 pm

AIX LVM QUORUM mysteries revealed

Comments Off
by    in AIX

 Technote (FAQ)
 
Question
Why can't I varyon a Volume Group when one or more physical volumes are not available?
 
Cause
Varyonvg requires 100% of it's physical volumes be available and accessible in order to successfully vary on the Volume Group without using the force option.
 
Answer
A common misconception is that the QUORUM setting of an LVM Volume Group can affect one's ability to varyon a volume group, when, in fact, the Volume Group QUORUM setting (enabled or disabled) has no bearing on the varyon process. This misconception is further enhanced by the following varyonvg error message...
0516-052 varyonvg: Volume group cannot be varied on without a
       quorum. More physical volumes in the group must be active.

This message indicates a "quorum" of physical volumes must exist in order to varyon the Volume Group and is unrelated to the Volume Group's QUORUM setting.

The Volume Group QUORUM setting is a concept that applies only to currently varied on Volume Groups in order to force varyoff of the Volume Group should it lose more than 51% of it's disks. With QUORUM disabled on the Volume Group, loss of one or more disks will not cause the Volume Group to varyoff. If QUORUM is enabled on the Volume Group, LVM will force varyoff the Volume Group if less than 51% of it's disks are available and accessible. For a two disk Volume Group with QUORUM enabled, LVM will check the number of VGDAs on each disk and varyoff the Volume Group should it lose QUORUM (if it loses the disk with two active VGDA's).

The Volume Group's QUORUM setting has no meaning for a Volume Group which is currently varied off. Varyonvg does not look at how many VGDAs a disk has, it ONLY looks at the number of physical volumes which are available and accessible. Without the -f (force) flag, ALL physical volumes in a Volume Group must be available and accessible. If one or more physical volumes is unavailable, the Volume Group may be forced online with varyonvg -f.


Excerpts from the varyonvg man page...

"The varyonvg will fail to varyon the volume group if a majority of the physical volumes are not accessible (no Quorum). This condition is true even if the quorum checking is disabled. Disabling the quorum checking will only ensure that the volume group stays varied on even in the case of loss of quorum."

"If the volume group cannot be varied on due to a loss of the majority of physical volumes, a list of all physical volumes with their status is displayed. To varyon the volume group in this situation, you will need to use the force option."

"-f Allows a volume group to be made active that does not currently have a quorum of available disks. All disk that cannot be brought to an active state will be put in a removed state. At least one disk must be available for use in the volume group."
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Operating SystemsAIX family AIX5.2, 5.3, 6.1
 
 
tags: , , , , , ,
Comments Off
March 19, 2010 1:53 am

0516-008 varyonvg: LVM system call returned an unknown error code (3).

Comments Off
by    in AIX 
Problem:

The system was rebooted itself and they can't varyon
             a volume group:
              varyonvg vgss01page
              0516-008 varyonvg: LVM system call returned an unknown
              error code (3).

Solution:

lsvg -o  -> not variedon
lspv:

hdisk2          000df0af41b969ae                    vgss01page
hdisk3          000df0af3ca7e15f                    vgss01page

lquerypv -h /dev/hdisk2 80 10
00000080   000DF0AF 41B969AE 00000000 00000000  |....A.i.........|

lquerypv -h /dev/hdisk3 80 10
00000080   000DF0AF 3CA7E15F 00000000 00000000  |....<.._........|

lqueryvg -Atp hdisk2 and hdisk3 gives the proper information  except for
Physical:       000df0afc5256113   1   0  which is not part of the vg

chpv -va hdisk2 -> 0516-010 lqueryvg: Volume group must be varied on;
use varyonvg command.
0516-722 chpv: Unable to change physical volume hdisk2.

chpv -va hdisk3 -> 0516-010 lqueryvg: Volume group must be varied on;
use varyonvg command.
0516-722 chpv: Unable to change physical volume hdisk3.

exportvg vgss01page -> ok
rmdev -dl hdis2 -> ok
rmdev -dl hdisk3 -> ok

cfgmgr -> hanging for a while but completed
importvg -y vgss01page hdisk2 ->

0516-304 getlvodm: Unable to find device id 000df0afc5256113 in the
Device
       Configuration Database.
PV Status:      hdisk2  000df0af41b969ae        PVACTIVE
               hdisk3  000df0af3ca7e15f        PVACTIVE
                       000df0afc5256113        NONAME
varyonvg: Volume group vgss01page is varied on.
0516-510 synclvodm: Physical volume not found for physical volume
       identifier 000df0afc52561130000000000000000.
0516-548 synclvodm: Partially successful with updating volume
       group vgss01page.
vgss01page
PV Status:      hdisk2  000df0af41b969ae        PVACTIVE
               hdisk3  000df0af3ca7e15f        PVACTIVE
                       000df0afc5256113        NONAME
varyonvg: Volume group vgss01page is varied on.
lsvg -l vgss01page
vgss01page:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT
POINT
paging01            paging     271   271   1    closed/syncd  N/A

13:39(usehss01:/export/home/root) # uptime
 01:41PM   up   5:51,  5 users,  load average: 0.03, 0.04, 0.05
13:41(usehss01:/export/home/root) #

sysdumpdev -L
0453-039

Device name:         /dev/sysdumpnull
Major device number: 7
Minor device number: 2
Size:                0 bytes
Date/Time:           Wed Dec 31 19:00:00 EST 1969
Dump status:         -1
no dump device defined

# sysdumpdev -l
primary              /dev/sysdumpnull
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    TRUE
dump compression     OFF

sent customr a technote procedure to create a valid dump device

reducevg -d vgss01page 000df0afc5256113

reducevg -d vgss01page 000df0afc5256113
0516-304 putlvodm: Unable to find device id
000df0afc52561130000000000000000 in the Device
       Configuration Database.
0516-896 reducevg: Warning, cannot remove physical volume
000df0afc5256113 from Device Configuration Database.

lsvg -p vgss01page
vgss01page:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE
DISTRIBUTION
hdisk2            active            271         0
00..00..00..00..00
hdisk3            active            542         542
109..108..108..108..109

swapon -a to actvate the paging space
tags: ,
Comments Off