Closed git70 closed 4 years ago
The explanation of why the functionality is now there is here[1]. Its been years since i last investigated it so perhaps its time to revisit the functionality.
The problem i saw was that a burst of fast writes will happen reducing estimated time remaining by a lot followed by prolonged stalling increasing estimated time remaining. The ETA was fluctuating too much for my liking.
It seemed to me that continuous writing block by block has a constant speed :( I don't know if it makes sense, but you can check how it is solved in Timeshift, FreeFileSync and VeraCrypt. They also have fluctuations, but it's better than no information...
Done and the binary git package has the functionality.
Looks wonderful :) I will wait with the update until you look at error 132
When writing random data to a file or device, it would be nice to see the estimated end time. Particularly useful for large volumes.