IT29759: IBM SPECTRUM PROTECT PLUS REPLICATION FAILS WITH "TRANSFER FAILED: [ERRNO 32] BROKEN PIPE" AFTER PRIOR JOB WAS CANCELLED.

APAR status

• Closed as program error.

Error description

• Cancelling a replication job does not properly clean
  up the replication transfer. This can lead to
  problem the next time replication is run.
  The job log will show:
  Error occured on Storage Vsnap replication Please check Vsnap
  Storage logs.
  Copy failed for snapshot spp_1027_2169_72_16b2647789d(2336)
  volume
  (localhost:spp_1027_2169_16b0b190158__16b0b192947_55_Datastore_M
  Y_HD_ ==> mysrvspp01:3c45f7226896ed19ae62dd7303f9241a). Last
  Error TransferError: Transfer failed: [Errno 32] Broken pipe
  Skipping remaining snapshots for volume
  localhost:spp_1027_2169_16b0b190158__16b0b192947_55_Datastore_MY
  _HD_ due to unrecoverable error
  vSnap repl.log fails with:
  Recieve operation failed: cannot receive incremental stream:
  dataset is busy
  Versions affected: 10.1.x
  

Local fix

• Ensure that no replication jobs are running.
  Run "sudo pkill -f 'zfs recv'" on both vSnaps
  

Problem summary

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

Problem conclusion

• When a vSnap replication session failed or was canceled, under
  certain conditions the data transfer pipe was not gracefully
  closed. This resulted in some hung processes being left behind
  on the replication target vSnap. During subsequent replication
  attempts, this would result in a "broken pipe" error. The
  problem has been resolved by improving the failure and
  cancellation logic to ensure that transfer pipes are closed
  gracefully when the replication ends.
  

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