May I ask you if you have created new devices with 7774 build, or you have created them on previous build, and ran an update after?

Usually we recommend the L2 Flash cache size would be ~10% of the HA storage size (i.e. 100Gb for 1TB).

StarWind functioned well in such config in our lab. May I ask you to provide me with next information: · StarWind service logs at the time of the issue from all problematic SAN boxes · Windows Application and System logs (in *.csv format) on the time of the issue from all problematic SAN boxes · Det...

That sounds like a good plan!
You may consider using part of Flash as L2 cache actually.

That is really weird and unexpected. Would you be so kind to drop quick email to support@ and one of our engineers will gladly jump on the remote session with you to get to the botom of the issue. Please don`t forget to out the link to this conversation to your email. Also I would highly appreciate ...

quick double-check - so you are running with All-Flash, correct?

That's true - just tested in my lab
Thanks! I`ll pass this along to dev guys.

Hi again!
Any chance you could upload the logs and share the download link with us?

May I ask you what are hte
1. Ammount of data stored on the LSFS device
2. Total disk space that LSFS currently takes?

Rich now it should take not more then 3times more from the amount of data.

Thanks for the heads up!

OK, got it. Lets continue the conversation there.

We will prepare the list within a week.

Hi! Sorry to hear that you are in trouble.
1. Can you double check if you have followed out manuals precisely?
2. Have you checked the logs?

@fbifido that is not an option - v6 DD hadn`t space reclaim feature @RGijsen I got where you come from. The DD of StarWind is aimed to save the diskspace while protecting the data. It is the bunch of solution that comes in one package. The perfect design for us here is cheap SATAs with high capacity...

We did fixed that, but the build with fixes is in QA dep right now, and it is on final testing stage.