Using both SSD/HDD for partitioning or is it better to just get external HDD?
I wanted to test out the SSD and it only has very little GB. I download many things so this is very small for me and I always use over 1TB of space. I wanted to know if something like this would work out. (Please note that I'm still quite new to the linux world)
SSD /dev/sda1, /boot /dev/sda2, / /dev/sda3, /usr /dev/sda4, /tmp 2TB HDD /dev/sdb1, /var /dev/sdb2, /home I been wondering how I should partition it and came across this site (I don't use this distro though) Quote:
Quote:
If I do use a external HDD, how would this work? I download files directly into the external HDD and if I wanted to play a video, would the mplayer that's located inside SSD get the benefit from the increased performance of the SSD even while playing the video that's located inside the slower external HDD? Or would I need to bring out the video into the SSD and play it from there? I'm not sure if mplayer in the SSD does all the job reading it or the slower external HDD is doing the work(which means I'm not getting an benefit from the SSD). I apologize for sounding very confusing. Just until yesterday, I had no idea about separating partition was even possible (I always made one partition and one swap) and I'm quite new at this. |
Hi,
As you know the 'SSD' will be functionally faster than the 'HDD'. The limited capacity of the 'SSD' is a controlling factor. Your partitioning scheme should be setup to optimize the use of a 'SSD'. Your example of the player is a good one. Your launch of the player would be faster on the 'SSD' then the player will be operating out of the memory. The load from the storage 'HDD' for video will be noticeable but depending on system resources the playing of the video should be steady. Sure it would be better to have it on the 'SSD' but you have a limited capacity. For a desktop system the partitioning scheme should reflect the typical user applications to be performed. If this were for a server then the scheme would be different. Partition schemes can be very personal and debates occur all the time over the best scheme. I would look at my physical memory first. Max out to the limit of your system memory capability. Then look at how your 'SSD' should be used to speed things up. If you do a lot of compiling then that should give you some lead. If you do video editing then that may dictate how you setup the basic scheme. So for someone else to provide a scheme generally then I say '/' on the 'SSD', minimal 'swap' on 'SSD'. I would create a separate partition on the 'SSD' for '/home'. Then use that big boy 1TB as a storage drive & backup. Do a search here on LQ as this very subject has been covered many times. :hattip: |
The /Storage on the external is probably a pretty good idea. There are a lot of config files stored in /home that get accessed a lot(SSD accesses will be faster). As far as building it, that is pretty easy. You make a sub directory in you home partition (/home/whoever/storage) and then mount the external drive to it. Another alternative (and the one I use) is to put the mount point in a general system area and then put a link to that mount point on your desktop. Here is the line I use from my fstab:
Quote:
|
Thank you for the reply. I'm probably making some people frustrated with all these newbie questions but I really want to make sure I'm doing things right first. I did do a search but I was confused about the way SSD was supposed to be setup because I was told partition scheme should be different from your normal HDD. All the search is coming up for HDD partition scheme and there's things I'm not supposed to do for SSD like making a swap partition or keeping /var in SSD.
I should've mentioned that I don't have any external HDD yet so if it's possible, I could use this 2TB internal HDD that I already have as my storage to save money. I'm not sure if I need a swap since I have 12GB of ram. I also did a google search and it mentioned to never create a swap "partition" on the SSD. I was looking at swap "file" now and maybe create one as a file if 12GB isn't enough for browsing the web, listening to music, storing and browsing pictures, watching DVD or videos, or using Virtualbox for windows on the application that is not compatible with wine. I don't hibernate my computer but I heard I still need at least 1GB minimum of swap no matter how much RAM I have. I'll probably just create 1GB of swap "file" to be on the safe side. Am I on the right track? What I'm confused is when I do a fresh install, how I should create a file called /storage on the 2TB HDD. I'm guessing (I think I'm making a horrible mistake) as root, I do: (sdb is where my 2TB HDD is located at) Code:
mkdir /dev/sdb storage Or is this the correct way? Go to fstab then add a line like this: Code:
/dev/sdb /Storage ext4 defaults According to the wiki, I should make a /var partition (/var isn't recommended on the SSD) here so I should probably add these two instead? Code:
/dev/sdb1 /var ext4 defaults So for a complete newbie guide, it should be something like this. 1) Do a fresh install and making /var partition on the second HDD at /dev/sdb1. /home, /, /boot should be located on the SSD. I heard I only need 32MB for /boot. I'm replacing LILO and going to use grub and I just wanted to make sure if this would be right on the SSD. I only have one OS and I never dual boot. I've seen people make over 150MB for /boot but I'm guessing this is only for dual booters? 2) Install everything else normally 3) After, make 1GB of swap "file" 4) Go to fstab and add: /dev/sdb2 /Storage ext4 defaults. This should magically create a folder called /storage and I can access this and directly download things into this folder. Maybe I'm supposed to follow Lazlow's way (even though this is for internal HDD, I think it should be the same) and make a folder called /home/myname/Storage then go to fstab and mount it using: Code:
/dev/sdb2 /home/myname/Storage ext4 defaults |
No problem...
I think that you might profit by reading these. http://www.tuxfiles.org/linuxhelp/linuxfiles.html http://www.tuxfiles.org/linuxhelp/mounting.html As I read the post from lazlow, the suggestion is that your /home directory be on the SSD in a /home partition. Then" You make a sub directory in your home partition (/home/whoever/storage) and then mount the external drive to it." Mounting either an external or internal HDD to the sub-directory "storage" puts the content that you want to store on the larger but slower drive, and the directory in which it is located, that will be called upon more often, on the smaller but faster SSD. A directory is a logical location for files, but the physical location of the files does not have to be the same as the the logical location. |
Thank you for the links thorkelljarl.
I read few things about SSD and came up with this and this. It seems like I don't have to make separate partition like /var or use something like ext2 according to the ext4 lead developer (Theodore Tso). I made my partition scheme very simple: /etc/fstab Code:
/dev/sda1 /boot ext2 defaults 0 1 Code:
mkdir Storage Code:
/dev/sdb1 /home/myname/Storage ext3 defaults 0 0 When I checked what's inside /dev, I see: sda1, sda2, sda3, sda4, sdb, sdc, sdd, sde, sdf. There's nothing called sdb1 in there so I changed it the /dev/sdb and I still get the same problem. |
I will take a guess that you have not formatted the file system on the drive, yet. You will probably need to put a partition on it (sdb1) and then put a file system on it. Gparted is probably either on your system or available in your repo, and it does both jobs very well.
|
Quote:
|
I successfully created sdb1 but I have a quick question regarding this. I'm trying this out on another HDD which has 600GB in it. I'm using large amounts of GB after I used the entire HDD for sdb1 storage. Is this normal?
Also, when I cd into /Storage and type ls -a, I get something called lost+Found. Is this what's taking 10GB of space? I used the entire drive space and using ext4 on this. This is what I added to my /etc/fstab: Quote:
|
They lie...
If you were to buy a 500GB HDD, its actual size may be less than the nominal 500GB that it would be sold as by measure. Look at the description of capacity measurements in point 3.1 in this . http://en.wikipedia.org/wiki/Hard_disk_drive In addition, the HDD size listed is as it is unformatted, and formatting also uses some of its storage capacity. My formatted 500GB HDD has 465GB of actual capacity as measure by "lshw" lost+found is normal. You may find it and its function with Google. |
Hi,
Quote:
You have too understand that the general statement of placing your '/var' on a 'SSD' can produce potential problem(s). The issue of writes to newer 'SSD' is not what it was for their predecessors. The major reason for not placing '/var' is that your will be writing logs and information which will be dependent on the operations performed. Placing on a different media like a 'HDD', the writing of the log(s) will not effect a noticeable problem, if you do notice a problem then you had better find out why or what the problem is. Whenever you allocate space on a storage media you must also create a 'filesystem' on that media. :hattip: Just a few links to aid you with your Linux ventures; Linux Documentation Project Rute Tutorial & Exposition Linux Command Guide Utimate Linux Newbie Guide LinuxSelfHelp Getting Started with Linux Advanced Bash-Scripting Guide Virtualiation- Top 10 These links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links! |
Ok, the HD manufactures round off when they label their HD drives on size (one issue). Ext3 and Ext4 are journaling file systems, which means the can fix themselves relatively easily (sorta). However it also means that it takes up more space, if I remember correctly the default is 5% of the disk space. While this amount can be adjusted(takes longer to look up how than to actually do it), in most cases I would just leave it as is.
|
Thank you for the reply and links.
Quote:
Series: X25-M Model : SSDSA2MH160G2R5 The ext4 lead developer mentions "However, the next generation of SSD’s, such as Intel’s X25-M SSD, have worked around the write amplification affect" so I was thinking it was alright to place /var into SSD or even make a swap partition. (I have 12GB of ram but I read before that I must have 1GB of swap partition/file no matter how much RAM I have or my computer won't function correctly. I don't use hibernation either.) I made a post about the read/write permission issue and wanted to confirm if this is safe to do: Quote:
|
Hi,
Your setting up a multi-user system now? Your concerned about control of the access to the storage by some other account on this machine? Who made the 1GB swap statement for a 12GB base memory? I'd ask why and not accept such as verbatim. How did you define the use of the system to the person that stated 1GB swap? If you are going to be doing large or intense applications that will utilize the memory footprint and your paging is set high then a 1GB would be a safe choice. But if your utilizing a normal desktop with that much memory then your paging most likely won't occur to swap so a smaller swap could be designated. Especially if your wanting to place the swap on the 'SSD'. The growth of the '/var' is the issue if you are not careful. By placing the contents of '/var' space on the 'HDD' an mounting on the 'SSD' directory '/var' won't cause a problem as long as the space allocation is sufficient. :hattip: |
Quote:
Quote:
Quote:
|
All times are GMT -5. The time now is 05:55 PM. |