Good

"native unmap" would problably only work on LUNs directly attached (ISCSI in OS) to guest VMs running Server 2012 > on vSphere, and not on disks on VMFS.

Hyper-V 2012 will allow guests to "send" unmap all the way I think.

Or am I wrong?

A little followup I created a 100GB LSFS LUN and created a VMFS datastore. I created a 50GB thick provisioned (lazy zeroed) on a VM (on that datastore) This is not using any space on the SW-box, but it uses 50GB on the vSphere datastore (as expected) I copied 40GB of data to the VM disk. I see many ...

My observations testing v8 RC - Deduplication is CPU intensive. I observed 50% cpu-load on my single i3 Xeon 2.5 GHz (2-core 2.5GHz + HT) during 50MB/s writes Is it not possible to adjust dedupe block size any more? Found only checkbox for auto-defrag and dedupe on/off in LSFS options. - UNMAP works...

This was standard image file devices (non-HA). I created the targets on the latest v6-release, then upgraded to Beta1 (success) and finally to beta2.

I do not have any logs now. Sorry.. :\

When I upgraded from beta1 to beta2 ESXi did not reconnect (even after resync). I could select "add storage" and choose "keep signature" to get access to my ISO-datastore, but this did not work for my VM datastore. Add storage + new signature worked. I then had to register all VM...

I also had to add storage and NOT signature after upgrade to beta2 (might bee npossible to remove VM's, rescan and then register VM's again.

~ # esxcli storage core device vaai status get -d eui.60eb6f9cc7cf59b6
eui.60eb6f9cc7cf59b6
VAAI Plugin Name:
ATS Status: supported
Clone Status: supported
Zero Status: supported
Delete Status: unsupported

ESX5.5 and beta release 8.0.6049
Delete Status still listed as unsupported

I understand that sending info about free space etc is some work, but you could maybe REPORT the storage as Thin Provisioned to the client.

It would also be great if you could make it possible to report storage as SSD or not. This is important for vSphere at least.

Please remember to fix that to (unmap). Also, send thin provisioning info to vSphere.

Remember to also fix the issue with L2-cache always stored on the same location as the main disk file. If I remember right the main storage is also always saved in storage pool location (even if you specify other location). Only tried image-file setting.

I have tried full copy / cloning. That works. I have not had time to do extensive testing yet.

hope this is fixed (delete support) Tested on ESXi 5.1 and 5.5 Command: esxcli storage core device vaai status get Output: eui.3c750b4679ddb0b1 VAAI Plugin Name: ATS Status: supported Clone Status: supported Zero Status: supported Delete Status: unsupported eui.689cf0483bc0b9f8 VAAI Plugin Name: ATS...

This is not normal. Is there any chance we'd see a screenshot or a StarWind log for the failed sequence? Could someone point me in the right direction as far as creating LSFS volumes properly. I've tried many different methods through the GUI, and they all result in "Device state: Failed!"...

esxi 5.1 host Doing some v8 tests. esxcli storage core device vaai status get -d eui.7943d98a2b309843 eui.7943d98a2b309843 VAAI Plugin Name: ATS Status: supported Clone Status: supported Zero Status: supported Delete Status: unsupported Strange. Delete Status = unsupported, but it is enabled on the ...

It looks like the L2-cache is always created in the storage-pool location, and not in the location selected in the wizard.