Weird Finder Bugs when Copying Files - Fixed in GG 27?

[RumorConsumer]

On Tahoe, I sometimes (not rarely) hit strange issues with large amounts of files like error -51 and -8084 (I think), when copying large amounts of files around between SSDs and the internal drive. If I let the machine "chill out" for a few hours, things work fine. I recently stayed up til 2am trying to figure out why my 600gb of music wasn't copying to an external drive without an error - I left it and woke up the next morning and it was fine. And the whole time, the copy worked with Carbon Copy Cloner. It was just Finder having a feeling. Then there's the issue with SSDs taking way too long to eject from the Finder. Wondering if anybody's workflows include this kind of stuff and how its going for you.

 

[Fishrrman]

"...And the whole time, the copy worked with Carbon Copy Cloner. It was just Finder having a feeling."

My understanding of this.

If the finder (when copying a group of files, small or large) encounters "a bad file" (corrupt or something else that's not quite right with it), it will just stop and abort the ENTIRE copy operation. Nothing gets copied.

However...
If you're using CarbonCopyCloner to do the copy, and CCC runs into bad files, it will just "go around them" and continue copying the rest of the GOOD files. CCC will put the filenames of the bad files into a log that you can check afterwards.

That's why CCC worked when the finder didn't.

 

[RumorConsumer]

"...And the whole time, the copy worked with Carbon Copy Cloner. It was just Finder having a feeling."

My understanding of this.

If the finder (when copying a group of files, small or large) encounters "a bad file" (corrupt or something else that's not quite right with it), it will just stop and abort the ENTIRE copy operation. Nothing gets copied.

However...
If you're using CarbonCopyCloner to do the copy, and CCC runs into bad files, it will just "go around them" and continue copying the rest of the GOOD files. CCC will put the filenames of the bad files into a log that you can check afterwards.

That's why CCC worked when the finder didn't.

CCC will report the error. It won't just say "thumbs up" without showing an error. If you read the post, I said I tried Finder the next day and it worked fine. So this is not a file issue this is a temperamental Finder issue.

 

[RumorConsumer]

Still curious

 

[Evil Lair]

Probably not much help but sounds like the same issue we have at work with Sequoia and SMB Synology shares. Using Finder constantly get error -51's but works perfectly using CCC.

 

[RumorConsumer]

Probably not much help but sounds like the same issue we have at work with Sequoia and SMB Synology shares. Using Finder constantly get error -51's but works perfectly using CCC.

That is going to be because of DS_Store files. Been there with Synologys of my own. Use BlueHarvest and it should work fine, but CCC is still king. Can also be because of differences in what file systems allow. Spaces after file extensions or right before etc. Some things make Finder angry.

 

[benholt]

same experience here on Tahoe with the Mac Studio — Finder chokes on big transfers between the internal and my TB4 raid, but CCC plows through fine. my theory is Spotlight is trying to index / preview the destination folder while it's still being written to. one thing that made a real difference for me: turning off Spotlight indexing on the external volumes with mdutil -i off /Volumes/whatever. eject delays also got noticeably better after that. not on GG beta yet so can't say if any of it's actually fixed there.

 

[RumorConsumer]

same experience here on Tahoe with the Mac Studio — Finder chokes on big transfers between the internal and my TB4 raid, but CCC plows through fine. my theory is Spotlight is trying to index / preview the destination folder while it's still being written to. one thing that made a real difference for me: turning off Spotlight indexing on the external volumes with mdutil -i off /Volumes/whatever. eject delays also got noticeably better after that. not on GG beta yet so can't say if any of it's actually fixed there.

interesting. makes me think if we are seeing this Apple is too. I hope it's fixed.