IBM Support

IT29793: FILE-BASED VSNAP POOL CANNOT BE STARTED ANYMORE AFTER UPGRADE TO 10.1.4

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After the upgrade to 10.1.4.0, the file-based (for example NFS)
    vSnap pool does not come online.
    The vSnap host message log will displays at vSnap startup:
    
    "cannot import '<poolname>': no such pool available"
    
    The vSnap startup logic was updated in version 10.1.4 with a new
    import method which auto-discovers disks in the pool by scanning
    the /dev directory.
    This was done to no longer rely on the pool cache file in
    case it is corrupted for any reason to still be able to mount
    it.
    But this change prevents to mount pools using files (for example
    NFS) instead of disks devices as that type of pool does need the
    cache for the import process.
    
    Use of file-based vSnap pools is intended for demonstration
    purposes only and is not a supported feature of
    IBM Spectrum Protect Plus.
    
    IBM Spectrum Protect Versions Affected:
    IBM Spectrum Protect Plus 10.1.4.0
    
    | MDVREGR SPP 10.1.4.0 |
    
    Initial Impact: High
    
    Additional Keywords: SPP, SPPLUS, TS002434541, startup, pool,
    vsnap, start
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus level 10.1.4.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in IBM Spectrum Protect Plus level     *
    * 10.1.4.179 and 10.1.5                                        *
    ****************************************************************
    

Problem conclusion

  • Starting with 10.1.4, vSnap introduced a new procedure to mount
    the pool during boot up. Instead of relying on a cachefile,
    vSnap now scans the /dev directory to auto-discover pool disks
    and mounts them. This change was made to address the problem
    described in APAR IT29086. However this change did not work for
    pools created using files in a filesystem. Since the files do
    not exist under /dev, they cannot be found and the pool fails to
    mount. The problem has been addressed by revising the startup
    logic. If the pool disks are not found under /dev, vSnap falls
    back to the older logic of relying on the cachefile which
    contains the file paths. This ensures that file-backed pools are
    correctly mounted during boot.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29793

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A14

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-30

  • Closed date

    2019-08-14

  • Last modified date

    2019-09-30

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

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

Fix information

  • Fixed component name

    SP PLUS

  • Fixed component ID

    5737SPLUS

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A14","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
30 January 2024