Search the Community
Showing results for tags 'measure'.
So I've recently switched from a desktop setup with 3x 8TB HDDs storage and 1x 128GB SSD cache, to a laptop + eGPU setup with the same four drives in an external enclosure connected to the eGPU. Laptop is connected to eGPU through a single Thunderbolt 3 cable for charging and data, and the enclosure is connected to the USB-C port on the graphics card. Every time I shut down and turn on my laptop, or if I disconnect the TB3 cable and plug it back in (so basically every day after coming home from work), Drivepool starts measuring my entire 22TB pool from scratch, so I just have to wait
There is a couple of issues and questions about measuring. Why it is not optimized / cached / smarter? Case 1: If there is a pool of 2 or more drives and one is disconnected for whatever reason - once the drive is back entire pool is measured. If that is large, cloud based pool with a lot of small files - a short interruption in connectivity triggers hours of measuring. Would that be possible to cache results of previous measure run and measure only the drive that was reconnected? Case 2: Four cloud based drives CLD1, CLD2, CLD3 and CLD4 are coupled in two