IJ27264: NSD TYPE MISMATCH WHEN ADDING A NSD TO A FILESYSTEM

APAR status

• Closed as program error.

Error description

• The check for mismatched NSDs in a storage pool may
  fail if the regular NSD was created with a pool
  designation different than the one used in the
  mmadddisk stanza file.
  

Local fix

• Use the --force-nsd-mismatch option
  

Problem summary

• The check for mismatched NSDs in a storage pool may
  fail if the regular NSD was created with a pool
  designation different than the one used in the
  mmadddisk stanza file.
  

Problem conclusion

• Benefits of the solution:
  Fixed code so that regular NSDs can be added
  to filesystems contained in vdisk-based NSDs.
  Work around:
  Use the --force-nsd-mismatch option
  Problem trigger:
  Adding regular NSDs to a filesystem which contains
  vdisk-based NSDs into a new pool which does not
  match the pool used when the NSD was created.
  Symptom:
  Error output/message
  Platforms affected: All
  Functional Area affected: ESS/GNR
  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