• Tenderizer78@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      6 hours ago

      And on Kubuntu it’s always endlessly writing to the drive, but it doesn’t say what process is doing it and there’s no way to figure it out.

      • anivicivokki@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        4 hours ago

        To be fair, this happens to me also in Debian Gnome, but very very rarely. On Windows, it keeps me from ejecting the drive until after I try it 4-5 times. Every time. In any case, lsof can help identify the culprit.

        lsof | grep DRIVENAME should give which program is keeping it.

    • Fiery@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      12
      ·
      8 hours ago

      Sure, that ‘fixes’ it. The real question is, if that information is retrievable anyways… Why is it not a built-in part of windows. You get the error popup and it should just show two buttons: "Ok and “Find which program is using it”

  • HiddenLayer555@lemmy.ml
    link
    fedilink
    English
    arrow-up
    26
    ·
    16 hours ago

    On Linux it just sticks around as a ghost until it’s closed. Less noticeable but frustrating in its own way.

    • addie@feddit.uk
      link
      fedilink
      arrow-up
      8
      ·
      10 hours ago

      Allows the very important ‘overwrite files while they’re open’ functionality used during update. Write all the new files for a service then restart it. No need to reboot the whole machine for that.

      Looking at you, Windows, and your bullshit scheduled reboots.