Skip to main content
NetApp Knowledge Base

Default tree rules auto-created even specific qtree name has been specified

Views:
78
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP 9

Issue

ONTAP API online documentation page said that:
qtree.name - Qtree for which to create the rule. For default tree rules, the qtree name must be specified as "".
 
However, while creating quota policy rule by REST API, the default rule also gets auto-created unexpectedly even a specific qtree name has been specified.
 
The operation log details are as below.
========================
cluster1::> volume quota policy rule show -volume vol1
There are no entries matching your query.
 
 
----- body -----
{
"qtree": {
"name":"qtree1"
},
"space": {
"hard_limit": "104857600",
"soft_limit": "5242880"
},
"svm": {
"name": "svm1"
},
 
"type": "tree",
"volume": {
"name": "qtree1"
}
}
----------------
 
cluster1::> volume quota policy rule show -volume vol1
Vserver: svm1              Policy: default           Volume: vol1
 

                                               Soft             Soft
                         User         Disk     Disk   Files    Files
Type   Target    Qtree   Mapping     Limit    Limit   Limit    Limit  Threshold
-----  --------  ------- -------  --------  -------  ------  -------  --------
tree   ""      ""      -                -        -       -        -          -  <----default rule is created unexpected
tree   qtree1  ""      -            100MB      5MB       -        -          -
2 entries were displayed.

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.