Can't empty trash or eject disk because Finder is "using" files?

Discussion in 'macOS' started by thegreatdivorce, May 2, 2013.

  1. thegreatdivorce macrumors regular

    Joined:
    Sep 23, 2010
    Location:
    Upper Left USA
    #1
    I keep getting various errors when trying to a) eject one of my external RAID arrays, and b) empty the trash, which contains files from said RAID drives.

    It gives me an Error -50 when trying to empty the trash.

    When I try to eject the external drive it says it can't because it's in use.

    Using the lsof command in Terminal reveals that Finder is "using" the file. What the hell?

    Any ideas? This is ridiculous.

    On my rMBP, for what it's worth.
     
  2. thegreatdivorce thread starter macrumors regular

    Joined:
    Sep 23, 2010
    Location:
    Upper Left USA
    #2
    Trying to use rm to delete the file(s) in the trash (which appear to be on the external drive?!) results in an "invalid argument"...

    MacBook-Pro:~ USERNAME$ cd ~/.Trash
    MacBook-Pro:.Trash USERNAME$ sudo rm -R /Volumes/VAULT\ ONE/.Trashes/501/00102.CR2
    Password:
    rm: /Volumes/VAULT ONE/.Trashes/501/00102.CR2: Invalid argument
     
  3. Drew017 macrumors 65816

    Drew017

    Joined:
    May 29, 2011
    Location:
    East coast, USA
    #3
    Use the secure empty trash feature… this works for me sometimes.
     
  4. Fishrrman macrumors G4

    Joined:
    Feb 20, 2009
    #4
    "Can't empty trash or eject disk because Finder is "using" files??"

    Procedure 1
    - Log out
    - Log back in
    - Empty trash
    - Eject disks

    Procedure 2, if #1 doesn't work
    - Shut down, wait 30 seconds
    - Restart
    - After login, empty trash
    - Eject disks

    Procedure 3, if computer won't shut down due to open processes:
    - Hold power-on button down continuously until computer powers off (should take about 6 seconds)
    - Restart
    - After login, empty trash
    - Eject disks
     
  5. Che Castro macrumors 603

    Joined:
    May 21, 2009
  6. thegreatdivorce thread starter macrumors regular

    Joined:
    Sep 23, 2010
    Location:
    Upper Left USA
    #6
    That's usually worked for me in the past, too. Not this time.

    Normal restarts didn't do anything. I ended up having to do a hart shutdown, and all was fine after that. Sigh.
     
  7. printz macrumors regular

    Joined:
    Dec 23, 2012
    #7
    Restarting or even logging out is overkill for a job like this, don't you think? Personally I'd just force-delete the files in Terminal.

    I wish OSX had a utility similar to Unlocker for Windows (third-party, not part of Windows). Something that detects what processes are using the file and lets you disconnect them so you can delete the file.
     
  8. Che Castro macrumors 603

    Joined:
    May 21, 2009
    #8
    If he made a thread about this it usually means this is bugging him , reboot is the quick fix

    I'm assuming this is just a one time problem for him
     
  9. thegreatdivorce thread starter macrumors regular

    Joined:
    Sep 23, 2010
    Location:
    Upper Left USA
    #9
    So, to get back to this ... I'm still having issues with the disk not ejecting. I honestly can't tell what the issue is. I don't know if it's an OS X problem, or if it's an issue with the particular hard drive (in this case, a RAID enclosure w/two 3TB drives in RAID 1.)

    Any clues? lsof command still reveals Finder as using the files.
     

Share This Page