Find the answer to your Linux question:
Results 1 to 4 of 4
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Linux file system divided between SSD and HDD


    In order to achieve better price/performance ratio, I plan to divide my file system (Ubuntu 14.04) between SSD and HDD.
    Things that are "read mostly" (i.e. most of OS stuff) - should reside on SSD.
    Things that are being read and written (/home, /tmp, /var) - should reside on HDD.
    The rationale is to harness SSD's speed keeping its wearing low.
    The mount scheme is somewhat unusual (at least for me):
    The SSD is mounted under /.
    The (whole) HDD is mounted under /mnt/xxx.
    Each of the directories, /home, /tmp, /var, is --rbind mounted under eponymous mount point.
    The rationale for bind-mounting, as opposed to creating 3 dedicated partitions, is more flexible disk space usage.
    I would like to hear (read) from the more experienced than myself if there are pitfalls I do not see at the moment, in particular related to power-up and suspend/resume times.
    Thanks !

  2. #2
    Linux Enthusiast
    Join Date
    Apr 2004
    Location
    UK
    Posts
    747
    This sounds pretty sensible. I'm using an SSD only here and the performance increase is incredible. I'm not certain if your hybrid setup will have similar performance improvement, but it sounds right to me.

    Suspend/Resume times will depend on your swap space. Are you planning on putting that on the SSD or are you going to keep with the read/write segregation and put it on the HDD?

    Let us know how you get on.
    To be good, you must first be bad. "Newbie" is a rank, not a slight.

  3. #3
    The swap goes to the HDD to keep the read-mostly / read-write segregation.
    My concern is about using bind-mount ... I don't see anything wrong with it, but I have not seen such a scheme in the past.
    ...
    I have implemented it, and it works, seemingly, all right. If anyone sees any pitfall in my design - please draw my attention.
    Thanks !

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    14,038
    -->
    I would definitely put the swap space on the HDD, along with files and directories that get a lot of updates, such as /var/log, /tmp, etc. Executables, libraries (.so files and such), are mostly static except when you occasionally update them. Likewise configuration files in /etc. Databases that are dynamic, should be kept on the HDD if possible.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •