On 19/09/2020 05:29, jdd@dodin.org wrote:
Le 19/09/2020 à 09:00, Carlos E. R. a écrit :
But I do not see a description of the algorithm.
IMHO pretty simple. Fill the disk with numbered files. Read to see if the numbers are there...
Simple but smart. Write 1 megabyte numbered files. Along the way it tests the writeability/readback looking for, not only the 'high water mark' that is the drive's capacity, but any errors along the way. Yes, I suppose you could use a script that does a stepwise DD+offset. Yes I suppose using DD you could have input files with different byte patterns and try each of them before moving onto the next bock on the drive. Yes you could prove just how creative a shell programmer you are. Yes, you set up something like this for one of the 256G devices I have. It might be slower than F3, which took almost 3 days to scan and prove one of my 256G devices. OK, so that chip wasn't fast, but for my tablet, books and movies, it was fast enough. It also, it seems, was fast enough for video recording on my camera which surprised me. But then it's an older, smaller camera; a modern HD 4/8K 10-bit camera has a greater demand! But it's not as if I'm vblogging or making short movies for YouTube. The bottom line here is that I ALWAYS test my 'portable storage devices' beforehand. I do not want to find out they were failures or 'not as advertised' AFTER I've used them to take unrepeatable photographs. -- All tyranny needs to gain a foothold is for people of good conscience to remain silent. -- Thomas Jefferson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org