Hi Hiroki,  When used with ESX, ScaleIO can indeed use a local datastore. Here are the notes on this from the 2.0.1.x Deploy Guide:  VMDK A new datastore is created, with a VMDK, and the VMDK is added to the SVM. ScaleIO requires thick provisioning, so this process can take a long time.  In almost all cases, RDM is the preferred method to add physical devices. Use the VMDK method only in the following scenarios: – The physical device does not support RDM. – The device already has a datastore, and the device isn’t being completely used. The excess area that is not already being used will be added as a ScaleIO device.  One note of caution here. If you use the local datastore as an SDS device on which the SVM resides, the SVM will be competing for disk resources while also trying to serve the needs of the cluster. This is definitely not recommended and should only be done in a test environment, as there will be performance and stability considerations with that setup.  Hope that helps, RIck
Hello. Thank for your attention.  I'm using ESXi 5.5. And I'll install ScaleIO on local datastore. In this case, Can ScaleIO use datastore what installed itself ?  ------------------------------------ ESXi 　∟datastore1　←install ScaleIO 　∟datastore2 ------------------------------------  In other words, Can SDS use both datastore1 and datastore2 as storage pool ?  Best regards,
Can ScaleIO use datastore what installed itself ?