More information about planning your system according to our best practices can be found here:
https://www.starwindsoftware.com/starwi ... ces-manual

Valid point, Darklight, thank you!

Hi everybody,

Basically, StarWind Virtual SAN should work flawlessly on default settings. Tweaking your network adapter is reasonable only in case of having stability or performance issues.

Hi, guys! Still having issues? Anything else I can help you with?

Lohelle, DarkLight - thank you very much for your contribution.

Anything else I can help here with?

We usually recommend using IOMeter for performance testing, since it gives more reliable results on our experience. Please find a generic benchmarking guide: https://www.starwindsoftware.com/starwind-benchmarking-best-practice-manual And recommended IOMeter set of tests: https://knowledgebase.starwi...

Hi guys, thank you very much for your contribution.

I have to admit that L2 cache still has some minor performance issues on some specific hardware configurations that will be improved in an upcoming build expected by the end of the year.

To be able to use internal SSD drives on your ESX hosts, you have to install StarWind Virtual SAN inside VM's on each of ESX hosts and then mirror these. This is generally called VMWare Hyper-Converged Scenario.

Darklight already provided a link to a proper guide, thank you!

Hi guys,

LSFS-growth issue was fixed in the latest version (Build 8730) however, LSFS devices created in previous versions might still be improper. If this is your case, please do not hesitate to recreate such devices from scratch using the newest StarWind Virtual SAN version.

Please find some more information about how to set up XenServer with StarWind Virtual SAN in the following guide:
https://www.starwindsoftware.com/starwi ... erver-pool

Darklight, thank you very much for you contribution on the case.

2 All Take a look at mpclaim /? command.

Hello Clickmaster,

A few questions to be able to find out the root cause of your issue:
1) Have you created any snapshots on the impacted volume?
2) Have you moved any files to the newly-created / still growing device after the update?

Thank you.

Anything here left unresolved that I could help with?

Thanks Darklight for making an awesome contribution to our community.

We have noticed some issues with L2 cache performance on fast and very fast (SAS) spindle drives. Right now we are making some further testing and improvements. I will keep you updated.

LSFS (both standalone and HA) is proven to be stable and ready for production. Enjoy!