Skip to main content
NetApp Knowledge Base

Why is a thick provisioned ONTAP LUN larger than its parent volume?

Views:
323
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9

Answer

This is expected behavior when the following environmental conditions are met:
  1. A space-reserved LUN in a volume with a space guarantee of VOLUME
  2. The fractional reserve on the volume is set to 0
  3. The volume has storage efficiency features (deduplication) enabled
  4. The LUN has space reservation honored = false

Additional Information

To check  Space Reservation and Space Reservation Honored please run the following command:

cluster1::> lun show -vserver vs1 -path /vol/vol1/lun1 -instance
              Vserver Name: vs1
                  LUN Path: /vol/vol1/lun1
               Volume Name: vol1
                Qtree Name: ""
                  LUN Name: lun1
                  LUN Size: 10MB
                   OS Type: linux
         Space Reservation: enabled
             Serial Number: xxxxxxxx
       Serial Number (Hex): xxxxxxxx
                   Comment: new comment
Space Reservations Honored: false
 ...
 
For more information regarding NetApp's best practice for LUN configuration please review, What is the proper configuration for a volume containing a LUN?
 
There is a current request for enhancement with our Engineering team to prevent this issue in future ONTAP releases.
 
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.