Comment 3 for bug 1871869

Revision history for this message
sudodus (nio-wiklund) wrote :

Your observation is correct and I have seen it too. RAM is bigger and processes are buffering in RAM more aggressively in recent computers with recent versions of linux operating systems. Be aware that also Windows uses this feature and for that reason you must 'remove the USB drive safely' or your data on it might get corrupted also in Windows.

For this reason I check flushing the buffers in the new tool to create USB boot drives, mkusb-plug. If you install mkusb-plug, it will bring the shellscript watch-flush, that you can use as a stand-alone program, or use it via the zenity GUI as I use it in mkusb-plug.

It would certainly be possible to do something similar also in Files alias nautilus.

There are pros and cons to let nautilus wait while the buffers are flushed when writing to removable drives, but I agree with your point:

Newbies might be tricked into yanking a USB pendrive before the buffers are flushed. Also more experienced users might forget about unmounting/ejecting. So if nautilus (or maybe a dedicated system service) will show on the desktop that there are still buffered data (alias 'dirty' data) waiting to be written to a removable drive, many users will avoid problems with corrupted files and file systems.