• Shayeta@feddit.org
    link
    fedilink
    English
    arrow-up
    56
    ·
    2 days ago

    Wait, is this the fix to that annoying thing when you copy a large file to a slow USB/SDCard and the OS instantly reports the copy as being complete, but actually it’s just been written to RAM and is slowly being written to the actual media in the background, and if you “safely remove” the device you just have a broken incomplete file? Is this the fix for that, finally!?

    Edit: YES, YES IT IS! HOLY SHIT, AMAZING!

      • Shayeta@feddit.org
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 days ago

        Hmm, that might mean I have another issue as well. Since safely remove would just remove the device instantly without waiting…

        • thingsiplay@lemmy.ml
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          2 days ago

          For me, sometimes with huge files even if the copy process ended, and I do a “safely remove”, sometimes I still have to wait a big chunk of time. Safely remove is actually safe, nothing should be left. I also thought this was a feature of the filesystem, where it caches and optimizes the actions before doing it under the hood.

          With something like System Monitor you should be able to see if anything is writing or reading on the filesystem constantly, before you do a disk remove.

    • ulterno@programming.dev
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      I have hated “Safely Remove” from back when I was on Windows.
      Always did weird GUI stuff and does on this too.

      So I just use syncand when it properly finishes, I do safely remove.