IBM Support

IZ90925: MOUNT POINT CHANGE IN CONCURRENT VG DOESN'T UPDATE REMOTE ODM APPLIES TO AIX 5300-10

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Mount point change with auto-mount option run on a file
    system belonging to concurrent vg does not update the
    LV ODM changes on the remote node.
    
    The scenario that affects customers is:
    -nodeA has the VG in Active mode, nodeB in Passive mode
    -the Mount Point is changed in CSPOC
    * nodeB LV ODM label attribute isn't updated
    -Move RG from nodeA to nodeB
    -Move RG from nodeB to nodeA
    >> Here PowerHA fails trying to unmount the old mount
    point
    that it gets from the LV ODM
    

Local fix

Problem summary

  • In an HACMP cluster...
    Chfs is called to change a filesystem mountpoint AND some other
    filesystem properties, such as auto-mount.
    
    The remote node in the cluster does not have it's LVM ODM
    information updated with the new filesystem label.
    
    After Moving the HA RG to the remote node, then trying to move
    it back, HA will fail because of trying to unmount the
    incorrect mount point
    

Problem conclusion

  • Ensure that chfs will propagate LVM ODM changes in LV label
    value to remote nodes in all cases.
    

Temporary fix

Comments

  • 5300-10 - use AIX APAR IZ90925
    5300-11 - use AIX APAR IZ81477
    5300-12 - use AIX APAR IZ90766
    6100-03 - use AIX APAR IZ93718
    6100-04 - use AIX APAR IZ93631
    6100-05 - use AIX APAR IZ84466
    6100-06 - use AIX APAR IZ93105
    6100-06 - use AIX APAR IZ85805
    7100-00 - use AIX APAR IZ85552
    

APAR Information

  • APAR number

    IZ90925

  • Reported component name

    AIX 5.3

  • Reported component ID

    5765G0300

  • Reported release

    530

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Submitted date

    2010-12-14

  • Closed date

    2010-12-14

  • Last modified date

    2013-04-17

  • APAR is sysrouted FROM one or more of the following:

    IZ81477

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    AIX 5.3

  • Fixed component ID

    5765G0300

Applicable component levels

  • R530 PSY U840527

       UP11/02/23 I 1000

PTF to Fileset Mapping

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11P","label":"APARs - AIX 5.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"530","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 April 2013