<?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: ZFS: Threat or Menace? Pt. II</title>
	<atom:link href="http://storagemojo.com/zfs-threat-or-menace-pt-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com</link>
	<description>Data storage info &#38; analysis</description>
	<lastBuildDate>Sun, 20 May 2012 13:26:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Donald Ragbirsingh</title>
		<link>http://storagemojo.com/zfs-threat-or-menace-pt-ii/comment-page-1/#comment-206060</link>
		<dc:creator>Donald Ragbirsingh</dc:creator>
		<pubDate>Sun, 18 Oct 2009 02:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?page_id=151#comment-206060</guid>
		<description>ZFS is being adopted in preference to VXFS at my company.  We&#039;ve found some issues that demonstrate how a better understanding of ZFS is critical.  A particular application was creating and deleting files so fast that the HDS USP had terrible i/o problems on a few 400GB filesystems - the transfer was a paltry 300MB/s when it should have been at least 700MB/s.  When we disabled the ZIL - we found the culprit and the i/o went up.  This M8000 domain had four Emulex LP11002 cards and four fibre connections interleaving the PCIe bridges within a single IOU.  Admittedly - yes - ZFS is an excellent choice, but further testing showed that locating the ZFS Intent Log to a SSD would have bypassed this issue.  HDS (and other frames) don&#039;t like ZFS to dictate when they should flush their NVRAM caches - in fact - ZFS takes a sequential write and transforms it into a pure random write.  On RAID5 and RAID6 storage which is typically assigned - these luns within the internal RAID group showed high latencies.  Careful planning is required, in my case RAID10 was actually better.</description>
		<content:encoded><![CDATA[<p>ZFS is being adopted in preference to VXFS at my company.  We&#8217;ve found some issues that demonstrate how a better understanding of ZFS is critical.  A particular application was creating and deleting files so fast that the HDS USP had terrible i/o problems on a few 400GB filesystems &#8211; the transfer was a paltry 300MB/s when it should have been at least 700MB/s.  When we disabled the ZIL &#8211; we found the culprit and the i/o went up.  This M8000 domain had four Emulex LP11002 cards and four fibre connections interleaving the PCIe bridges within a single IOU.  Admittedly &#8211; yes &#8211; ZFS is an excellent choice, but further testing showed that locating the ZFS Intent Log to a SSD would have bypassed this issue.  HDS (and other frames) don&#8217;t like ZFS to dictate when they should flush their NVRAM caches &#8211; in fact &#8211; ZFS takes a sequential write and transforms it into a pure random write.  On RAID5 and RAID6 storage which is typically assigned &#8211; these luns within the internal RAID group showed high latencies.  Careful planning is required, in my case RAID10 was actually better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

