IT29193: VSNAP CRASHES WITH KERNEL CORE DUMP GENERATED

APAR status

• Closed as program error.

Error description

• vSnap crashes with kernel core dump generated. The
  /var/crash/127.0.0.1-<date timestamp>/vmcore-dmesg.txt displays
  following stack trace:
  
  [164082.645134] Call Trace:[164082.646007] [<ffffffffc05de877>]
  taskq_dispatch+0x37/0x200 [spl]
  [164082.646951] [<ffffffffc0bcac8c>] zil_clean+0xec/0x100 [zfs]
  [164082.647837] [<ffffffffc0b479f7>]
  dsl_pool_sync_done+0x37/0x70 [zfs]
  [164082.648721] [<ffffffffc0b66444>] spa_sync+0x664/0xea0 [zfs]
  
  The crash most likely happens during vSnap replication. The job
  log may contain below error:
  
  INFO,1555642070488,<date timestamp>,2,Copy failed for snapshot
  spp_xxxx volume (<primary vsnap>:spp_xxxx ==> <secondary
  vsnap>:xxxx). Last Error PartnerOperationError: Operation failed
  on partner server <secondary vsnap>: RelationshipUpdateError:
  Failed to update relationship: Snapshot id xxxxx was not found
  on disk
  ERROR,1555642070488,<date timestamp>,2,Skipping remaining
  snapshots for volume <primary vsnap>:spp_xxxx due to
  unrecoverable error
  WARN,1555642070488,<date tiestamp>,2,Error occured on Storage
  Vsnap replication Please check Vsnap Storage logs.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus version 10.1.3                     *
  ****************************************************************
  * 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. Note that this is subject to change at the           *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• A null pointer dereference in the zfs kernel module caused the
  vSnap system to crash. The problem has been resolved by checking
  for and correctly handling the null pointer.
  

Temporary fix

Comments

APAR Information

• 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