Finished installing the new (fixed) starwind server using
https://tmplink.starwind.com/StarWindBeta.exe whith the following results:
The option to (manually) trigger defragmentation of the LSFS device is now available. Clicked that option and my 5TB datastore went from 7.65TB to 4.61TB size on disk in a couple hours, but....
- Statistics about device fragmentation status are somewhat crazy, I think:
User data is said to be in the order of Petabytes!!!
Fragmented Data is only 50 GB, however recovered more than 3TB of disk space after defragmentation.
Fragmentation Percent is stucked at 100% even after defragmentation has already occurred.
- Mounting time is still sky high: 5 hours in my case mounting a 5TB device.
Im not yet been able to check the integrity of the data inside the datastore because Starwind service now crushes ramdonly with Event ID 1000 due to failure on module ntdll.dll....Dont know if this is a driver/hardware/software(starwind) malfunction. Never happened before with the previous versions of Starwind/HW. Such kind of behavior could be caused sometimes by resource exhaustion (high memory consumption), which I dont think is the case...
What would be really desirable in my opinion:
- Autodefragmentation should (actually) trigger when I/O demand is low.
- It should be possible to execute manual defragmentation (with high priority) as a time-windowed scheduled task with an start and end time.
- Mounting time is too high. Still an issue to work on.
Ill keep testing.....
)... I´ll be back to LSFS in production after you release the bugfixed RTM version and let you know....