archive rule not working on 5GB+ folder

Hi there,
i tried search the forum for this issue but no luck.

The problem occurs when hazel is set to archive a folder based on color label: 1-2GB dir. and less works fine but when I trie archiving 5GB+ it fails after some time. This is all on local disk.

any idea what causes this?

2013-06-20 23:14:55.494 hazelworker[8172] Processing folder _user_data_erik (forced)
2013-06-20 23:14:57.521 hazelworker[8172] 5413_Onninen: Rule pakk og flytt matched.
2013-06-20 23:21:36.664 hazelworker[8172] Verification of archive failed: /Volumes/ELT/_user_data_erik/5413_Onninen.zip.
2013-06-20 23:21:36.706 hazelworker[8172] [Error] Archive failed: Failed to create archive for /Volumes/ELT/_user_data_erik/5413_Onninen.
2013-06-20 23:21:39.424 hazelworker[8172] Received abort event.
2013-06-20 23:21:39.425 hazelworker[8172] Done processing folder _user_data_erik

Thanks
Erik

Does it work if you do it in Finder? Also, what OS version are you running on?

Mr_Noodle wrote:Does it work if you do it in Finder? Also, what OS version are you running on?

Mr_Noodle; yes it works in Finder. I'm on 10.8.4

Thanks for helping.

Odd. I'm wondering if there's some sort of 32-bit issue here since that can only address up to 4GB. I'll look into it and see what I can find.

Mr_Noodle wrote:Odd. I'm wondering if there's some sort of 32-bit issue here since that can only address up to 4GB. I'll look into it and see what I can find.

sounds like your onto something there.

I guess it's "ditto" that does the compression process and when inspecting this process in Activity Monitor, it runs through every file in the folder, no matter size of folder, but fails to verify the archive when archived file is, as you write, 4GB+

Looking at the code again (it's been a while), I actually do an extra verification step using "zip". I may drop that since it's time consuming and, possibly error prone.

Mr_Noodle wrote:Looking at the code again (it's been a while), I actually do an extra verification step using "zip". I may drop that since it's time consuming and, possibly error prone.

sounds like this is worth a test. Would you be abel to email me a version with the fix?

Email support and I'll send you a link when I have it ready.