Re: Overcoming USB copy delay
Posted: Sat Sep 05, 2020 3:31 am
Hi Flash, since I'm not duplicating right now the conditions resulting in file corruptions, I'm trying to remember the circumstances. Okay here's one for sure: I have had situations in the past where I saved a file to USB, and the save dialog closes before the file transfer is finished. This was evidenced on the thumb drive via the LED (if it has one). On some thumbdrives I have it flashes while a transfer is taking place. With those it was possible to see that a transfer was still taking place, sometimes long after the save dialog closes.
Also the OP talked about unmounting under pupmode5 where the automatic flush transfer appeared to finish before it actually had. This is the same problematic process.
I think I have also had situations in the past when graphically unmounting a USB drive (by left clicking the drive "dot") when the "dot" or light or X on the drive icon went out before the transfer was finished, and then I pulled the USB stick out before it was actually ready.
Thinking about why this could be happening, I'm wondering if there is some kind of USB cache or buffer that these indicators are reacting to. They finish sending data to the cache, signal completion, but maybe the cache hasn't fully emptied to the drive? Kind of like how a printer spooler can cause a word processor to return from a print dialog as completed, while the printer hasn't yet started to print.
As a guess also, this may be more apparent in say an older system with USB 2.0 with longer transfers and more perceptible delay than in newer USB 3.0 systems. Which may be why some people are having the problem, and others never see it and don't know what the fuss is about.
I dunno, these are just guesses...
Also the OP talked about unmounting under pupmode5 where the automatic flush transfer appeared to finish before it actually had. This is the same problematic process.
I think I have also had situations in the past when graphically unmounting a USB drive (by left clicking the drive "dot") when the "dot" or light or X on the drive icon went out before the transfer was finished, and then I pulled the USB stick out before it was actually ready.
Thinking about why this could be happening, I'm wondering if there is some kind of USB cache or buffer that these indicators are reacting to. They finish sending data to the cache, signal completion, but maybe the cache hasn't fully emptied to the drive? Kind of like how a printer spooler can cause a word processor to return from a print dialog as completed, while the printer hasn't yet started to print.
As a guess also, this may be more apparent in say an older system with USB 2.0 with longer transfers and more perceptible delay than in newer USB 3.0 systems. Which may be why some people are having the problem, and others never see it and don't know what the fuss is about.
I dunno, these are just guesses...