Page 1 of 1

Could not move file code=89

PostPosted: Mon Apr 09, 2018 6:58 pm
by BitSquad
Hello!

I'm having issues getting hazel to move particular files. This is the error I'm getting:

2018-04-09 18:50:51.710 hazelworker[763] Error moving file from /Users/bobsaget/Downloads/frog.jpg to /Volumes/DataDump/Images/Unsorted/frog-7.jpg: Error Domain=NSPOSIXErrorDomain Code=89 "Operation canceled"

The rules seem to work otherwise, but certain files fail.

Thank you!

Re: Could not move file code=89

PostPosted: Tue Apr 10, 2018 11:37 am
by Mr_Noodle
Can you tell me more about the DataDump volume? Is it an external drive? A network share? Something is canceling the operation and that seems like a likely cause.

Re: Could not move file code=89

PostPosted: Tue Apr 10, 2018 1:28 pm
by BitSquad
Hello!

Yes, it is a NAS. After some experimentation, I found that I didn't have any trouble moving the files if they were staying on my Mac. I figured that Hazel is the solution for ordering my files into a folder structure, but I'll need to find something else to take this data and append it to my archive. If Hazel isn't moving files off the system though and doesn't have to actually rewrite, then it should be much faster, so this seems like it will probably be a much better way to handle it.

Re: Could not move file code=89

PostPosted: Tue Apr 10, 2018 5:49 pm
by BitSquad
I know I said I was going to take another approach, but I want to ask if it is possible to fix this issue or will I need to restrict Hazel to local sorting on the Mac?

My NAS is a Qnap TVS-871U-RP.

I was asking in a Qnap forum how to best set it up to automatically transfer the files sorted by Hazel into the file structure of my NAS, and was suggested that it might be best to have Hazel directly sort them into a mounted drive. I explained how I got errors with this, but as I explore options for how to handle my data, I'd like to know if removing those errors is an option or if that is off the table.

Thank you!

Re: Could not move file code=89

PostPosted: Wed Apr 11, 2018 10:40 am
by Mr_Noodle
I feel like it's an issue with the NAS. The cancellation of the operation is coming from its end, from what I can tell.