IJ34331: MMCHMGR COMMAND COULD FAIL TO ASSIGN A NEW FILE SYSTEM MANAGER WITH "NO LOG AVAILABLE" ERROR.

APAR status

• Closed as program error.

Error description

• When the mmchmgr command is used to assign
  a new file system manager, it could fail
  with "No log available" message after the current
  file system panics with "No log available" error.   This
  can happen if file system is not externally
  mounted on any node.
  

Local fix

• Mount the file system before issuing the mmchmgr
  command
  

Problem summary

• When the mmchmgr command is used to assign
  a new file system manager, it could fail
  with "No log available" message after the current
  file system panics with "No log available" error.   This
  can happen if file system is not externally
  mounted on any node.
  

Problem conclusion

• This problem is fixed in 5.0.5  PTF 10
  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:
  Avoid unexpected "No log available" error
  when changing the file system manager with
  the mmchmgr command
  
  Work Around:
  Mount the file system before issuing the mmchmgr
  command
  
  Problem trigger:
  Using the mmchmgr command to assign a
  new file system manager
  
  Symptom:
  Error output/message
  
  Platforms affected:
  ALL Operating System environments
  
  Functional Area affected:
  All Scale Users
  
  Customer Impact:
  Suggested
  

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