Skip to main content
NetApp Knowledge Base

Devices backing volume do not support UNMAP

  1. Last updated
  2. Save as PDF
Views:
7,257
Visibility:
Public
Votes:
9
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • VMware ESXi 5.x and later
  • ONTAP9
  • ONTAP 8.1 and later

Issue

  • An error occurs when performing a ESXi UNMAP from the ESX CLI:

[root@esxi:~] esxcli storage vmfs unmap -l Datastore_Name 
Devices backing volume <uuid> do not support UNMAP

  • VAAI status states:

[root@esxi:~] esxcli storage core device vaai status get -d naa.6006016094602800e07xxxxxx
naa.6006016094602800e07xxxxxx
    VAAI Plugin Name: VMW_VAAIP_NETAPP
    ATS Status: supported
    Clone Status: supported
    Zero Status: supported
    Delete Status: unsupported

  • In ONTAP, space allocation for the LUN is disabled:

::> lun show -vserver <vserver_name> -path <lun_path> -instance

                  Vserver Name: vserver1
                      LUN Path: /vol/somevol/thinlun
                   Volume Name: somevol
                    Qtree Name: ""
                      LUN Name: thinlun
                      LUN Size: 10GB
                       OS Type: linux
             Space Reservation: disabled
                           [...]
              Space Allocation: disabled

 

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.