DS_Store files (using " defaults write DSDontWriteNetworkStores true") but that did not prevent the issue. That might explain why you can copy using Finder sometimes and you can't other times (timing of the reading/writing of those hidden files?) - but I can't be sure about that. It could be related to the hidden files that AFS is dead set on putting everywhere it can. This is obviously a Finder issue and has nothing to do with the ability to actually copy files. No issues whatsoever using "cp" with single or multiple files. I'll report back when I have a better idea about other processes and the reliability of this work-around.Īfter a week of using "cp" on the command line, I'm confident in saying this is a viable work-around. I need to copy a lot more files before I'm convinced using "cp" is a reliable work-around.
I haven't received an error using "cp" yet but I've only used it for a handful of files. My current work-around is to use the "cp" command (I'm not using "sudo" - permissions are not the issue). I'll keep poking around to see if I can tell what that "something" is. However, these clues about DiskUnmountWatcher and EvernoteHelper may point toward the root cause: "something" is occasionally (randomly?) opening/locking these files either on the local drive or on the network drive. I do not have Evernote nor any EvernoteHelper running. I tried quitting/disabling DiskUnmountWatcher but that didn't help me.
If there were permission issues the copy would never be successful without changing permissions. If I keep trying over and over, the file will eventually will copy successfully with no changes to any permissions between attempts. If there were permission issues the error would occur as soon as the copy was first attempted.
The entire files copy - completely - then I get the error at the end. The issue began with me when I upgrade to Yosemite (I skipped Mavericks).
0 kommentar(er)
