4 ms·
I had 32k files using up 8GB in /usr/local, and the time spent on "2 minutes remaining" was about 45 minutes. In retrospect, I'm happy that I didn't waste any
by podsnap 12y ago
I had 32k files using up 8GB in /usr/local, and the time spent on "2 minutes remaining" was about 45 minutes. In retrospect, I'm happy that I didn't waste any time on special preparations.
One thing I learned is that the ⌘L log window blocks progression from restore to the next reboot; I lost about 15 minutes that way.
- jlindley 12y agoI'll add that note. People with problems tended have >100k or more files.
- podsnap 12y agoSee my reply above. A more accurate count on a keyboard with working keys is 243185. I'm starting to wonder whether the /usr/local-related delay is naturally about an hour, but vastly increased - sometimes catastrophically - by having the log window open. Just a theory.
- jlindley 12y agoI've gotten messages from people who didn't even know how to open the log viewer until hours into the process, so it's just a highly variable delay depending on individual circumstances.
- bratsche 12y ago45 minutes, another lost 15 minutes... wow, you're install went fast! Everyone else seems to be having multiple-hours long installs. :)
- podsnap 12y agoIt was multi-hour altogether, but the lying about two minutes remaining only took 45 minutes.
- podsnap 12y agoSorry, 32k was the result of `ls -lR /usr/local | wc -l` and then typing on a keyboard with a broken 4. To be much more precise, `find /usr/local -type f | wc -l` is 243185, while (including directories and links) `find /usr/local | wc -l` is 274709.