Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I just came across this blog article by lloyd chambers of Macperformanceguide as he tested Fusion drives: http://macperformanceguide.com/fusion-complexity.html

Though this article came out before the release of ML 10.8.3.
He recommends having a separate physical backup of your fusion drive.
He is being captain obvious because he doesn't understand the technical stuff that well (it's in his other articles too). He's trying to fix 1 drive that is part of the Fusion Drive in a completely different Mac. Anyone who knows the technology would not even attempt such a ridiculous thing. It's like taking out 1 disk in a RAID array and rebuilding it on a completely different machine. Or if you have 1 disk in your computer at home: chopping it in half and trying to fix it on your computer at work. Of course it doesn't work. The only additional thing he found and for which we do have to give him some credits is the fact that trying to do something this stupid can result into hosing the data on all the disk in the machine you are using to fix the disk.

Anyway, the OWC article:
There have been many tutorials on how to create a Core Storage volume that have been labeled as “how to create a Fusion drive”. They are two similar, yet different drive configurations.
They are not as different as the author tries to tell you and which is quite clear from the aforementioned articles from Arstechnica and Jolly. You can not create a Fusion Drive specifically. Period. What you can only do is create a CoreStorage Volume Group. Whether that group will be a Fusion Drive or not is not up to the user because it is OS X that will decide on this. That's also the problem: you get a Fusion Drive (or not) whether you like it or not. OS X will create a Fusion Drive automatically when that volume group contains an ssd and an hdd. If you don't want that then your only option is creating something else then a CoreStorage Volume Group. However, this does not make CoreStorage and CoreStorage Volume Groups the same as Fusion Drive! Those are all different things. Fusion Drive can be defined as a CoreStorage Volume Group consisting of an ssd and an hdd.

The only problem I have with the article is the following:
You don’t find out that it’s not truly ‘Fusion’ until the SSD portion has been completely filled up. And even then – what’s on the SSD continues to be read at full SSD speed, so it’s only the new data writes (where existing data on SSD is not being replaced) and subsequent reads of that HDD stored data that are slower due to being on the HDD. The way a Core Storage volume works, it really makes people think they’ve created a true Fusion drive. So, now that you know the difference, the question on everyone’s mind is…
It's just this. Nothing but a claim the other articles are wrong. No proof that they are, no proof that 10.8.3 does indeed create a real Fusion Drive. We have to believe that the author is correct. It's quite a bold statement when you say (nearly) every article about setting up a Fusion Drive for 10.8.2 is wrong when there are articles that provide iostats when moving around data which shows that the speed changes. The technical information about how Fusion Drive works and the differences between 10.8.2 and 10.8.3 is what the article is about. The only problem: the article doesn't contain such info and thus is completely useless. There is a bold claim the other articles are wrong after which they are copy-pasting the Fusion Drive setup procedure that is in those same articles.

The pudding is in the comments :) Somebody has noticed and is asking what the difference is between 10.8.2 and 10.8.3 regarding Fusion Drive. OWV Michael comments on it and it appears they have only tested it with 10.8.1 and 10.8.3. It's a strange comment. I'm wondering if they actually know what they are doing when setting up Fusion Drive. It seems they are misunderstanding some terminology and/or misinterpreting test results. For me the article raises more questions than it answers.
 
My home folder sits on a platter drive after an upgrade go into users preference pane and pick you old home drive as your current home drive..

Oh I think I see... So instead of doing this through Apple's Migration tool. Hmm, never thought of doing that on OS X.

And it works..? Cool!

So to make sure I know what you're talking about an example would be:

  1. Boot in the current 10.7.5 on volume1 (with home folder on volume2)
  2. Upgrade to version 10.8.3 on volume1 (link to the folder on volume2 as the Home)
Right?
 
Oh I think I see... So instead of doing this through Apple's Migration tool. Hmm, never thought of doing that on OS X.

And it works..? Cool!

So to make sure I know what you're talking about an example would be:

  1. Boot in the current 10.7.5 on volume1 (with home folder on volume2)
  2. Upgrade to version 10.8.3 on volume1 (link to the folder on volume2 as the Home)
Right?

Correct, If you dual boot you can share the home folder. The caveat is you may need to give yourself read/write permissions on the individual folders again
 
Correct, If you dual boot you can share the home folder. The caveat is you may need to give yourself read/write permissions on the individual folders again

Yeah, I was aware of that but figured it ought to be the same version - so not very useful.

I think I'm with elvisizer on this one. "YMMV" meaning go for it if you dare... but really not something to recommend to others. I can see way too many potential conflicts with a setup like that. Then when the newby does it he'll be back here with yet another thread asking why he's getting kernel panics or why his machine just turns off all by it self for no apparent reason - and so on and so forth.

I totally agree with recommending this for the data folders (music, documents, images, etc.) but not the entire home folder.
 
Last edited:
Yeah, I was aware of that but figured it ought to be the same version - so not very useful.

I think I'm with elvisizer on this one. "YMMV" meaning go for it if you dare... but really not something to recommend to others. I can see way too many potential conflicts with a setup like that. Then when the newby does it he'll be back here with yet another thread asking why he's getting kernel panics or why his machine just turns off all by it self for no apparent reason - and so on and so forth.

I totally agree with recommending this for the data folders (music, documents, images, etc.) but not the entire home folder.

My milage is fine..my current home folder is the same folder as my 10.6.8 install in my 1,1, it's now in the 4,1 with a 10.8.3 install..
 
That's because Apple has fixed the problems with relocating your homedir (iirc they fixed it in 10.6). For it to work properly you have to relocate it via System Preferences > Users & Groups. Right click the user and select advanced options. In the following window you can define the new location for that users homedir.
 
I guess you didn't catch my meaning. Sorry I kinda suck at this communication thing. I meant like, sure, YOU can do it... cuz you're like a guru master ninja dude... I just wouldn't recommend it to everyone...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.