The closest feature which can be done with current implementation is dropping tail of the journal to rollback state of LSFS device to the selected snapshot. We'll bring it to UI. But it is limited with one device and one path, not suitable to scenarios where several devices are based on single "...

Yes, that's right!
You can check StarWind log file for the string "disk is SSD" near the records about initialization of ImageFile device.

What ESXi version are you using?
Does datastore rescan or "refresh capacity information" change anything?

I had doubts about need of ESXi reboot for refreshing device info. It works with V8R4 from August 2016. We have checked with 3-node ESXi 6.5 cluster. Option has been added to both StarWind HA nodes: edit StarWind.cfg, restart StarWind service, wait for HA sync, repeat for the second node. Then all t...

Let us check this in our lab. vSphere don't like to update information about "known" devices on fly. For example, it updates information about supported commands only after restart of ESX server.

It can be done in the current version of StarWind by adding "SolidStateDrive" parameter to device string in config file StarWind.cfg: Start WordPad with administrator privileges, open StarWind.cfg file, find <device... record by value of device name or .swdsk file parameter. Add SolidState...

This issue occurs when source image is thin-provisioned. V2V Converter checks free disk space using full size of virtual disk. We are fixing this behavior in upcoming update of V2V Converter. Unfortunately, there is no workaround except using destination path with free space large enough to pass the...

Yes, UNMAP functionality for LSFS is being tested now. We are planning to release it in March.

Just curious if there are statistics available anywhere in the product (or PerfMon) for things such as cache hit ratios, etc..., or if that is still on the roadmap. We are working on this functionality right now, it is planned for release on September. Counters are: - Cache usage percent (used cach...

Thank you!
We will get it to the correct state.
Unfortunately, updates for StarWindX module went out of scope for this release update.

Unfortunately, StarWind Intiator product is EOL-ed, and is not supported anymore.

It is possible, that initiator is not compatible with Windows 8, as it use some kernel-level functionality. Try to run it from Windows 7, it may solve the issue.

Most of prameters, that are accessible trough IDevice.GetPropertyValue(), are internal, and not intended for external use. We will add "State" parameter to device properties in later update. Current list of values for State field is as follows: 0 - DeviceActive, 1 - DeviceNonActive, 2 - De...

Thank you very much for comprehensive feedback!
Could you please send us log file from StarWind service for the session that finished with crash? Or even all the /logs directory in zip-archive, if it is OK for you.

Dear Beta-team members, we have reworked defragmentation process in LSFS devices: - Defragmentation algorithms changed to handle data growth better. - Defragmentation can be started manually with context menu command of LSFS device. Initial implementation of defragmentation algorithm had too high th...

It's a diagnostic message, nothing special.
Service kernel checks disk if it supports WRITE_SAME command, disk says it doesn't support this command.
In a result service kernel processes these commands itself.

Yes. This setting makes LUN read only for all initiators.