Page 2 of 2

Re: Various problems with CAJA

Posted: Sun Jul 07, 2019 10:36 am
by scjet45
ColdBootII wrote:
Sat Jul 06, 2019 11:35 pm
wpshooter wrote:
Wed Feb 13, 2019 10:29 am
So, for some reason it just takes an inordinate amount of time
for the VERY FINAL part of the copy process to finish and the copy procedure
window to close !!!

Don't seem to have this problem though when copying anything other than
the ISO image(s).

You should not rely on the "copy procedure window" for anything when copying is done to a USB if it involves large files like ISOs. This is not just Caja's issue.

It doesn't report the actual speed at which the stick is writing data. You may have noticed that if you ever tried to "Eject" it when progress window closed, you receive a notification that "Kernel is busy...bla bla" Of course, if you copy a few small files this is less marked since even the slowest USB 2.0 sticks write at least 2MiB/s in Linux. And the writing speed can vary considerably depending on the state of the stick and the amout of data to copy.
I don't have any problems copying huge files with Caja, but, as @ColdBootII mentioned, the copying ain't really done, 'till it's done, (due to cacheing).
If you open another terminal while coping large files, via file-manager or terminal, and run, ie:

Code: Select all

iostat -x 1
you'll notice that even though it looks completed,
"iostat" is still displaying the real drive's write/read stats for a couple more seconds, depending, hence why when after copying large files to usb, ..., it's always good to wait a second or so, before slamming an "Eject", or "Unmount".

Re: Various problems with CAJA

Posted: Sun Jul 07, 2019 11:02 am
by ColdBootII
According to this document, it is possible to determine exactly when copying to the flash stick really finished i.e. all the data were synced. It happens when the 9th field in stat file in_flight equals zero. Furthermore, it is also possible to tell how much data was actually written by the flash stick, very precisely.

But no file manager I ever used in Linux, implements this. To be sure, you will see no more than an approximation in Windows as well. :mrgreen: Indeed it is good practice to wait up some time after copy progress dialog closes.

Cheers :D

Re: Various problems with CAJA

Posted: Wed Jul 24, 2019 5:40 am
by scjet45
Regarding the 'slow-to-open-folders" issues with Caja, I've created a github account and voiced my concerns upstream with one of the many other still open tickets there.
In the meantime, on my Mate 19.1, I've replaced Caja with Thunar <-which is far more responsive than Caja ever was.