Skip to main content
NetApp Knowledge Base

Unexpected Space Overhead in StorageGRID

  1. Last updated
  2. Save as PDF
Views:
11
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • StorageGRID
  • EC 2+1
  • Fabric Pool
  • Balanced Ingest Behavior

clipboard_16a13d22-5af9-4271-8128-6a55efb9e21c.png

clipboard_37c75ca0-8be4-42a8-b050-5911fd0ac23c.png

Answer

  • StorageGRID is configured with ILM (Information Lifecycle Management) rules to use EC2+1 erasure coding for objects larger than 200KB. However, when the grid nodes do not have enough space to meet the ILM requirement, the system could not satisfy the EC2+1 rule due to lack of available space and eligible nodes.
  • As a result, the objects started ingesting as dual commit  which store objects as two replicated copies. This replicated copy policy results in a 100% space overhead (i.e., every object is stored twice).
  • This behavior is designed to ensure data durability when the preferred erasure coding policy cannot be met. 

clipboard_9e3d0eef-4509-45aa-aa1c-0d5a51f8b710.png

Additional Information

additionalInformation_text
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.