I have the same issue. They are orphaned log files that are not removed during defragmentation and after service restart they are not automatically purged. Use the following at your own risk, but I get around it by restarting the starwind service, waiting for full device mount and sync to complete (...

Ok thanks for the tip and schedule update Oleg.

Kevin

That's great news that you found the problem Oleg!

When you say to run flushcacheall.ps1 before I restart the service - is that necessary even though I have only write-through caches in vsan?

Any idea when the next build will be released?

Thanks,
Kevin

Futher to my post in Blowfish-IT's thread regarding Starwind consuming large amounts of disk I/O related to reading (little to no write activity) LSFS log files even with no workload, I noticed that the defragmentation levels reported by the console seem quite off (>900%?) and the amount of physical...

While I haven't experienced complete failure of the storage system as indicated by Blowfish-IT, I have noticed that both nodes in my HA setup running under build 11818 for the last month continuously consume around 200-500MB/s heavily skewed to reading LSFS device files as you can see from the scree...

Following Vladcat's note that the 2TB version worked fine, I returned the 3TB drive and picked up a 2TB model. I can confirm that one works fine so the issue is definitely related to capacity. My issue is resolved, so no point for me to open a ticket, but hopefully the info provided will help you tr...

Hi Dmitry, Same version as Vladcat 8.0 build 8730. All plugins are 8.0, but there is also a 2nd deduplicated disk v5.8 plugin. (Both nodes are the same) I have the same errors in the starwind log when the Seagate backup disk is attached to the USB port: code 1117, and readcapacity16 failed with &quo...

I have this exact problem as well on both nodes of my 2-node cluster although with Seagate 3TB USB drive. Any update would be appreciated.