Volume not tiering data with aborted-nospace error
Applies to
- ONTAP 9.9.1+
- FabricPool
- MetroCluster
- unmirrored aggregate
Issue
- After an update to ONTAP 9.9.1+, data in unmirrored MetroCluster aggregates are no longer tiering to the FabricPool.
- Tiering for the volumes is in a
ready
state and the previous run aborts with theaborted-nospace
error:
Cluster01::> set advanced
Cluster01::*> vol object-store tiering show -volume vol1 -vserver SVM1
Vserver: SVM1
Volume: vol1
Node Name: Node-04
Volume DSID: 3089
Aggregate Name: aggr2
State: ready
Previous Run Status: aborted-nospace
Aborted Exception Status: -
Time Scanner Last Finished: Tue Jun 21 11:25:14 2022
Scanner Percent Complete: -
Scanner Current VBN: -
Scanner Max VBNs: -
Time Waiting Scan will be scheduled: -
Tiering Policy: auto
Estimated Space Needed for Promotion: -
Time Scan Started: -
Cloud Retrieval Policy: default
Elapsed Time Scanner Ran: -
Time of Last Space Related Error: -
Scheduling class of scanner: -