IJ21108: Encrypted replicas mismatch after mmchdisk starts disks.

APAR status

• Closed as program error.

Error description

• If encryption is not configured properly, starting down disks
  could result in mismatched replicas.
  

Local fix

Problem summary

• If encryption is not configured properly, starting down disks
  could result in mismatched replicas.
  

Problem conclusion

• Benefits of the solution:
  
  
  With the fix, encrypted replicas will be synchronized after down
  disks are started.
  
  Work around:
  
  None
  
  Problem trigger:
  
  During the "start disk", repairing mismatched replicas failed
  on certain files because
  encryption context was not available, and the error
  E_ENC_CTX_NOT_READY
  was treated as a SEVERE error which means that the code
  continues to repair the replicas to the degree possible.
  In the final phase of repair,
  the missupdate flag was incorrectly cleared from the inode
  even though we did not
  synchronize the replicas, as the repair failed due to
  unavailable encryption context.
  As the missupdate flag was cleared from the inode, a subsequent
  "start disk" brought up all down disks, but the file still had
  mismatched replicas.  A later "mmrestripefs -c"
   may then pick up the wrong replica and overwrite the good
  replicas.
  
  Symptom:
  
  Encrypted replicas mismatch after start disk.
  
  Platforms affected:
  
  All
  
  Functional Area affected:
  
  Core
  
  Customer Impact:
  
  Critical
  

Temporary fix

Comments

APAR Information

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

  IJ21104

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

Fix information

• Fixed component name

  GPFS NR POWER E

• Fixed component ID

  5725Q01NP

Applicable component levels