You are not logged in.
I have a 240GB SSD and 1TB HDD. I am not sure how to partition my installation, should I put all the partitions i.e. /, boot, swap, home on the SSD and use the HDD for storing big files like games? Or have my home on the HDD and the rest on SSD? The first option seems like a good choice to me personally. In the first case, I know how to make the 4 partitions on SSD but how to set up the partitioning for HDD to use it for storing big files, where to mount it and all?
Thanks
Last edited by an4rki_ (2022-08-22 20:50:13)
"A computer is like air conditioning - it becomes useless when you open Windows." - Linus Torvalds
Arch + DWM
Offline
This is, of course, going to be like arguing how many angels can dance on the head of a pin.
Where it my system, I would use the ssd for everything except /home. I would use the tried and tested ext4 for my root partition.
I would partition the HDD, then create one huge btrfs (https://wiki.archlinux.org/title/btrfs). I would create a @home subvolume and mount it at /home. If you want, you could also create a subvolume for your "big files". The beauty is that on btrfs, these subvolumes share the storage space of the main volume but appear to be independent volumes (technically, they are more like namespaces). Kink of gives you the best of both worlds. And, it keeps the system on the ssd to provide higher performance.
This assumes you are not planning a great deal of high disk activity in home -- like a lot of compiling or database I/O.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
While I agree with ewaller that there is a good bit of subjectivity to this, the size of those drives puts you so far out on one end of the continuum that is seems pretty clear to me: and here's where I'd disagree with ewaller. I'd put "everything" (all system partitions including home) on the SSD. The size of boot is trivial, and swap (if used at all) tends to be modestly sized. What can be greatly debated is just how bit a root partition should be - for most of my systems, 10G is far bigger than I'd ever need but more complex systems can certainly benefit from more room; though I just don't see any point in a root partition being more than 20-25G on any system. But even if your root partition approaches 40G (which is absurdly large), that still leaves nearly 200G on the SSD which you may as well use for home. The home partition stores all sorts of sporadically placed config files, data files, cache data, etc that is all read every time a program starts up - thus having home on a SSD can greatly benefit performance.
Then use the 1TB to store particularly large data / media. Here's where I'd go back to agreeing that perhaps btrfs could be a good choice - or maybe an lvm so you can reallocate some of the 1TB "on the fly" as needed. Depending on your usage, I could imagine a chunk of the 1TB HDD might get mounted at or under /opt (to store non-repo games which tend to be quite large), and another chunk could be somewhere under home for media / videos / photos / etc.
Last edited by Trilby (2022-08-22 16:12:59)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I would recommend putting your /boot, /root, and swap on the SSD, and then put your /home partition on the HDD. This partition layout assumes that you aren't wanting the fastest access to your home directory, but I would trade size for speed in most cases.
Before generating the fstab make sure to mount everything where you want it, and make sure you mount your HDD to /home. As for the partition sizing, I would recommend the following:
--- SSD ---
300 MB fat32 boot partition (assuming you have a uefi system)
8 GB swap partition (assuming you don't want to hibernate your system)
For the root partition just have it use the remaining space, also using btrfs.
--- HHD ---
1 TB btrfs home partition
Offline
Trilby makes many good points. Allow me to refine my suggestion.
Perhaps the SSD is a good place for home for the reasons noted. My home tends to have my multimedia files, all my build directories, and even a couple VM images that might be better on cheaper, bigger, slower storage. Here is where the btrfs (or lvm) magic can happen. Suppose I decide my multimedia files don't need to be on the SSD anymore. Great, make a new subvolume on the big btrfs volume, move the files to that subvolume, and them mount the subvolume on the directory (mountpoint) where the files used to exist (for example. /home/ewaller/multimedia). Aside from being a bit slower, and some confusion that will occur when you start trying to grasp your real disk usage, things should be seamless.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
You have to put /home on SSD otherwise any program that stores anything would drop down to HDD speeds.
Most programs put tons of tiny files under your /home (configs, saves, caches, ...) you only get SSD level performance if those are stored on SSD.
Offline
While I agree with ewaller that there is a good bit of subjectivity to this, the size of those drives puts you so far out on one end of the continuum that is seems pretty clear to me: and here's where I'd disagree with ewaller. I'd put "everything" (all system partitions including home) on the SSD. The size of boot is trivial, and swap (if used at all) tends to be modestly sized. What can be greatly debated is just how bit a root partition should be - for most of my systems, 10G is far bigger than I'd ever need but more complex systems can certainly benefit from more room; though I just don't see any point in a root partition being more than 20-25G on any system. But even if your root partition approaches 40G (which is absurdly large), that still leaves nearly 200G on the SSD which you may as well use for home. The home partition stores all sorts of sporadically placed config files, data files, cache data, etc that is all read every time a program starts up - thus having home on a SSD can greatly benefit performance.
Then use the 1TB to store particularly large data / media. Here's where I'd go back to agreeing that perhaps btrfs could be a good choice - or maybe an lvm so you can reallocate some of the 1TB "on the fly" as needed. Depending on your usage, I could imagine a chunk of the 1TB HDD might get mounted at or under /opt (to store non-repo games which tend to be quite large), and another chunk could be somewhere under home for media / videos / photos / etc.
This looks like a great option. I am going with this one, thanks ![]()
"A computer is like air conditioning - it becomes useless when you open Windows." - Linus Torvalds
Arch + DWM
Offline