Skip to main content
NetApp Knowledge Base

Disk Reconstruction Stuck at 0 due to Job having future Queue Time

Views:
67
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Issue

  • After initial cluster setup, disk reconstruction jobs are stuck at 0%. Other system jobs also show queue times set in the future, even after NTP is configured correctly.
  • The system logs and job output show:

Cluster::*> date
Node      Date                     Time zone
--------- ------------------------ -------------------------
node1   Sat Oct 03 02:18:02 2025    Asia/Kolkata
node2   Sat Oct 03 02:18:02 2025    Asia/Kolkata

 
Cluster::> job show-fields name,queue-time
id  vserver  name                     queue-time
---------------------------------------------------------
1   Cluster  DiskStatisticsCollector  10/04 01:00:02  --------> Job having future time
3   Cluster  GetObjectStoreServer     10/04 01:00:07
 
  • Disk reconstruction does not progress.
  • The system time was previously set to a future date and later corrected.
  • NTP is now configured, but jobs still retain the original (future) queue time.

 

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.