<?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: Is ZFS ready for primetime?</title>
	<atom:link href="http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/feed/" rel="self" type="application/rss+xml" />
	<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/</link>
	<description>Blog O' Matty</description>
	<lastBuildDate>Tue, 07 Feb 2012 02:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Raul Ortega</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-346673</link>
		<dc:creator>Raul Ortega</dc:creator>
		<pubDate>Sat, 22 Mar 2008 19:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-346673</guid>
		<description>I have 2 server x86 using openSolaris b81 and b74, quite some experimental, but have mor than 6 month withouth problem. b81 it&#039;s a CIFS server to 4 Wireless clients and 2 Desktops and Squid Proxy restriction, and b74 only Squid server to 20 computer. ZFS = 0 Problems.
My laptop &gt; 8 month with openSolaris = 0 Corruption. :-P</description>
		<content:encoded><![CDATA[<p>I have 2 server x86 using openSolaris b81 and b74, quite some experimental, but have mor than 6 month withouth problem. b81 it&#8217;s a CIFS server to 4 Wireless clients and 2 Desktops and Squid Proxy restriction, and b74 only Squid server to 20 computer. ZFS = 0 Problems.<br />
My laptop &gt; 8 month with openSolaris = 0 Corruption. :-P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matty</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-267964</link>
		<dc:creator>matty</dc:creator>
		<pubDate>Sun, 17 Feb 2008 20:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-267964</guid>
		<description>Hey Some guy. 

I feel your pain, and  am starting to realize more and more that you need to have the latest Solaris 10 patches applied in order to get a stable operating environment. Which Solaris 10 update (and kernel revision) are you running?

- Ryan</description>
		<content:encoded><![CDATA[<p>Hey Some guy. </p>
<p>I feel your pain, and  am starting to realize more and more that you need to have the latest Solaris 10 patches applied in order to get a stable operating environment. Which Solaris 10 update (and kernel revision) are you running?</p>
<p>- Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some guy</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-266393</link>
		<dc:creator>Some guy</dc:creator>
		<pubDate>Sun, 17 Feb 2008 07:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-266393</guid>
		<description>This is not necessarily a ZFS bug, but recently this happened with a 6TB filesystem that sees heavy use:

&lt;code&gt;
  pool: somepool
 state: ONLINE
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: http://www.sun.com/msg/ZFS-8000-8A
 scrub: scrub completed with 7 errors on Tue Feb 12 17:09:21 2008
config:

        NAME                       STATE     READ WRITE CKSUM
        somepool                  ONLINE       0     0 23.91
          c2t320000D0736EBA7Cd1s6  ONLINE       0     0 23.91

errors: The following persistent errors have been detected:

          DATASET    OBJECT     RANGE
          somepool   164910     0-131072
          5          132353a    lvl=0 blkid=0
          5          48a25df    lvl=0 blkid=0
          5          5ed1f75    lvl=0 blkid=19
          somepool   114393905  0-131072
          31         132353a    lvl=0 blkid=0
          31         48a25df    lvl=0 blkid=0
          31         4c297d7    lvl=0 blkid=0
          31         4c297d7    lvl=0 blkid=16
          31         5ed1f75    lvl=0 blkid=19
          31         633f73f    lvl=0 blkid=0
          31         68d62e7    lvl=0 blkid=1
&lt;/code&gt;

Yes, there&#039;s no redundancy. Just one vdev on top of 6TB of dumb-as-a-rock hardware RAID 5. No, that&#039;s not my doing. Sadly, this way of operating (zero-planning) is normal for the organization I work for.

Of course, it could be that it *is* a ZFS bug, because management has dictated that patches are NOT A PRIORITY AT ALL so this particular machine is six-months behind on kernel patches. Great place to work, huh?</description>
		<content:encoded><![CDATA[<p>This is not necessarily a ZFS bug, but recently this happened with a 6TB filesystem that sees heavy use:</p>
<p><code><br />
  pool: somepool<br />
 state: ONLINE<br />
status: One or more devices has experienced an error resulting in data<br />
        corruption.  Applications may be affected.<br />
action: Restore the file in question if possible.  Otherwise restore the<br />
        entire pool from backup.<br />
   see: <a href="http://www.sun.com/msg/ZFS-8000-8A" rel="nofollow">http://www.sun.com/msg/ZFS-8000-8A</a><br />
 scrub: scrub completed with 7 errors on Tue Feb 12 17:09:21 2008<br />
config:</p>
<p>        NAME                       STATE     READ WRITE CKSUM<br />
        somepool                  ONLINE       0     0 23.91<br />
          c2t320000D0736EBA7Cd1s6  ONLINE       0     0 23.91</p>
<p>errors: The following persistent errors have been detected:</p>
<p>          DATASET    OBJECT     RANGE<br />
          somepool   164910     0-131072<br />
          5          132353a    lvl=0 blkid=0<br />
          5          48a25df    lvl=0 blkid=0<br />
          5          5ed1f75    lvl=0 blkid=19<br />
          somepool   114393905  0-131072<br />
          31         132353a    lvl=0 blkid=0<br />
          31         48a25df    lvl=0 blkid=0<br />
          31         4c297d7    lvl=0 blkid=0<br />
          31         4c297d7    lvl=0 blkid=16<br />
          31         5ed1f75    lvl=0 blkid=19<br />
          31         633f73f    lvl=0 blkid=0<br />
          31         68d62e7    lvl=0 blkid=1<br />
</code></p>
<p>Yes, there&#8217;s no redundancy. Just one vdev on top of 6TB of dumb-as-a-rock hardware RAID 5. No, that&#8217;s not my doing. Sadly, this way of operating (zero-planning) is normal for the organization I work for.</p>
<p>Of course, it could be that it *is* a ZFS bug, because management has dictated that patches are NOT A PRIORITY AT ALL so this particular machine is six-months behind on kernel patches. Great place to work, huh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nelson</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-238978</link>
		<dc:creator>nelson</dc:creator>
		<pubDate>Thu, 07 Feb 2008 05:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-238978</guid>
		<description>with regards to the hang...er it&#039;s more like a deadlock.  we&#039;ve let it go and it panics cluster nodes. 

on a non clustered node i&#039;ve seen it hang for many hours (cough - overnight in fact).

during this time you can no longer log into the server but it responds to ping.  applications appear to fault.  it should be under bug 6513209 (well the IDR states that anyway)</description>
		<content:encoded><![CDATA[<p>with regards to the hang&#8230;er it&#8217;s more like a deadlock.  we&#8217;ve let it go and it panics cluster nodes. </p>
<p>on a non clustered node i&#8217;ve seen it hang for many hours (cough &#8211; overnight in fact).</p>
<p>during this time you can no longer log into the server but it responds to ping.  applications appear to fault.  it should be under bug 6513209 (well the IDR states that anyway)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: next</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-238343</link>
		<dc:creator>next</dc:creator>
		<pubDate>Wed, 06 Feb 2008 21:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-238343</guid>
		<description>&lt;i&gt;the real *busy* system causes ZFS to hang&lt;/i&gt; - I seem to be experiencing this as well. I&#039;m not sure what your &quot;hang&quot; means, in my case it looks like &lt;em&gt;nothing&lt;/em&gt; is written/read to/from the pool for several seconds. Often it takes up to two minutes.

I hope it gets solved soon now will be available as a patch.</description>
		<content:encoded><![CDATA[<p><i>the real *busy* system causes ZFS to hang</i> &#8211; I seem to be experiencing this as well. I&#8217;m not sure what your &#8220;hang&#8221; means, in my case it looks like <em>nothing</em> is written/read to/from the pool for several seconds. Often it takes up to two minutes.</p>
<p>I hope it gets solved soon now will be available as a patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nelson</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-222837</link>
		<dc:creator>nelson</dc:creator>
		<pubDate>Thu, 31 Jan 2008 08:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-222837</guid>
		<description>we&#039;ve hit the snapshot destroy bug, the real *busy* system causes ZFS to hang,  ARC cache growing and *locking* ram, san/zfs cache flushing problem and ye ol&#039; standard live upgrade zones on zfs.

1 was worked around quickly and easiler
3 and 4 were /etc/system changes
5 is waiting in 04/08
2 is (currently) an IDR fix that we&#039;re testing</description>
		<content:encoded><![CDATA[<p>we&#8217;ve hit the snapshot destroy bug, the real *busy* system causes ZFS to hang,  ARC cache growing and *locking* ram, san/zfs cache flushing problem and ye ol&#8217; standard live upgrade zones on zfs.</p>
<p>1 was worked around quickly and easiler<br />
3 and 4 were /etc/system changes<br />
5 is waiting in 04/08<br />
2 is (currently) an IDR fix that we&#8217;re testing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvaro</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-182478</link>
		<dc:creator>Alvaro</dc:creator>
		<pubDate>Wed, 02 Jan 2008 15:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-182478</guid>
		<description>please read &#039;by some bug&#039; ...</description>
		<content:encoded><![CDATA[<p>please read &#8216;by some bug&#8217; &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvaro</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-182476</link>
		<dc:creator>Alvaro</dc:creator>
		<pubDate>Wed, 02 Jan 2008 15:14:16 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-182476</guid>
		<description>I got hit but some bug that got me into a state that not even Sun support eng were able to fix it. I had Oracle running on top of  a 60gig pool, and when oracle went nuts (actually a stored procedure) the pool got 100% usage and bam... nothing else we could do. I was running 11/06... It was a development box so no harm was done, but I am staying away from this, as appealing as it looks, not production ready :-(</description>
		<content:encoded><![CDATA[<p>I got hit but some bug that got me into a state that not even Sun support eng were able to fix it. I had Oracle running on top of  a 60gig pool, and when oracle went nuts (actually a stored procedure) the pool got 100% usage and bam&#8230; nothing else we could do. I was running 11/06&#8230; It was a development box so no harm was done, but I am staying away from this, as appealing as it looks, not production ready :-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-156542</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Tue, 11 Dec 2007 21:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-156542</guid>
		<description>Well - I&#039;ve got a 6 Tb 3511 array that my organisation has spent serious $$ on, and I&#039;m using a Solaris 10u4 sparc box with zfs to drive it. 

All was going well until a week ago. It now kernel panics twice a day. zpool status reports no errors, and zpool scrub just seems to make it crash a bit more consistently (about 50% through).

Here is the error message:

panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024)

This zpool has about 200 snapshots on it.

Somehow I get the feeling that there is something going on that sun is not telling us...</description>
		<content:encoded><![CDATA[<p>Well &#8211; I&#8217;ve got a 6 Tb 3511 array that my organisation has spent serious $$ on, and I&#8217;m using a Solaris 10u4 sparc box with zfs to drive it. </p>
<p>All was going well until a week ago. It now kernel panics twice a day. zpool status reports no errors, and zpool scrub just seems to make it crash a bit more consistently (about 50% through).</p>
<p>Here is the error message:</p>
<p>panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024)</p>
<p>This zpool has about 200 snapshots on it.</p>
<p>Somehow I get the feeling that there is something going on that sun is not telling us&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/comment-page-1/#comment-155329</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Mon, 10 Dec 2007 20:46:10 +0000</pubDate>
		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/11/28/is-zfs-ready-for-primetime/#comment-155329</guid>
		<description>Mind if I ask how you&#039;re using ZFS there to have hit these bugs?  We&#039;re looking to purchase a couple of Thumpers soon, and I&#039;m wondering if these bugs something we&#039;re likely to experience?

Any idea what caused them?</description>
		<content:encoded><![CDATA[<p>Mind if I ask how you&#8217;re using ZFS there to have hit these bugs?  We&#8217;re looking to purchase a couple of Thumpers soon, and I&#8217;m wondering if these bugs something we&#8217;re likely to experience?</p>
<p>Any idea what caused them?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

