MacOS – `rm` and Mac OS X’s Versions feature

macosversions

I assume that deleting a file via Finder also deletes any previous versions in /.DocumentRevisions-V100 that are attached to that file.

But what's happening if a file is deleted in Terminal with the rm command? Are previous versions left behind or do they actually get deleted, too?

Best Answer

rm just deletes the file(s) specified on the command line. So if you need to delete additonal files from /.DocumentRevisions-V100 you need to delete them explicitely as well.

Related Solutions

MacOS – External hard drive problems

Sure this problem applies for both your drives? Could be that one drive affect the other thru your USB controller. Try to disconnect one of them and see it it gets better. If it doesent, swap them to see. If it gets better while one of them is disconnected I would limit the problem to be a faulty drive.

You could also try to check if some processes are accessing your drive. Have you checked torrent or so aren't loading to the drive(s)?

Alternatively you could turn off the option for spinning down your hard drives when possible in your settings panel for power.

macOS Terminal – How to Force Relaunch Finder in Background

The open command exits after it opens Finder. Even if it didn't, closing a shell would close background processes. You could try using disown:

/System/Library/CoreServices/Finder.app/Contents/MacOS/Finder & disown $!

Or launchctl submit:

launchctl submit -l my.finder /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

launchctl remove my.finder removes the job.

Have you looked at log messages or crash reports? If you have tried to load or unload /System/Library/LaunchAgents/com.apple.Finder.plist, try removing entries for Finder in /var/db/launchd.db/com.apple.launchd{,.peruser.501}/overrides.plist.

Best Answer

Related Solutions

MacOS – External hard drive problems

macOS Terminal – How to Force Relaunch Finder in Background

Related Question