• Unbecredible@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      2 days ago

      This is the only thing I can’t forgive. I accept that it’s hard to say how long something is going to take. But when that bar reaches 100% something should happen pretty fucking snappish.

      • mPony@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        8 hours ago

        Windows gets around this by sitting at 99% instead. it’s the “I’m not touching you” of file management.

          • Natanael@infosec.pub
            link
            fedilink
            arrow-up
            1
            ·
            4 hours ago

            Shouldn’t be 5 min, but that’s what you get if the drive don’t have both enough RAM and capacitors to hold a decent write cache to extend it’s lifetime. Then the OS have to either wait for drive to report it’s done, or complete the sync from the file system driver’s cache. Or else you simply deal with it being both slower and dying faster…

            • village604@adultswim.fan
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 hour ago

              I was being hyperbolic, but the OS shouldn’t report the transfer as complete if the drive hasn’t reported it’s done.

              The fact that the system is able to tell you the transfer isn’t complete when trying to safely remove the drive means the information exists for the file transfer dialogue to utilize.

              A simple “finishing things up,” message in the transfer dialogue is all that’s needed. Especially since unplugging a thumb drive without safely removing it (which tons of people do) while a transfer is still ongoing can corrupt the data on the drive.