IJ50067: RESYNCV2 SHOULDN'T CONSIDER RECOVERY DIRS WHENAFMSKIPRESYNCRECOVERY IS SET

APAR status

• Closed as program error.

Error description

• When afmResyncVer2 is run with afmSkipResyncRecovery set to
  yes,then the priority directories that AFM usually queues
  shouldnot be done. Since such directories might exist
  underparents that are not in sync already leading to error 112.
  

Local fix

• fallback to Resync Version1 where afmSkipResyncRecoveryhas
  effect.
  

Problem summary

• When afmResyncVer2 is run with afmSkipResyncRecovery set to
  yes,then the priority directories that AFM usually queues
  shouldnot be done. Since such directories might exist
  underparents that are not in sync already leading to error 112.
  

Problem conclusion

• This problem is fixed in 5.1.9.3
  To see all Spectrum Scale APARs and their respective
  Fix solutions refer to page:
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  
  Benefits of the solution:
  Skip queuing priority directories for recyncV2
  ifafmSkipResyncRecovery is set.
  
  Work Around:
  fallback to Resync Version1 where afmSkipResyncRecoveryhas
  effect.
  
  Problem trigger:
  Run afmResyncVer2 on a fileset which has never had syncto home
  and set afmSkipResyncRecovery on it.
  
  Symptom:
  Unexpected Behavior
  
  Platforms affected:
  Linux Only
  
  Functional Area affected:
  AFM
  
  Customer Impact:
  High Importance
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels