Skip to main content
NetApp Knowledge Base

FlexGroup constituents increasing in size after volume expansion

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

Applies to

  • ONTAP 9
  • FlexGroup

Issue

  • A FlexGroup is expanded in size using command volume expand
  • ONTAP automatically creates new constituents on the aggregates designated in the volume expand command above
  • The number of constituents created depends on the scale of the expansion. In some scenarios, the total number of constituents in the FlexGroup can double in size as a result
  • Following the expansion, it is observed that ONTAP is increasing the size of the original constituents which is resulting in out of space warnings on the parent aggregates

fg.member.elastic.sizing:notice]: Constituent 2067 in FlexGroup FlexGroup1 was resized from 22109774036 to 22109086003.

monitor.volume.nearlyFull:error]: Aggregate aggr1 is nearly full (using or reserving 93%% of space and 0%% of inodes).

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.