<?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: Raid Trim support for future chip sets? in Archive</title>
    <link>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10703#M8328</link>
    <description>&lt;P&gt;It's complicated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RAID splits data blocks across drives.  When a file is marked for TRIM, the driver has to know to send the command to the right blocks across drives.  With data, you must be absolutely sure or else there is the risk of data corruption.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jun 2011 00:52:24 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2011-06-09T00:52:24Z</dc:date>
    <item>
      <title>Raid Trim support for future chip sets?</title>
      <link>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10700#M8325</link>
      <description>&lt;P&gt;Is it possible yet?&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2011 04:50:10 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10700#M8325</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-06-03T04:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: Raid Trim support for future chip sets?</title>
      <link>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10701#M8326</link>
      <description>&lt;P&gt;TRIM for RAID member support is actually a driver limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Intel has made no recent comment on this topic.     &lt;/P&gt;</description>
      <pubDate>Sat, 04 Jun 2011 02:33:37 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10701#M8326</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-06-04T02:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: Raid Trim support for future chip sets?</title>
      <link>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10702#M8327</link>
      <description>&lt;P&gt;So whats holding them back then?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 06:53:02 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10702#M8327</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-06-08T06:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: Raid Trim support for future chip sets?</title>
      <link>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10703#M8328</link>
      <description>&lt;P&gt;It's complicated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RAID splits data blocks across drives.  When a file is marked for TRIM, the driver has to know to send the command to the right blocks across drives.  With data, you must be absolutely sure or else there is the risk of data corruption.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jun 2011 00:52:24 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/raid-trim-support-for-future-chip-sets/m-p/10703#M8328</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-06-09T00:52:24Z</dc:date>
    </item>
  </channel>
</rss>

