<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why we need 4k drives</title>
	<atom:link href="http://storagemojo.com/2009/12/21/why-we-need-4k-drives/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/</link>
	<description>Data storage info &#38; analysis</description>
	<lastBuildDate>Thu, 09 Sep 2010 22:00:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Brian&#8217;s Brain &#187; Blog Archive &#187; To Infinity And Beyond: Seagate Turns 3 TByte HDDs On</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-209962</link>
		<dc:creator>Brian&#8217;s Brain &#187; Blog Archive &#187; To Infinity And Beyond: Seagate Turns 3 TByte HDDs On</dc:creator>
		<pubDate>Wed, 07 Jul 2010 17:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-209962</guid>
		<description>[...] mitigating the degrading effects of raw error rates. Unfortunately, the 4 Kbyte sector size is at minimum performance- and capacity-inefficient, and worst-case completely incompatible, with legacy operating systems when the drive is directly accessed by them. By putting an [...]</description>
		<content:encoded><![CDATA[<p>[...] mitigating the degrading effects of raw error rates. Unfortunately, the 4 Kbyte sector size is at minimum performance- and capacity-inefficient, and worst-case completely incompatible, with legacy operating systems when the drive is directly accessed by them. By putting an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Ferebee, Frankfurt&#187; Blogarchiv &#187; 1 TB im MacBook Pro</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-208898</link>
		<dc:creator>Chris Ferebee, Frankfurt&#187; Blogarchiv &#187; 1 TB im MacBook Pro</dc:creator>
		<pubDate>Fri, 02 Apr 2010 12:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-208898</guid>
		<description>[...] Ich verwende die Western Digital WD10TPVT, nachdem die ursprünglich angekündigte WD10TEVT nie in Stückzahlen ausgeliefert wurde. Die WD10TPVT unterscheidet sich durch eine leicht geringere Umdrehungsgeschwindigkeit (5200 UpM statt 5400) und der neuen 4K-Sektorgröße, die für moderne Betriebssysteme nur Vorteile bringt, z. B. eine bessere Fehlerkorrektur. [...]</description>
		<content:encoded><![CDATA[<p>[...] Ich verwende die Western Digital WD10TPVT, nachdem die ursprünglich angekündigte WD10TEVT nie in Stückzahlen ausgeliefert wurde. Die WD10TPVT unterscheidet sich durch eine leicht geringere Umdrehungsgeschwindigkeit (5200 UpM statt 5400) und der neuen 4K-Sektorgröße, die für moderne Betriebssysteme nur Vorteile bringt, z. B. eine bessere Fehlerkorrektur. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Block alignment is critical &#124; CTI Strategy Blog</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-208814</link>
		<dc:creator>Block alignment is critical &#124; CTI Strategy Blog</dc:creator>
		<pubDate>Fri, 26 Mar 2010 23:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-208814</guid>
		<description>[...] that is often overlooked in storage. I read a blog entry by Robin Harris a couple months back about the importance of block alignment with the new 4KB  drives. I was curious to test the theory on one of the new 4KB drives, but I did not have one on hand. [...]</description>
		<content:encoded><![CDATA[<p>[...] that is often overlooked in storage. I read a blog entry by Robin Harris a couple months back about the importance of block alignment with the new 4KB  drives. I was curious to test the theory on one of the new 4KB drives, but I did not have one on hand. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvin</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-208570</link>
		<dc:creator>Alvin</dc:creator>
		<pubDate>Thu, 11 Mar 2010 08:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-208570</guid>
		<description>Actually, using 4k-sector format drives is strongly motivated by two major persectives which the conventional 512Byte (half-k sector format) drive is far lagged behand:

1. Disk format efficiency improvement by about 10% capacity increase - each sector starts with disk preamble data that has no user information but presents least information necessary for disk manufactorers. using larger sector format, i.e. 4k sector format, has saved 7 such gap space for storing user data per 4096-Byte sector that the conventional 512Byte sector drive cannot save, which largely yields extra recording spaceds for user, given the same density is applied. In WD drives, users should not notice any difference.
2. Using 4k sector format drive not only increases the conventional RS-ECC correction capability, but is potentially replacing the RS-ECC with the new revolutional LDPC code technology, which will provide significant disk drive URE performance. For instance, given URE of every 1 of 10^14 bit data read in conventional RS-ECC, by using LDPC and 4k sector format, the drive can easily go down to every 1 of 10^22 URE. This will translate into a huge benefit to users, Os and HDD industries with new technologies in head and media as well. In the end, parameers such as AFR, SMART and MTBF will be largely improved. RAID-x configuration may be rethought with these new gerneration high-performance drives.</description>
		<content:encoded><![CDATA[<p>Actually, using 4k-sector format drives is strongly motivated by two major persectives which the conventional 512Byte (half-k sector format) drive is far lagged behand:</p>
<p>1. Disk format efficiency improvement by about 10% capacity increase &#8211; each sector starts with disk preamble data that has no user information but presents least information necessary for disk manufactorers. using larger sector format, i.e. 4k sector format, has saved 7 such gap space for storing user data per 4096-Byte sector that the conventional 512Byte sector drive cannot save, which largely yields extra recording spaceds for user, given the same density is applied. In WD drives, users should not notice any difference.<br />
2. Using 4k sector format drive not only increases the conventional RS-ECC correction capability, but is potentially replacing the RS-ECC with the new revolutional LDPC code technology, which will provide significant disk drive URE performance. For instance, given URE of every 1 of 10^14 bit data read in conventional RS-ECC, by using LDPC and 4k sector format, the drive can easily go down to every 1 of 10^22 URE. This will translate into a huge benefit to users, Os and HDD industries with new technologies in head and media as well. In the end, parameers such as AFR, SMART and MTBF will be largely improved. RAID-x configuration may be rethought with these new gerneration high-performance drives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IBM legacy BIOS</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207338</link>
		<dc:creator>IBM legacy BIOS</dc:creator>
		<pubDate>Sun, 27 Dec 2009 05:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207338</guid>
		<description>The link provided by Karl makes a valid point about DOS/BIOS based partition tables for x86.  An issue some SAN/VMWare environments suffer from as well.

This misalignment can cut peak IOPs in half or more.

Still waiting for EFI ( http://en.wikipedia.org/wiki/Extensible_Firmware_Interface )  motherboards with GUID partition table support (http://en.wikipedia.org/wiki/GUID_Partition_Table ) to take off :(</description>
		<content:encoded><![CDATA[<p>The link provided by Karl makes a valid point about DOS/BIOS based partition tables for x86.  An issue some SAN/VMWare environments suffer from as well.</p>
<p>This misalignment can cut peak IOPs in half or more.</p>
<p>Still waiting for EFI ( <a href="http://en.wikipedia.org/wiki/Extensible_Firmware_Interface" rel="nofollow">http://en.wikipedia.org/wiki/Extensible_Firmware_Interface</a> )  motherboards with GUID partition table support (<a href="http://en.wikipedia.org/wiki/GUID_Partition_Table" rel="nofollow">http://en.wikipedia.org/wiki/GUID_Partition_Table</a> ) to take off <img src='http://storagemojo.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Katzke</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207312</link>
		<dc:creator>Karl Katzke</dc:creator>
		<pubDate>Thu, 24 Dec 2009 04:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207312</guid>
		<description>The 4k thing is also sort of screwing over &lt;a href=&quot;http://blog.fosketts.net/2009/12/23/drobo-xp-beware-4k-advanced-format-drives/&quot; rel=&quot;nofollow&quot;&gt;Drobo users too&lt;/a&gt;... funny that I saw these two posts on the same day!</description>
		<content:encoded><![CDATA[<p>The 4k thing is also sort of screwing over <a href="http://blog.fosketts.net/2009/12/23/drobo-xp-beware-4k-advanced-format-drives/" rel="nofollow">Drobo users too</a>&#8230; funny that I saw these two posts on the same day!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drobo, XP Users: Beware of 4K &#8220;Advanced Format&#8221; Drives! &#8211; Stephen Foskett, Pack Rat</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207310</link>
		<dc:creator>Drobo, XP Users: Beware of 4K &#8220;Advanced Format&#8221; Drives! &#8211; Stephen Foskett, Pack Rat</dc:creator>
		<pubDate>Wed, 23 Dec 2009 21:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207310</guid>
		<description>[...] StorageMojo: Why we need 4k drives [...]</description>
		<content:encoded><![CDATA[<p>[...] StorageMojo: Why we need 4k drives [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gonzio</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207307</link>
		<dc:creator>gonzio</dc:creator>
		<pubDate>Wed, 23 Dec 2009 16:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207307</guid>
		<description>Clariion uses 520 bytes sectors, but 8 of those bytes are used internally by the storage to store a time stamp and a checksum to ensure data integrity. The host only sees the 512 bytes sectors, so it is the same as with internal disks.</description>
		<content:encoded><![CDATA[<p>Clariion uses 520 bytes sectors, but 8 of those bytes are used internally by the storage to store a time stamp and a checksum to ensure data integrity. The host only sees the 512 bytes sectors, so it is the same as with internal disks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207306</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 23 Dec 2009 15:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207306</guid>
		<description>The presumption of this is that existing data will be reformatted to 4k sector file systems, and that 512 emulation on 4k will offer as good or better performance.  Both are huge assumptions not likely to be true at the 90% level for years.</description>
		<content:encoded><![CDATA[<p>The presumption of this is that existing data will be reformatted to 4k sector file systems, and that 512 emulation on 4k will offer as good or better performance.  Both are huge assumptions not likely to be true at the 90% level for years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207300</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 23 Dec 2009 02:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207300</guid>
		<description>Yes... Clariion uses 520 byte sectors.  Secondly, UBE of Enterprise FC and SATA is 1 in 10 to the 15th, not 1 in 10 to the 14th.  That&#039;s a *real* important distinction... If the 400 bytes of ECC on 4096 byte sector greatly increases reliability, I&#039;m all for it.  The extra 8 bytes on 512 bytes, hasn&#039;t impressed me ;-)</description>
		<content:encoded><![CDATA[<p>Yes&#8230; Clariion uses 520 byte sectors.  Secondly, UBE of Enterprise FC and SATA is 1 in 10 to the 15th, not 1 in 10 to the 14th.  That&#8217;s a *real* important distinction&#8230; If the 400 bytes of ECC on 4096 byte sector greatly increases reliability, I&#8217;m all for it.  The extra 8 bytes on 512 bytes, hasn&#8217;t impressed me <img src='http://storagemojo.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin K. Petersen</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207299</link>
		<dc:creator>Martin K. Petersen</dc:creator>
		<pubDate>Tue, 22 Dec 2009 18:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207299</guid>
		<description>Linux has supported devices with native 4KB sectors for a long time. As far as drives with 512-byte logical and 4KB physical sectors is concerned the support was included in the 2.6.31 kernel. Our partitioning and LVM tools have been updated to compensate for the alignment reported by drive (ATA and SCSI). I think Fedora is the only distribution that ships the relevant bits at this point.

It is hard for a general purpose operating system to deal with buffer sizes that are not multiples of 512 in an efficient manner. So 520/528-byte sector drives have mostly been used inside RAID arrays. The extra bytes are used to store information proprietary to the array firmware.

Linux does support 520/4106-byte sector drives, but only when they are formatted using T10 Protection Information (DIF) and hanging off a DIF or DIX-capable HBA.</description>
		<content:encoded><![CDATA[<p>Linux has supported devices with native 4KB sectors for a long time. As far as drives with 512-byte logical and 4KB physical sectors is concerned the support was included in the 2.6.31 kernel. Our partitioning and LVM tools have been updated to compensate for the alignment reported by drive (ATA and SCSI). I think Fedora is the only distribution that ships the relevant bits at this point.</p>
<p>It is hard for a general purpose operating system to deal with buffer sizes that are not multiples of 512 in an efficient manner. So 520/528-byte sector drives have mostly been used inside RAID arrays. The extra bytes are used to store information proprietary to the array firmware.</p>
<p>Linux does support 520/4106-byte sector drives, but only when they are formatted using T10 Protection Information (DIF) and hanging off a DIF or DIX-capable HBA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dali</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207298</link>
		<dc:creator>Dali</dc:creator>
		<pubDate>Tue, 22 Dec 2009 16:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207298</guid>
		<description>Great in depth article from Anandtech covering the need for 4K sectors, the issues and the workarounds.

http://www.anandtech.com/storage/showdoc.aspx?i=3691</description>
		<content:encoded><![CDATA[<p>Great in depth article from Anandtech covering the need for 4K sectors, the issues and the workarounds.</p>
<p><a href="http://www.anandtech.com/storage/showdoc.aspx?i=3691" rel="nofollow">http://www.anandtech.com/storage/showdoc.aspx?i=3691</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: holger</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207296</link>
		<dc:creator>holger</dc:creator>
		<pubDate>Tue, 22 Dec 2009 09:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207296</guid>
		<description>I think several vendors of raid boxes use a 520 byte formatting *internally* to store extra metadata there.
Even good old VMS presented 512 bytes to the user but used the additional bytes for storing the &quot;forced error flag&quot;.</description>
		<content:encoded><![CDATA[<p>I think several vendors of raid boxes use a 520 byte formatting *internally* to store extra metadata there.<br />
Even good old VMS presented 512 bytes to the user but used the additional bytes for storing the &#8220;forced error flag&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate</title>
		<link>http://storagemojo.com/2009/12/21/why-we-need-4k-drives/comment-page-1/#comment-207289</link>
		<dc:creator>nate</dc:creator>
		<pubDate>Mon, 21 Dec 2009 18:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1749#comment-207289</guid>
		<description>It seems EMC uses 520 bytes, not sure if anyone else does - http://chucksblog.emc.com/chucks_blog/2008/08/your-storage-mi.html

Also I think the file system block size is related? In that if your drive has 512-byte sectors and your file system is using 4096-byte blocks then you&#039;ll probably be more efficient with a 4k physical sector? I don&#039;t recall the last time linux was able to use a 512-byte file system block size(man page says supported values are 1-4k), I think the default with most larger file system sizes is 4k today already(on linux at least).

On my big storage array the average I/O size is about 37kB( to disk, over 100kB to cache).</description>
		<content:encoded><![CDATA[<p>It seems EMC uses 520 bytes, not sure if anyone else does &#8211; <a href="http://chucksblog.emc.com/chucks_blog/2008/08/your-storage-mi.html" rel="nofollow">http://chucksblog.emc.com/chucks_blog/2008/08/your-storage-mi.html</a></p>
<p>Also I think the file system block size is related? In that if your drive has 512-byte sectors and your file system is using 4096-byte blocks then you&#8217;ll probably be more efficient with a 4k physical sector? I don&#8217;t recall the last time linux was able to use a 512-byte file system block size(man page says supported values are 1-4k), I think the default with most larger file system sizes is 4k today already(on linux at least).</p>
<p>On my big storage array the average I/O size is about 37kB( to disk, over 100kB to cache).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
