Skip to main content
NetApp Knowledge Base

Aggregate metadata has exploded in size, causing aggregate to become full

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

Applies to

  • ONTAP 9
  • FAS/AFF

Issue

  • Multiple volume moves were running on the aggregate[within the same aggregate] to encrypt the volume.
  • Aggregate metadata size increased, causing the aggregate to become full.

monitor_volume_full object_type="Aggregate" name="aggr1" app="" vserver_uuid="" percent_full_blocks="99" percent_full_inodes="0"   <<<<<
wafl_vvol_xfer_nospacedestErr vol="temp__1087__10261__XXXXX" app="" volident="@vserver:a078084a-XXXX-XXXX-XXXX-d039XXXXXe85" aggr="aggr1"

wafl_vol_full type="aggregate" owner="" vol="aggr1" app="" volident="" requested="24.0KB" available="16.0KB"

  • Datastores mapped to the volumes in the aggregate went into read-only mode.  

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.