Welcome to a new issue of "This Week in Plasma"! Every week we cover the highlights of what's happening in the world of KDE Plasma and its associated apps like Discover, System Monitor, and more.
very noticeable and annoying when transferring to slower media like usb sticks, sometimes it takes tens of minutes to unmount after copying a large file because its actually still writing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”. this should absolutely NOT be a thing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”.
AFAIK it can actually destroy the USB if it’s removed while being written.
You can use sync in terminal. But it’s tricky because it sometimes returns even when the writing isn’t finished.
My method is to use sync multiple time, if it returns immediately 2 times it should be clear,
Only then do i dismount the stick, because I don’t like to dismount a device with pending operations.
But when the dismount says the stick is ready to be removed, you should be clear.
What annoys me is that this was an issue as far back as the early 90’s. On DOS and Windows 3.11. It’s such an annoyance that I don’t get how this problem still exist?!
If the unmount function can see if write is finished, a file copy function should obviously be able to see it’¨s own copy state.
GNOME does exactly the same thing.
very noticeable and annoying when transferring to slower media like usb sticks, sometimes it takes tens of minutes to unmount after copying a large file because its actually still writing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”. this should absolutely NOT be a thing.
AFAIK it can actually destroy the USB if it’s removed while being written.
no way to know for sure if its still writing if the progress bar is inaccurate.
You can use sync in terminal. But it’s tricky because it sometimes returns even when the writing isn’t finished.
My method is to use sync multiple time, if it returns immediately 2 times it should be clear,
Only then do i dismount the stick, because I don’t like to dismount a device with pending operations. But when the dismount says the stick is ready to be removed, you should be clear.
exactly. thats unnecessarily complicated for someone on a rush for something that should be a functional progress bar.
What annoys me is that this was an issue as far back as the early 90’s. On DOS and Windows 3.11. It’s such an annoyance that I don’t get how this problem still exist?!
If the unmount function can see if write is finished, a file copy function should obviously be able to see it’¨s own copy state.