IBM Support

IV01322: BACKBYNAME -U EXITS IF A FILE IS REMOVED WHILE IT IS ARCHIVED APPLIES TO AIX 5300-12

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a file is removed after backbyname -U has started
    archiving it and before we have archived the EA datas,
    backbyname will exit immediately and will not backup the
    remaining files.
    The error message will be :
    <file_name>: A file or directory in the path name does
    not exist.
    If -U is not specified, the following error will be
    displayed :
    backup: 0511-449 An error occurred accessing <file_name>:
    A file or directory in the path name does not exist and
    the backup will continue to backup remaining files.
    

Local fix

  • Using -U flag is useful only when backing up filesystems
    that can hold Extended attributes, this means they have
    EAformat: v2 in lsfs -q.
    If none of the Filesystems you are trying to backup have
    v2 format, then you can simply not use -U flag.
    When using mksysb/savevg this can be done by using -a
    flag to not backup EA attributes.
    Another way is to stop the application playing with these
    files before the backup.
    mksysb and alt_disk_copy are also affected by this error
    and may exhibit an early exit due to this error.  mksysb
    archives that are created when this error is experienced
    are truncated and will not restore.  Errors in these
    components are also resolved with this APAR.
    needed.
    

Problem summary

  • If a file is removed after backbyname -U has started
    archiving it and before we have archived the EA datas,
    backbyname will exit immediately and will not backup the
    remaining files.
    The error message will be :
    <file_name>: A file or directory in the path name does
    not exist.
    If -U is not specified, the following error will be
    displayed :
    backup: 0511-449 An error occurred accessing <file_name>:
    displayed :irectory in the path name does not exist and
    backup: 0511-449 An error occurred accessing <file_name>:
    A file or directory in the path name does not exist and
    the backup will continue to backup remaining files.
    

Problem conclusion

  • The fix is to prevent exiting immediately when we discover
    that file is no more in existance, rather we would
    continue in backing up the remaining files and print
    an appropriate message to warn about this to the user.
    Code changes for the same has been made in the fetchacl
    subroutine.s for the same has been made in the fetchacl
    subroutine.
    

Temporary fix

  • If error is experienced in mksysb, the -a flag may be used to di
    sable
    the -U flag from being used when mksysb calls backup.
    Affected users may instead opt to exclude files that change in s
    ize
    from the backups being created.
    

Comments

  • 5300-12 - use AIX APAR IV01322
    

APAR Information

  • APAR number

    IV01322

  • Reported component name

    AIX 5.3

  • Reported component ID

    5765G0300

  • Reported release

    530

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Submitted date

    2011-06-02

  • Closed date

    2011-08-04

  • Last modified date

    2013-04-07

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

    IV00081

  • 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 U844673

       UP11/10/10 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:
07 April 2013