

documents or downloads or music.Ī third suggestion I met, but with little detail, was using (part of?) the SSD as a cache for the HDD.

Distribute data more or less evenly across the two drives, without any consideration for the speed benefits of the SSD.Īnother option is to manually choose the partitions.Combine the remaining SSD and the entire HDD into a logical Btrfs partition.

As far as I can tell (correct me if I’m wrong!), this will: One option is to just let Anaconda pick the defaults. Here’s what I’ve been able to piece together so far: I’ve done a lot of searching, and there have been questions about this before-not just here, but on Reddit, on FedoraForum, on non-Fedora communities, etc.-but everything I could find is quite old, quite specific to a particular situation, quite technical, or some combination of them.

I would also like the why and the how as much as possible: what are the benefits/drawbacks, and what options are needed to make it happen? (Optionally) Leaving room to dual-boot the system with Windows, but not trying to work around an existing installation.Looking to benefit from the SSD’s speed as much as possible, while using the HDD for things that aren’t speed-critical, like holding media files and documents.A HDD that’s bigger than (or at least as big as) the SSD.A modern SSD with decent size (from a couple of hundred gigabytes up to a terabyte or more) and a lifetime write capacity that’s not worth worrying about.I don’t want this to be specific to my setup (although I am putting together a new computer), so here are the broad-strokes assumptions I’d like recommendations for: What is a current (Fedora 34) recommended setup for a new system with both an SSD and a HDD?
