Hi, I frequently copy files (Size about 2GB, sometimes 50 files of this size in one copying process) from my internal laptop disk (Win8.1) to an external media, usb flash drive or external disk. The copying progress is schown in the right upper corner of the display. When the display shows "copying is finished", the copying process is not really finished, it takes some additional minutes, before I can eject the external media. This appears in F24/F25/F26. This is confusing. Kind regards
Dne 26.7.2017 v 11:13 Joerg Lechner napsal(a):
Hi, I frequently copy files (Size about 2GB, sometimes 50 files of this size in one copying process) from my internal laptop disk (Win8.1) to an external media, usb flash drive or external disk. The copying progress is schown in the right upper corner of the display. When the display shows "copying is finished", the copying process is not really finished, it takes some additional minutes, before I can eject the external media. This appears in F24/F25/F26. This is confusing. Kind regards
You need to create BUG for every tool you are using.
TOOL simply has to wait before 'fdatasync()' operation is finished - otherwise such device just 'fill' your page-cache.
There is nothing else you can do here.
A normal protection from a user against buggy programs like this is - you call 'sync' &| 'umount' from cmdline before you unplug external media - you never try to just 'cut-off' cable when some tool reports 'it's finished'.
Regards
Zdenek
On 07/26/2017 02:13 AM, Joerg Lechner wrote:
I frequently copy files (Size about 2GB, sometimes 50 files of this size in one copying process) from my internal laptop disk (Win8.1) to an external media, usb flash drive or external disk. The copying progress is schown in the right upper corner of the display. When the display shows "copying is finished", the copying process is not really finished, it takes some additional minutes, before I can eject the external media. This appears in F24/F25/F26. This is confusing.
This is standard behaviour on all current operating systems. That is why they all have the "eject" button for unmounting external media. The reason is that the operating system buffers the data in memory and then writes it to the device as fast as the device can accept it. This lets whatever process is doing the writing to get on with other things instead of having to wait for slow media. The unmount command waits for all the cached data to be written to the device before unmounting. Then you get a notification saying that you can remove it.
On Wed, 2017-07-26 at 11:50 -0700, Samuel Sieb wrote:
On 07/26/2017 02:13 AM, Joerg Lechner wrote:
I frequently copy files (Size about 2GB, sometimes 50 files of this size in one copying process) from my internal laptop disk (Win8.1) to an external media, usb flash drive or external disk. The copying progress is schown in the right upper corner of the display. When the display shows "copying is finished", the copying process is not really finished, it takes some additional minutes, before I can eject the external media. This appears in F24/F25/F26. This is confusing.
This is standard behaviour on all current operating systems. That is why they all have the "eject" button for unmounting external media. The reason is that the operating system buffers the data in memory and then writes it to the device as fast as the device can accept it. This lets whatever process is doing the writing to get on with other things instead of having to wait for slow media. The unmount command waits for all the cached data to be written to the device before unmounting. Then you get a notification saying that you can remove it.
I don't think it's "standard behaviour", no. I think quite a lot of file managers only copy synchronously, to avoid exactly this confusion. It would help if Joerg specified which desktop / file manager he's using?
On 07/26/2017 01:35 PM, Adam Williamson wrote:
On Wed, 2017-07-26 at 11:50 -0700, Samuel Sieb wrote:
This is standard behaviour on all current operating systems. That is why they all have the "eject" button for unmounting external media. The reason is that the operating system buffers the data in memory and then writes it to the device as fast as the device can accept it. This lets whatever process is doing the writing to get on with other things instead of having to wait for slow media. The unmount command waits for all the cached data to be written to the device before unmounting. Then you get a notification saying that you can remove it.
I don't think it's "standard behaviour", no. I think quite a lot of file managers only copy synchronously, to avoid exactly this confusion. It would help if Joerg specified which desktop / file manager he's using?
Ok, then it used to be standard behaviour and I haven't paid attention to it since then. :-) I will have to try it out, but I thought I saw this with nautilus recently.
Hi, My desktop is the "Workstation Edition" and I use the files menu with copy and paste. In the case of interest (F26) the first 1.5 GB are copied very quickly (about 100MB/sec) then the copying process slows down to about 11MB/sec. After signalling completion I have to wait about 4 minutes untill I am allowed to eject. If this is normal, then OK, if not, possibly I should file a bug. Kind regards
-----Ursprüngliche Mitteilung----- Von: Samuel Sieb samuel@sieb.net An: test test@lists.fedoraproject.org Verschickt: Mi, 26. Jul 2017 23:45 Betreff: Re: question to file copy to external media
On 07/26/2017 01:35 PM, Adam Williamson wrote:
On Wed, 2017-07-26 at 11:50 -0700, Samuel Sieb wrote:
This is standard behaviour on all current operating systems. That is why they all have the "eject" button for unmounting external media. The reason is that the operating system buffers the data in memory and then writes it to the device as fast as the device can accept it. This lets whatever process is doing the writing to get on with other things instead of having to wait for slow media. The unmount command waits for all the cached data to be written to the device before unmounting. Then you get a notification saying that you can remove it.
I don't think it's "standard behaviour", no. I think quite a lot of file managers only copy synchronously, to avoid exactly this confusion. It would help if Joerg specified which desktop / file manager he's using?
Ok, then it used to be standard behaviour and I haven't paid attention to it since then. :-) I will have to try it out, but I thought I saw this with nautilus recently._______________________________________________test mailing list -- test@lists.fedoraproject.orgTo unsubscribe send an email to test-leave@lists.fedoraproject.org