If it was a journaling file system then the sync would happen no less frequently than every 5 seconds. FAT is not journaling so there's no kernel-level periodic sync'ing being enforced. Just a massive write cache fills up (see: free -h)
At the GUI level I do agree we should be representing the actual performance of the copy. An fsync or whatever would make sense to me. It seems there have already been upstream discussions but they've stalled for years: https://gitlab.gnome.org/GNOME/nautilus/-/issues/3015 https://gitlab.gnome.org/GNOME/glib/-/issues/3043 https://gitlab.gnome.org/GNOME/glib/-/issues/207 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3015 https://gitlab.gnome.org/GNOME/nautilus/-/issues/3015 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3043 https://gitlab.gnome.org/GNOME/glib/-/issues/3043 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #207 https://gitlab.gnome.org/GNOME/glib/-/issues/207 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/3015 Importance: Unknown Status: Unknown ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/207 Importance: Unknown Status: Unknown ** Also affects: glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871869 Title: Nautilus copy task status is not accurate. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1871869/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
