IJ53548: MISSING CHECK FOR SETTING TIMESTAMPS BEFORE EPOCH

APAR status

• Closed as program error.

Error description

• Attempting to set a timestamp in GPFS to a time before Jan 1
  1970  results in an unexpected timestamp being stored. GPFS
  currently  stores timestamps as a 32bit unsigned integer, and
  thus can store  timestamps from Jan 1 1970 00:00:00 UTC to 7
  February 2106 at  06:28:15 UTC. Setting a timestamp before 1970
  was silently accepted.
  

Local fix

• Avoid setting timestamps outside the supported range in GPFS.
  

Problem summary

• Attempting to set a timestamp in GPFS to a time before Jan 1
  1970  results in an unexpected timestamp being stored. GPFS
  currently  stores timestamps as a 32bit unsigned integer, and
  thus can store  timestamps from Jan 1 1970 00:00:00 UTC to 7
  February 2106 at  06:28:15 UTC. Setting a timestamp before 1970
  was silently accepted.
  

Problem conclusion

• This problem is fixed in 5.2.2.1
  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:
  Attempting to set timestamps before 1970 is rejected with an
  error.
  
  Work Around:
  Avoid setting timestamps outside the supported range in GPFS.
  
  Problem trigger:
  Attempt to set timestamp on a GPFS inode before 1970, e.g.:   
  touch -m -t 196001010000 testfile
  
  Symptom:
  Unexpected Results/Behavior
  
  Platforms affected:
  ALL Linux OS 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