Generally when I am messing with usb drives I have used these 2 commands: grep Dirty /proc/meminfo (dirty is the amount of write buffers that need to be flushed for all disks, most will usually be the disk that was just copied to) the second is "vmstat 1" and watch the bi/bo columns as they show reads and writes to the disk subsystem, if it umounts when the writes stop that implies the sync may have returned before it actually did all its work. On Mon, May 7, 2018 at 6:58 PM, Bob Goodwin <bobgoodwin@xxxxxxxxxxx> wrote: > On 05/07/18 19:35, Samuel Sieb wrote: >> >> >> Then that supports my suggestion. Unless the the flash drive is mounted >> with the "sync" option, the data is copied into the cache and the copy >> command exits. The data is being written in the background, but when you >> want to unmount the drive, it has to wait until all the data is finished >> writing. To verify this, try running "sync" after doing the copy. That >> should take the same time to exit and then the unmount should be immediate. > > > + > > I should have mentioned, I always type sync before going to the desktop icon > and unmount. Before this problem started things worked differently, but it's > been a long time, as I said I just put up with it, I expect Fedora 28 will > do the same in my system ... > > -- > Bob Goodwin - Zuni, Virginia, USA > http://www.qrz.com/db/W2BOD > box10 FEDORA-27/64bit LINUX XFCE Fastmail POP3 > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
