I had a volume set to thin on my EQL 6210XS and got a warning about used space over 90%. In VMware the datastore was reporting about 1TB free (out of 3TB) so a pretty big mismatch. It seems like the EQL arrays don't support auto unmap on 6.5 with VMFS6 so I ran the manual unmap (I used a host in maintenance mode in the cluster from which to run the command). Now the EQL is looking better (well below 90%) but my free space in vmware has gone down which makes no sense to me.

If I sum up the used space of all the vms I should be left with a little more than 1TB free space but after the unmap I lost a good 250-300GB of space it seems. I did notice there an leftover .asyncUnmapFile at the root of the datastore but I'm not sure if I can safely delete it (when I google .asyncUnmapFile i get one solution 3020 from vmware but it says the article is not applicable since I'm on 6.5 and VMFS6). Part of the vmkernel.log is shown below when the unmap ends.

Anyone know what's going on or do I need to call VMware/EQL support?

2017-09-01T21:20:36.015Z cpu52:68605 opID=775d14d4)WARNING: Res3: 4314: [type 1] resource 64 (cluster 1309) on volume labeled 'MyVol' already freed by another host: This may be a non-issue
2017-09-01T21:20:36.216Z cpu52:68605 opID=775d14d4)WARNING: Res3: 4314: [type 1] resource 64 (cluster 1309) on volume labeled 'MyVol' already freed by another host: This may be a non-issue
2017-09-01T21:20:36.428Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.463Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.497Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.531Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.570Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.617Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.662Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.711Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.746Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.785Z cpu52:68605 opID=775d14d4)Fil3: 14292: MyVol: Converting 0 LFBs to SFB clusters: Success
2017-09-01T21:20:36.789Z cpu52:68605 opID=775d14d4)Fil3: 8210: Max no space retries (10) exceeded for caller Fil3_SetFileLength (status 'No space left on device')
2017-09-01T21:20:36.799Z cpu52:68605 opID=775d14d4)WARNING: Res3: 4314: [type 1] resource 64 (cluster 1309) on volume labeled 'MyVol' already freed by another host: This may be a non-issue
2017-09-01T21:20:36.811Z cpu52:68605 opID=775d14d4)WARNING: Res3: 4314: [type 1] resource 64 (cluster 1309) on volume labeled 'MyVol' already freed by another host: This may be a non-issue
2017-09-01T21:20:36.818Z cpu52:68605 opID=775d14d4)WARNING: Res3: 4314: [type 1] resource 64 (cluster 1309) on volume labeled 'MyVol' already freed by another host: This may be a non-issue
2017-09-01T21:20:36.818Z cpu52:68605 opID=775d14d4)Fil3: 7022: Truncating failed: Not found