IJ30451: MMRESTRIPEFILE TAKES 20~30 MINUTES WITHOUT ANY REPAIRING DONE

APAR status

• Closed as program error.

Error description

• When trying to rebalance a greatly unbalanced
  file via mmrestripefile -b [ --strict]] -F filename
  the command runs for several 10s of minutes, and returns
  ok, without having done any change on the balancing of
  the file.
  

Local fix

• check with mmlsattr -L  filename   if a unbalanced flag
  is
  set. If not, suspend and resume a disk in the filesystem,
  that will set the 'unbalanced' flag. After this is set,
  rerun the mmrestripefile.
  

Problem summary

• When a user starts the mmrestripefile command
  against a big file with -b option, it could take a long
  time(e.g. more than 20 minutes) to return but no data
  movement is seen between disks. This is because
  the big file is already balanced.
  

Problem conclusion

• Benefits of the solution:
  Shorten the running time of the mmrestripefile
  command if no repair work is needed.
  
  Work around:
  No
  
  Problem trigger:
  Using mmrestripefile to rebalance big files.
  
  Symptom:
  Performance impact
  
  Platforms affected:
  All Operating Systems
  
  Functional Area affected:
  mmrestripefile command
  
  Customer Impact:
  Suggested
  

Temporary fix

Comments

APAR Information

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

  IJ29917

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

  412AC3Ÿ

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels