PowerHA for AIX

 View Only

PowerHA-6.1.0 SP16 C-SPOC defects / strange bahaviour

  • 1.  PowerHA-6.1.0 SP16 C-SPOC defects / strange bahaviour

    Posted Fri December 18, 2015 08:52 AM

    Originally posted by: PontiacGeronimo


    hello,

    I have a shared VG in the cluster on VSCSI disks (reserve_policy=no_reserve)

    when I go to:

    System Management (C-SPOC) -> Storage -> Volume Groups -> Set Characteristics of a Volume Group

    shortcut:

    smitty cl_vgsc

     

    and when I selected e.g. "Add a Volume to a Volume Group" some mess was output in smitty window:

     

    1800-050 Error exit status (1) returned by
    Command_to_List; the output is:
    "#Volume Group    Resource Group             Node List           VG Type
     hb1vg          <Not in a Resource Group>  NODE1,NODE2             0
     hb2vg          <Not in a Resource Group>  NODE1,NODE2             0
     datavg          DB_RG                 NODE1,NODE2             0
    rm: /tmp/cel13566022_s19.out: No such file or directory
    NODE1: /dev/old_rootvg not found
    NODE1: 0516-604 importvg: Physical volume name not entered.
    NODE1: Usage: importvg [ [ [-V MajorNumber] [-y VGname] [-f] [-c] [-x] ] | [-L VGname] ]
    NODE1:                [-n] [-F] [-R] [-O] PVname
    NODE1: Imports the definition of a volume group.
    NODE1: 0516-604 importvg: Physical volume name not entered.
    NODE1: Usage: importvg [ [ [-V MajorNumber] [-y VGname] [-f] [-c] [-x] ] | [-L VGname] ]
    NODE1:                [-n] [-F] [-R] [-O] PVname
    NODE1: Imports the definition of a volume group.
    NODE1: cdsh: cl_rsh: (RC=1) /usr/es/sbin/cluster/cspoc/cexec  clvaryonvg  old_rootvg
    error executing clvaryonvg old_rootvg on node NODE1
    Error detail:
        NODE1: 0516-082 varyonvg: Unable to access a special device file.
        NODE1:     Execute redefinevg and synclvodm to build correct environment.
        NODE1: 0516-082 varyonvg: Unable to access a special device file.
        NODE1:     Execute redefinevg and synclvodm to build correct environment.
        NODE1: updating local VG info for old_rootvg, this may take a while
        NODE1: RETURN_CODE=0
        NODE1: RETURN_CODE=0
        NODE1: /dev/old_rootvg not found
        NODE1: 0516-604 importvg: Physical volume name not entered.
        NODE1: Usage: importvg [ [ [-V MajorNumber] [-y VGname] [-f] [-c] [-x] ] | [-L VGname] ]
        NODE1:            [-n] [-F] [-R] [-O] PVname
        NODE1: Imports the definition of a volume group.
        NODE1: 0516-604 importvg: Physical volume name not entered.
        NODE1: Usage: importvg [ [ [-V MajorNumber] [-y VGname] [-f] [-c] [-x] ] | [-L VGname] ]
        NODE1:            [-n] [-F] [-R] [-O] PVname
        NODE1: Imports the definition of a volume group.
        NODE1: RETURN_CODE=1
        NODE1: cdsh: cl_rsh: (RC=1) /usr/es/sbin/cluster/cspoc/cexec  clvaryonvg  old_rootvg
    


     

    After several tries and such errors on output, now  I see that errors are gone and..... old_rootvg "disappeared" on both nodes (old_rootvg's were probably exported from systems when I selected "Add volume to cluster VG" in CPOC)

    Isn't this strange that C-SPOC does something what is not under it's responsibility? Besides I did not run any real action yet from C-SPOC - just selecting option from menu - it must have do bad job during scanning/collecting system information. And the old_rootvg was old system VG, not related to the cluster configuration at all in this case.

     

    Besides, the cluster was and is up and running stable all the time..

     

    kind regards,