Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. According to Samsung docs (http://www.samsung.com/global/business/semiconductor/minisite/SSD/us/html/about/whitepaper05.html) /With the introduction of the 840 Series and the reality of increasingly complex NAND fabrication processes, however, Samsung has chosen to implement a minimum amount of OP in its mainstream drives (the 840 PRO will not feature mandatory OP)./ Should I therefor make sure that I only fill up ~90% of the total disk with partitions during install? Then what about the -discard mount option to get the drive to trim deleted data, Is this something I have to manually add? Is it a best practice to add this or is it better to leave it alone or use in some other way? -- john -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
2013/12/18 Robert Moskowitz r...@htt-consult.com On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I guess it's really depending on what SSD you are using. I'm not sure though, that's why I'm asking. I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. 840 *PRO* is using MLC NAND -- john -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 08:15 AM, John Obaterspok wrote: 2013/12/18 Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I guess it's really depending on what SSD you are using. I'm not sure though, that's why I'm asking. I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. 840 *PRO* is using MLC NAND And the 840 PRO is even MORE expensive compared to the M500, :) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 08:15 AM, John Obaterspok wrote: 2013/12/18 Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I guess it's really depending on what SSD you are using. I'm not sure though, that's why I'm asking. I am doing some more reading on the wiki and found one article (https://fedoraproject.org/wiki/Acer_Aspire_One) that discourages using swap on the SSD becuase of slow write times. Is that still true? Also discourages using LVM. I have often wondered why I use LVM on my notebooks; I don't see the gain over just plain EXT4 partitions. I have read a number of articles and I can't find any solid advantage. I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. 840 *PRO* is using MLC NAND -- john -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 04:38 PM, Robert Moskowitz wrote: Also discourages using LVM. I have often wondered why I use LVM on my notebooks; I don't see the gain over just plain EXT4 partitions. I have read a number of articles and I can't find any solid advantage. Well, I dont have a notebook, but a laptop (16GB RAM, Corei7-8 threads, 512 SSD Samsung 840 Pro) I use it for work, and I heavily virtualize on it. I have 1LV per VM. VMs are small (2GB RAM, 5GB disk space), but they are numerous (mostly 4-5 VMs turned on) When I clone a VM, the LV gets cloned too. I find it very usefull and clean on the drive. I'm sysadmin and I test massive deployment methods (CfEngine, custom packagin,...) -- +261 34 81 738 69 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 10:15 AM, Mihamina RKTMB wrote: On 12/18/2013 04:38 PM, Robert Moskowitz wrote: Also discourages using LVM. I have often wondered why I use LVM on my notebooks; I don't see the gain over just plain EXT4 partitions. I have read a number of articles and I can't find any solid advantage. Well, I dont have a notebook, but a laptop (16GB RAM, Corei7-8 threads, 512 SSD Samsung 840 Pro) I use it for work, and I heavily virtualize on it. I have 1LV per VM. VMs are small (2GB RAM, 5GB disk space), but they are numerous (mostly 4-5 VMs turned on) When I clone a VM, the LV gets cloned too. I find it very usefull and clean on the drive. OK. Excellent justification for LVM. So far I have not done VMs, but I have been thinking heavily about it. But not HOW to do it. Seems like I probably should if I want to set up my drive now for VMs soon. And well, my main system is a laptop, though only 12. Just the right size to use in flight. I'm sysadmin and I test massive deployment methods (CfEngine, custom packagin,...) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Wed, Dec 18, 2013 at 9:38 AM, Robert Moskowitz r...@htt-consult.comwrote: On 12/18/2013 10:15 AM, Mihamina RKTMB wrote: On 12/18/2013 04:38 PM, Robert Moskowitz wrote: Also discourages using LVM. I have often wondered why I use LVM on my notebooks; I don't see the gain over just plain EXT4 partitions. I have read a number of articles and I can't find any solid advantage. Well, I dont have a notebook, but a laptop (16GB RAM, Corei7-8 threads, 512 SSD Samsung 840 Pro) I use it for work, and I heavily virtualize on it. I have 1LV per VM. VMs are small (2GB RAM, 5GB disk space), but they are numerous (mostly 4-5 VMs turned on) When I clone a VM, the LV gets cloned too. I find it very usefull and clean on the drive. OK. Excellent justification for LVM. So far I have not done VMs, but I have been thinking heavily about it. But not HOW to do it. Seems like I probably should if I want to set up my drive now for VMs soon. And well, my main system is a laptop, though only 12. Just the right size to use in flight. If you're a typical desktop user (unlike the situation above) and you're not going to reserve any space on your drive, I don't think there's a compelling reason to use LVM. I do anyway since that's what anaconda defaults to... To explain what I mean... Unless you're going to create multiple LV (perhaps one for /, one for /var, one for /home) and reserve some space on your disk in case you guessed wrong so you can add more space to any of those, then what's the point? This makes even less sense for a laptop, but lets look at a desktop situation. Sure you could add a second disk, add it to your volume group, add space to your LV, and resize your filesystem to use it. One problem though, you've created another point of failure for your FS (two disks) without getting anything in exchange. It's not striped (you can do LV striping, but that's another discussion altogether), it's not mirrored, there's no parity. So why do it? In a server/enterprise setting I think it makes a lot more sense where you're likely to need to use LVM to span across multiple raid arrays, SANs, etc. Just my $.02.. Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 6:03 AM, Robert Moskowitz r...@htt-consult.com wrote: On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. FYI, be aware there appears to be a queued TRIM bug with the M500 where it may be causing silent data corruption. I wouldn't use discard on this, or any, SSD, in production until it's been well tested. https://bugzilla.redhat.com/show_bug.cgi?id=1024002 Until the industry gets its act together on TRIM, I think we're probably better off executing fstrim once a week with a cron job at a time the computer is likely to be idle. Chris Murphy-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 8:15 AM, Mihamina RKTMB miham...@rktmb.org wrote: On 12/18/2013 04:38 PM, Robert Moskowitz wrote: Also discourages using LVM. I have often wondered why I use LVM on my notebooks; I don't see the gain over just plain EXT4 partitions. I have read a number of articles and I can't find any solid advantage. Well, I dont have a notebook, but a laptop (16GB RAM, Corei7-8 threads, 512 SSD Samsung 840 Pro) I use it for work, and I heavily virtualize on it. I have 1LV per VM. VMs are small (2GB RAM, 5GB disk space), but they are numerous (mostly 4-5 VMs turned on) When I clone a VM, the LV gets cloned too. I find it very usefull and clean on the drive. Two other options exist, but first a disclosure being that there are always a bunch of ways to do one thing on linux. And a lot of times it's about comfort level and familiarity rather than what's best. The critique I'd apply to using LV's as backing for VM's is that they allocate all of that space - it's taking out of the VG. So you have to plan in advance accordingly to avoid over committing space that is now no longer in the VG. You can resize but… now that's another series of steps, and you may be resizing again in the future. So while I used to use LVs for this task, I'm now using qcow2 files. I create one, install once, and then snapshot the qcow2 five times (for five VMs) and have the VMs use the snapshots. The backing qcow2 isn't ever modified from that point forward, only the snapshots are. Since they're sparse, they only take up the space that's actually being used. They're easy to backup, etc. Another option, that's quite new and probably still needs testing, is LVM Thin Provisioning. There's an extra layer between the VG and LV called the thin pool. LV's are created with a virtual size, meaning they simply get tagged as being that size (think of it as a maximum) but extents aren't taken from the thin pool until needed by any LV using that pool. So instead of creating 5GB LVs, you can create 50G LVs just in case it's needed. If one LV needs 1GB, then only 1GB of extents are used in the pool the rest are available to other LVs. Also, it's possible to get efficient snapshotting unlike conventional LVM snapshots. So you can create an LV, install a system, snapshot it to create other LVs and use them as your VM backing. No preallocation for snapshot space required, it draws extents from the pool as each VM's LV needs to grow with changes. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 01:32 PM, Chris Murphy wrote: On Dec 18, 2013, at 6:03 AM, Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com wrote: On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. FYI, be aware there appears to be a queued TRIM bug with the M500 where it may be causing silent data corruption. I wouldn't use discard on this, or any, SSD, in production until it's been well tested. https://bugzilla.redhat.com/show_bug.cgi?id=1024002 Seems like a workaround was posted yesterday? So since I am still waiting for the drive to show up on my porch... Until the industry gets its act together on TRIM, I think we're probably better off executing fstrim once a week with a cron job at a time the computer is likely to be idle. And what is TRIM and fstrim? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 8:50 AM, Richard Shaw hobbes1...@gmail.com wrote: This makes even less sense for a laptop, but lets look at a desktop situation. Sure you could add a second disk, add it to your volume group, add space to your LV, and resize your filesystem to use it. One problem though, you've created another point of failure for your FS (two disks) without getting anything in exchange. Yes, I agree it's a problem short of a way to mitigate the (inevitable) failure of one of the disks and hence any file system that uses all or part of a failed PV. It's not striped (you can do LV striping, but that's another discussion altogether), it's not mirrored, there's no parity. So why do it? pvmove is a pretty cool way to move every LV, online, to a new PV. But I agree LVM is overly complicated for such hypothetical benefits. Benefits that assume more knowledge on the part of the typical user than is true. It's much simpler to just backup, and restore to a new bigger disk, than to learn various LVM commands. For what it's worth, LVM2 supports its own raid0, 1, 5 and 6. Those raid levels are LV attributes. So instead of configuring different raid levels by using disk partitions, and the ensuing near impossibility (or madness) of resizing them should it be needed, this can be done on a per LV basis from a single VG. It's simpler in that there's one less layer to deal with, however it means learning totally new vernacular and monitoring methods which itself isn't exactly simple. In a server/enterprise setting I think it makes a lot more sense where you're likely to need to use LVM to span across multiple raid arrays, SANs, etc. I think LVM is pretty bad ass. During F18 pre-release, the installer team had moved to Standard Partition scheme (all ext4) by default. But for the very reasons you mention, I was opposed to LVM by default redux, but the LVM camp won that argument somehow. Another place it makes some sense is full disk encryption (i.e. not just home), where the PV/VG is encrypted, and then the LVs are drawn from that. That's simpler than separately encrypting partitions for /home and /. Assuming you want /home separate. Honestly a lot of these things get easier with Btrfs due to yet another loss of a separate layer. It's as simple to use as a plain file system without thinking of esoteric features if you don't want, but they're there should you need them: compression, much safer fs resize shrink or grow, partitioning without having to specify sizes, functional equivalent to pvmove, and even the ability to migrate specific partitions like /home to another disk, multiple device support, and of course snapshots. Plus it's also friendlier to SSD than other options. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 11:50 AM, Robert Moskowitz r...@htt-consult.com wrote: On 12/18/2013 01:32 PM, Chris Murphy wrote: On Dec 18, 2013, at 6:03 AM, Robert Moskowitz r...@htt-consult.com wrote: On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. FYI, be aware there appears to be a queued TRIM bug with the M500 where it may be causing silent data corruption. I wouldn't use discard on this, or any, SSD, in production until it's been well tested. https://bugzilla.redhat.com/show_bug.cgi?id=1024002 Seems like a workaround was posted yesterday? So since I am still waiting for the drive to show up on my porch… Yes. Although I'm uncertain whether we get queued TRIM for free with a SATA rev 3.0 controller, or if that means such drives use the SATA rev 3.0 non-queued TRIM? I'm under the impression that to get SATA rev 3.1 queued TRIM that the drive and the controller it plugs into, and libata all need to support SATA rev 3.1. So I don't actually fully understand the problem, but it sounds like a firmware bug to me. Suffice to say, with Windows having enabled TRIM by default for all SSDs, if a drive is corrupting its data, this ought to be quickly remedied with a firmware update I'd think. Until the industry gets its act together on TRIM, I think we're probably better off executing fstrim once a week with a cron job at a time the computer is likely to be idle. And what is TRIM and fstrim? Ultimately you don't need to worry about it because TRIM isn't used by default on Fedora. This is enabled with the discard mount option. As far as I know, only Ubuntu has said they will use discard by default in the near future. You can read more on TRIM on wikipedia and elsewhere if you're interested. The gist is it's a way to inform the SSD of pages that are no longer in use by the file system, i.e. deleted files, rather than files that have been overwritten. This optimization is desirable, but only if it works correctly. And right now it's not universally working correctly. fstrim is a user space program to manually issue TRIM, so it can be done when the drive is idle, and therefore negative side effects of the discard mount option aren't readily noticed - those primarily being short term performance problems that seem like a system hang for a few seconds (or in some extreme cases up to a minute or two). Where you're likely to experience a particular need for fstrim or discard is if you have a fairly full SSD, with more file delete and create workload rather than file overwrite workload. So if your SSD has a lot of unused space you're unlikely to notice SSD slow down as a result of the SSD not having many pages erased and ready for writes. It's sort of a complicated issue. Chris Murphy-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 03:09 PM, Chris Murphy wrote: On Dec 18, 2013, at 11:50 AM, Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com wrote: On 12/18/2013 01:32 PM, Chris Murphy wrote: On Dec 18, 2013, at 6:03 AM, Robert Moskowitz r...@htt-consult.com mailto:r...@htt-consult.com wrote: On 12/18/2013 04:41 AM, John Obaterspok wrote: Hello, I'm going to setup F20 with a new SSD disk (256gb Samsung 840 PRO) and was wondering about best practices for Over Provisioning during partitioning. hmmm. I just ordered a Crucial M500 256GB SSD for my new install. I thought I would have it all to work with (currently using a 320GB HD, so that is a 64GB reduction already). Are you implying here that you need to not use all of the SSD drive so that it has some swap around? I chose the M500 over the 840 based on price and reviews. The M500 uses MLC NAND compared to the 840 using TLC NAND. FYI, be aware there appears to be a queued TRIM bug with the M500 where it may be causing silent data corruption. I wouldn't use discard on this, or any, SSD, in production until it's been well tested. https://bugzilla.redhat.com/show_bug.cgi?id=1024002 Seems like a workaround was posted yesterday? So since I am still waiting for the drive to show up on my porch… Yes. Although I'm uncertain whether we get queued TRIM for free with a SATA rev 3.0 controller, or if that means such drives use the SATA rev 3.0 non-queued TRIM? I'm under the impression that to get SATA rev 3.1 queued TRIM that the drive and the controller it plugs into, and libata all need to support SATA rev 3.1. So I don't actually fully understand the problem, but it sounds like a firmware bug to me. Suffice to say, with Windows having enabled TRIM by default for all SSDs, if a drive is corrupting its data, this ought to be quickly remedied with a firmware update I'd think. My Lenovo x120e supposedly has the sata3 chipset, but only sata2 enabled. According to a few forums that I found when looking for what type of drive to buy for this laptop. Some think the sata2 option is to upsell the x220. So perhaps TRIM is even less important to me. But first I have to get f20 working reasonably on my Asus before installing on my Lenovo. And I have to figure out a few things. Not being able to specify the update repo at install was painful. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 1:38 PM, Robert Moskowitz r...@htt-consult.com wrote: My Lenovo x120e supposedly has the sata3 chipset, but only sata2 enabled. According to a few forums that I found when looking for what type of drive to buy for this laptop. Some think the sata2 option is to upsell the x220. For SSD you'll almost certainly want SATA rev 3.0 enabled. The bandwidth is 300MBs vs 600MB/s. By running SATA rev. 2 you're bandwidth limiting your hardware. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 03:44 PM, Chris Murphy wrote: On Dec 18, 2013, at 1:38 PM, Robert Moskowitz r...@htt-consult.com wrote: My Lenovo x120e supposedly has the sata3 chipset, but only sata2 enabled. According to a few forums that I found when looking for what type of drive to buy for this laptop. Some think the sata2 option is to upsell the x220. For SSD you'll almost certainly want SATA rev 3.0 enabled. The bandwidth is 300MBs vs 600MB/s. By running SATA rev. 2 you're bandwidth limiting your hardware. And sata2 is better with a HD than a SSD? All the comments I found said that Linux was seeing the drive as sata2, even though the chipset supported sata3. No workarounds, and the posts were not that old. Well we will see when the drive comes. I have been having wierd behaviour here, like audio turning off. Can't tell if it is software (old and who knows what is running now) or hardware. If f20 does not fix all the issues (USB sticks, but not drives, audio, external vga turning off then back on), it is time to get a new box. But I am budget limited and x120e is at a nice price. I will only get a 12 laptop with an eraserhead mouse button. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 1:59 PM, Robert Moskowitz r...@htt-consult.com wrote: On 12/18/2013 03:44 PM, Chris Murphy wrote: On Dec 18, 2013, at 1:38 PM, Robert Moskowitz r...@htt-consult.com wrote: My Lenovo x120e supposedly has the sata3 chipset, but only sata2 enabled. According to a few forums that I found when looking for what type of drive to buy for this laptop. Some think the sata2 option is to upsell the x220. For SSD you'll almost certainly want SATA rev 3.0 enabled. The bandwidth is 300MBs vs 600MB/s. By running SATA rev. 2 you're bandwidth limiting your hardware. And sata2 is better with a HD than a SSD? In terms of bandwidth, no difference because the drive is slower than the SATA rev2 cap, but there are other benefits to SATA rev 3.0 including some ncq enhancements and other hand waivey things. So normally, short of bugs, you should use the highest revision the drive and controller support. All the comments I found said that Linux was seeing the drive as sata2, even though the chipset supported sata3. Seems possible. You can check this with dmesg, find the SATA device note and then redo dmesg and filter with grep to find all the messages related to that drive only. Also useful for finding bugs if the driver is having problems communicating with the drive at the higher spec revision level (rare but does sometimes happen). Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On Dec 18, 2013, at 2:05 PM, Chris Murphy li...@colorremedies.com wrote: You can check this with dmesg, find the SATA device note node! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: SSD Partitioning OP/Trim recommendations
On 12/18/2013 04:09 PM, Chris Murphy wrote: On Dec 18, 2013, at 2:05 PM, Chris Murphy li...@colorremedies.com wrote: You can check this with dmesg, find the SATA device note node! Tomorrow -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
