Skip to main content
NetApp Knowledge Base

SVM storage limit modification fails with error :Vserver storage limit is less than already allocated

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

Applies to

  • ONTAP 9

Issue

  • When attempting to modify the storage limit on an existing SVM (vserver), the following error is observed, even though the actual allocated space is much lower than the requested limit:

cluster1::> vserver modify -vserver svm1 -storage-limit 30TB
Error: command failed: Vserver storage limit ("30TB") is less than already allocated ("900.5TB").

  • However, volume show output indicates that the total allocated space on all volumes is less than 20TB.

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.