Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm going to install fedora on my machine. I have 16 GB's of RAM, 120 GB SSD & a 1 TB Drive. How should I set up my partitions to get the best use of what am running?

share|improve this question

closed as not constructive by Ƭᴇcʜιᴇ007, rob, Sathya May 20 '12 at 8:57

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

I don't have a SSD, but if I did I would probably just put / on the SSD and /home on the larger drive. It would be nice to have someone with actual experience and/or benchmarks answer, though. – user55325 May 20 '12 at 3:02
Yea, from the tutorials/ forums I've read. Most don't account for a system with that much resource available. – Digital Fire May 20 '12 at 3:04
This is WAY vague can only be answered with opinion. As the question stands now, the answer is "Set them up how you'd like, as it's yours and you know your usage better than us.". If you run into a problem setting them up how you'd like, come back and ask questions about actual problems. ;) – Ƭᴇcʜιᴇ007 May 20 '12 at 5:00
This seems to me asking like schedule your life by others. ;) – avirk May 20 '12 at 5:51

As an opposing response to @emb1995 I would say "It depends"... I say this because it is somewhat important to know what you use your computer for. The SSD is small, and thus if you want to store all of your music and pictures and videos in your /home directory (which is where the default folders are), the you will fill up that SSD quite fast.. I would assume since you HAVE a 1 TB HDD that you are planning (or already) have a decent amount of data that you need to store. If this is the case, and for desktop purposes, I would put the layout as follows:

Mount Point | Size, Type               | FS Type
/boot       = 150MB, Primary Partition = ext2
/           = ~103GB, Primary          = ext4
swap        = 17GB,  Primary Partition = Swap

/home       = All 1TB, Primary Partition = ext4


Now remember in this situation the rule of "The bigger they are, the harder they fall" applies quite well... meaning that if you put important data on your computer, you better be backing it up. 1 TB of data is an aweful lot of data to lose in case of a HDD failure. I would suggest a RAID-1 or RAID-5 if your mobo supports it, or if you have the extra $ for another drive or 2... even a software raid isnt as bad as loosing the data... and in some cases can be better (portability standpoint).

Swap on SSD?!?!: You will find many arguments against this, but being you have 16 GB of RAM I doubt you will reach a point of actually using the swap. Also, most of the argument of 'burning out your SSD' dont really apply anymore to modern-day SSD, you will most likely never 'burn out' your SSD before you upgrade first. Allocating 17GB of swap was so you can hibernate and resume. Ahh yes, and if you are that paranoid about it you can manually set the OSs "swappiness" to 'very low' as to encourage it to use RAM moreso than swap, and thus ease your worries some more about swap frying your ssd (even though I already said it wouldn't happen).

Do /boot, /, swap in that order because if you ever want to remove your swap from the ssd, it is easier to grow the '/' backwards to consume that space, than it is to grow '/' forward. Trust me on this one!

Lastly, if you are using your system as a fileserver or web server and not for 'desktop' use, then this scheme doesn't apply very well and would need to be rethought with intended use in mind.

share|improve this answer
Also remember, if you do RAID 5 or 6 without battery-backed cache, you'll be susceptible to data loss due to the so-called RAID 5 write hole. Software RAID 1 in Linux is awesome, because you can add as many levels of mirroring as you want. Use at least 2 levels of mirroring to improve your odds in the event of a disk failure, and don't forget to keep an up-to-date backup (or two). – rob May 20 '12 at 6:00
Didn't you mean "it is easier to grow the '/' forwards to consume that space, than it is to grow '/' backwards."? I think you got backwards and forwards swapped. – Dan D. May 20 '12 at 6:02
@rob, Yes I didn't mention the write hole, but I don't think RAID 6 suffers from it as well. Either way, a RAID of anything but 0 would be safer than simply relying on one drive. I cannot stress enough that you need a backup of sorts. – CenterOrbit May 21 '12 at 16:46
@DanD. , No I mean grow backwards. If the partition needs to grow forward on the disk, you will have to first move the entire partition forward (very risky procedure) and then expand backwards to the end of the disk. Whereas if you are already in front of any potential expanding it will be a quick and painless procedure that will grow the partition backwards. – CenterOrbit May 21 '12 at 16:48
I agree on that fact but I only consider that according to this diagram: [start of disk | <- expand backwards towards start of disk [start of partition | end of partition] expand forwards towards end of disk -> | end of disk], that my spacial mapping differs, in that your backwards is forwards and your forwards is backwards. – Dan D. May 21 '12 at 22:06

I would recommend keeping / and /home on your SSD, but /boot, /var, and /media/data on the rotary disk. This guide seems to be a wealth of information.

share|improve this answer

There's one item the guide @emb1995 posted that hasn't been stressed enough here.

Cells wear out. Consumer MLC cells at mature 50nm processes can handle 10000 writes each; 35nm generally handles 5000 writes, and 25nm 3000 (smaller being higher density and cheaper). If writes are properly spread out, are not too small, and align well with cells, this translates into a lifetime write volume for the SSD that is a multiple of its capacity. Daily write volumes have to be balanced against life expectancy.

Therefore I would recommend against putting /home /var and any other partition you use to store variable data on the SSD. And that probably also means it's best not to put SWAP on the SSD as well because it is by nature volatile. Again in this particular case with 16GB RAM your SWAP usage is likely to be low but still it's a waste of write operations on a device that has a limited number of them.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .