Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

coolbreeze2

macrumors 68000
Original poster
Sep 24, 2009
1,810
1,484
I just installed Mojave on my MBP. My desktop is designated to load to iCloud. I decided that a folder on my desktop which is 8.3 GB is taking up too much space on iCloud; therefore, I am moving it from my desktop to another place on my computer that is not connected to iCloud. It never gets pass "Estimating time remaining" and has been stuck for an hour. This is my 2nd time trying. I stopped the first try after about 20 minutes to try again.

I tried to do this with a folder that's 748MB and the result was the same. Then I tried with a folder that's 10.9MB and it was quickly successfully copied.

Should I submit a bug report or does someone what the problem is?
 
Last edited:
I have seen poor Finder performance including aborted copies. For now, I use ChronoSync. On large copies that is a good thing anyway, since you can restart that without copying files already copied.
 
I found a workaround. However, this needs to be solved. I submitted a bug report.
 
OP wrote:
"I found a workaround."

It would be nice if you told us what your "workaround" was.

The problem with copying a folder containing many items is that there need be only ONE "corrupted file" inside to toss a wrench into the entire process. The finder will abort the copy, but WON'T tell you what file was the culprit.

An easy way to get around this is to use CarbonCopyCloner to copy the folder from one volume to another.
Of course, it's a bit of work to "deselect everything else" BUT the folder/folders in question, but it's worth the effort. Here's why:
CCC will NOT "abort the copy" when it encounters a bad file(s).
Instead, it makes note of the problem files and then.... goes right on copying.
When the clone is done, CCC will present you with a list of "problem files" that didn't get copied.
At this point, you can decide what to do with them -- delete them, try to "fix them in place", etc.
 
  • Like
Reactions: J.Gallardo
OP wrote:
"I found a workaround."

It would be nice if you told us what your "workaround" was.

The problem with copying a folder containing many items is that there need be only ONE "corrupted file" inside to toss a wrench into the entire process. The finder will abort the copy, but WON'T tell you what file was the culprit.

An easy way to get around this is to use CarbonCopyCloner to copy the folder from one volume to another.
Of course, it's a bit of work to "deselect everything else" BUT the folder/folders in question, but it's worth the effort. Here's why:
CCC will NOT "abort the copy" when it encounters a bad file(s).
Instead, it makes note of the problem files and then.... goes right on copying.
When the clone is done, CCC will present you with a list of "problem files" that didn't get copied.
At this point, you can decide what to do with them -- delete them, try to "fix them in place", etc.

The folder was on my desktop which is synchronized between my devices. Apparently the corrupted part of the folder was only on my laptop? When I tried to copy the folder on my iMac it did so without a problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.