<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SSD Over Provisioning in Archive</title>
    <link>https://community.solidigm.com/t5/archive/ssd-over-provisioning/m-p/15195#M9873</link>
    <description>&lt;P&gt;There is another way for over-provisioning as well.... just don't fill the drive up! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMO, this is the best way since it allows the greatest flexibility.  Sometimes, you may temporarily need that extra space.  You can set a quota in the OS to warn you if you exceed a subjective limit.  An enforced over-provisioning is really only needed if you have some unmanaged servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, you are correct.  If you create a 60GB parition on a 80GB array, that would be a 20GB over-provisioning (which is excessive for common desktop usage).&lt;/P&gt;</description>
    <pubDate>Wed, 28 Sep 2011 17:47:20 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2011-09-28T17:47:20Z</dc:date>
    <item>
      <title>SSD Over Provisioning</title>
      <link>https://community.solidigm.com/t5/archive/ssd-over-provisioning/m-p/15194#M9872</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This article discusses over-provisioning an SSD&lt;/P&gt;&lt;P&gt;&lt;A href="http://cache-www.intel.com/cd/00/00/45/95/459555_459555.pdf" rel="nofollow noopener noreferrer"&gt;http://cache-www.intel.com/cd/00/00/45/95/459555_459555.pdf&lt;/A&gt; &lt;A href="http://cache-www.intel.com/cd/00/00/45/95/459555_459555.pdf" rel="nofollow noopener noreferrer"&gt;http://cache-www.intel.com/cd/00/00/45/95/459555_459555.pdf&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Essentially the article indicates two methods for over-provisioning:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Using the SET MAX ADDRESS command&lt;/P&gt;&lt;P&gt;2) Defining a partition that is smaller than the capacity of the drive&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm wondering if, in a RAID 0 configuration, there isn't a THIRD option that achieves this as well, and that is defining a RAID array that is smaller than the sum of the two drives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my situation I have two x25v 40GB SSD's in a RAID 0, so if for example I defined a RAID 0 array at 60GB does this achieve the same thing as options 1 or 2 and will the SSD's see this unused portion and use it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Greg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2011 15:42:09 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/ssd-over-provisioning/m-p/15194#M9872</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-28T15:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSD Over Provisioning</title>
      <link>https://community.solidigm.com/t5/archive/ssd-over-provisioning/m-p/15195#M9873</link>
      <description>&lt;P&gt;There is another way for over-provisioning as well.... just don't fill the drive up! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMO, this is the best way since it allows the greatest flexibility.  Sometimes, you may temporarily need that extra space.  You can set a quota in the OS to warn you if you exceed a subjective limit.  An enforced over-provisioning is really only needed if you have some unmanaged servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, you are correct.  If you create a 60GB parition on a 80GB array, that would be a 20GB over-provisioning (which is excessive for common desktop usage).&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2011 17:47:20 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/ssd-over-provisioning/m-p/15195#M9873</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-28T17:47:20Z</dc:date>
    </item>
  </channel>
</rss>

