<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861876#M182296</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How to monitor the progress of space recycling?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Aug 2019 13:23:51 GMT</pubDate>
    <dc:creator>frecol</dc:creator>
    <dc:date>2019-08-14T13:23:51Z</dc:date>
    <item>
      <title>/vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861874#M182294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;/vmfs/volumes # esxcli storage vmfs unmap -l UNITY027_SSD_20TB&lt;/P&gt;&lt;P&gt;Initializing async unmap failed on volume 5b2d478a-96343bdf-2bc6-0025b500001f :&lt;STRONG&gt; Device or resource busy&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;how to resove&amp;nbsp; thanks?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 03:26:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861874#M182294</guid>
      <dc:creator>frecol</dc:creator>
      <dc:date>2019-08-14T03:26:28Z</dc:date>
    </item>
    <item>
      <title>Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861875#M182295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you should check those 2 links about lockfiles :&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/1008728?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1" title="https://kb.vmware.com/s/article/1008728?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1"&gt;VMware Knowledge Base&lt;/A&gt; (&lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:134;a" style="font-size: 10pt;"&gt;Manipulating a file on a Datastore fails with the error: device or resource busy / file is locked (1008728)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/10051?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1" title="https://kb.vmware.com/s/article/10051?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1"&gt;VMware Knowledge Base&lt;/A&gt;​ &lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:174;a"&gt;(&lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:174;a"&gt;Investigating virtual machine file locks on ESXi (10051))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Else, have you checked if the volume is in use ? If you can , temporarly remove any links between your VMs and the datastore then unmap -l the datastore then rebuild links.&lt;/P&gt;&lt;P&gt;If you use HA check if your datastore is not used for heartbeat (let me know if you need help)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 09:25:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861875#M182295</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T09:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861876#M182296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How to monitor the progress of space recycling?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 13:23:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861876#M182296</guid>
      <dc:creator>frecol</dc:creator>
      <dc:date>2019-08-14T13:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861877#M182297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think you'll be able to monitor it only with esxcli command...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone succeed to automate it using PowerCLI , you can monitor the action using PowerCLI so :&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/" title="http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/"&gt;http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Else, take a look at the step 7 in this link, &lt;A href="https://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html" title="https://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html"&gt;VAAI Thin Provisioning Block Reclaim/UNMAP In Action - VMware vSphere Blog&lt;/A&gt; &lt;/P&gt;&lt;P&gt;It explain you how you can "monitor" the process via ESXTOP command (you can see the quantity of MB deleted)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i didn't find any tools or cli to monitor the action as you can monitor the progress of anything in vCenter, sorry..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 13:42:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861877#M182297</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T13:42:21Z</dc:date>
    </item>
  </channel>
</rss>

