Skip to main content
NetApp Knowledge Base

Unable to reclaim space from a thin provision volume

Views:
1,386
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

 

Applies to

E-Series Controller Firmware

Answer

When trying to reclaim deleted blocks or space from E-Series thin provisioned volume, space is not reclaimed and the host SCSI UNMAP operation returns with an error.

SCSI UNMAP was first introduced in E-Series controller firmware starting 8.25.05, which means deleted blocks will not be reclaimed on a volume that was created prior to this release. Once the controller firmware level support this feature, SCSI UNMAP should be enabled on each thin-provisioned volume created prior to 8.25.05. See the following links to enable this feature according to the host OS:

  • FA24: What are Windows host operating system considerations when using SCSI UNMAP with E-Series thin volumes?

  • FA25: What are VMware considerations when using SCSI UNMAP with E-Series thin volumes?

  • FA26: What are Linux host operating system considerations when using SCSI UNMAP with E-Series thin volumes?

Some platforms cannot be upgraded beyond 8.20 and therefore SCSI UNMAP is not supported on these platforms. From customer product communication  CPC-1705-03:
"SANtricity OS 8.20 is at the end of engineering support as of May 1, 2017. The E2600, E5400, and EF540 systems cannot be upgraded beyond SANtricity OS 8.20."

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.