Skip to main content
NetApp Knowledge Base

FabricPool tiering has aborted-defrag-throttled status for some volumes

  1. Last updated
  2. Save as PDF
Views:
323
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • FabricPool

Issue

Some volumes have the aborted-defrag-throttled when checking their tiering status:

cluster1::> set advanced

cluster1::*> volume object-store tiering show

                                                  Policy
Vserver Volume Aggregate State   %Complete  Tiering   CloudRetrieve LastStatus
------- ------ --------- -------- --------- --------- ------------- ----------
svm1    proj1  aggr1_cluster1 active      - auto      default       completed

        proj2  aggr1_cluster1 waiting     - auto      default       completed

        proj3  aggr1_cluster1 waiting     - snapshot-only default   completed

        proj4  aggr2_cluster1 ready       - all       default       aborted-defrag-throttled

        proj5  aggr2_cluster1 ready       - auto      default       aborted-defrag-throttled

        svm1_root aggr1_cluster1 waiting  - none      default       completed

6 entries were displayed.

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.