Turned on cmd-L to see where it's at and I've got several pypy versions and MacTex in there, hundreds of gigs of files. Based on this new information which I so desperately wish apple made me aware of before running, I expect my install to take at least overnight. thanks apple for your consistently declining level of software quality!
Upgrading to Mac OS X 10.10 Yosemite as a Developer
21–30 of 39 posts
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#22Isn't it safer to use the "ditto" command for the restore? sudo mv /usr/local ~/local then merge it back in ditto -V ~/local /usr/local That way it should merge all the files from the backup into the new folder (and show you what it's doing)
Thanks, I've updated the post in response to this suggestion from you & a few others. Might need to force refresh your browser to see it.
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#23Just a warning - after 6+ hours (not sure exactly as I went to sleep) my Yosemite install failed because the log buffer was full. I can't say for sure that this would not have happened if I hadn't left the log viewer open, but I would recommend closing the log window when you're not actively using it.
All add a note about the log buffer, thanks.
Just happened again. The error is:
Line 128,493 - INSTALLER LOG SHARED BUFFER IS FUL
This time I only opened the log viewer briefly at one point during the upgrade, and again after several hours because it seemed to have hung again. I can't imagine I'm the only one who's affected by this issue. I'll report back when/if I find out how to fix it.
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#24Earlier quoted context omitted.
All add a note about the log buffer, thanks.
Just happened again. The error is: Line 128,493 - INSTALLER LOG SHARED BUFFER IS FUL This time I only opened the log viewer briefly at one point during the upgrade, and again after several hours because it seemed to have hung again. I can't imagine I'm the only one who's affected by this issue. I'll report back when/if I find out how to fix it.
What did you do after this happened? Is it safe to restart the machine, or will that totally hose the install?
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#25I 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.
45 minutes, another lost 15 minutes... wow, you're install went fast! Everyone else seems to be having multiple-hours long installs. :)
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#26Earlier quoted context omitted.
Just happened again. The error is: Line 128,493 - INSTALLER LOG SHARED BUFFER IS FUL This time I only opened the log viewer briefly at one point during the upgrade, and again after several hours because it seemed to have hung again. I can't imagine I'm the only one who's affected by this issue. I'll report back when/if I find out how to fix it.
What did you do after this happened? Is it safe to restart the machine, or will that totally hose the install?
(Gah! HN's anti procrastination measures have kicked in so I can't login with my normal account... )
Anyway, I've got threads open at Apple ( https://discussions.apple.com/thread/6603910 ) and at MacRumours ( http://forums.macrumors.com/showthread.php?t=1803281 ) describing my situation - hopefully some kind soul will be able to help out.
In the meantime I've restarted the process one more time. The laptop still boots straight into the Yosemite installer so I don't think the hard reboots have adversely affected the machine.
edit: It occurs to me that the longest I've waited has been 12 hours (my first attempt). I've now seen reports of 15 hour installs, perhaps I didn't wait long enough? Even if the log buffer is full, that wouldn't necessarily mean that install has outright failed... hmm
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#27I 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.
45 minutes, another lost 15 minutes... wow, you're install went fast! Everyone else seems to be having multiple-hours long installs. :)
It was multi-hour altogether, but the lying about two minutes remaining only took 45 minutes.
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#28Super handy Jim, big thanks. Full install completed in 40 mins with no issues with brewed packages. ;)
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#29I 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.
Sorry, 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.
Re: Upgrading to Mac OS X 10.10 Yosemite as a Developer
#30I 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.
I'll add that note. People with problems tended have >100k or more files.
See 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.