Skip to main content
NetApp Knowledge Base

File's time stamp is incorrectly set to future time

Last Updated:

Applies to

  • ONTAP 9
  • CIFS
  • NFS


  • The inode subsystem might experience high memory usage,
  • System slowdown and unresponsive behavior
  • Controller disruption in some extreme cases
  • Sporadic file timestamps are incorrectly set to future time


Check file's time stamp after file creation

% date ; ls -l ; ls -l --full-time
Fri Jan 15 16:58:18 JST 2020
total 12
drwxr-xr-x 2 xxxxx xxxxx 4096 Jan 11 17:51 test/
drwxr-xr-x 2 xxxxx xxxxx 4096 Jan 13 01:46 test2/
drwxr-xr-x 2 xxxxx xxxxx 4096 Jan 14 19:59 test3/
-rw-r--r-- 1 xxxxx xxxxx    0 Jan 15 17:51 testfile



Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device