Comments on: Is ZFS ready for primetime?

By: Raul Ortega

Raul Ortega — Sat, 22 Mar 2008 19:21:39 +0000

I have 2 server x86 using openSolaris b81 and b74, quite some experimental, but have mor than 6 month withouth problem. b81 it’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 > 8 month with openSolaris = 0 Corruption. :-P

By: matty

matty — Sun, 17 Feb 2008 20:06:13 +0000

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

By: Some guy

Some guy — Sun, 17 Feb 2008 07:10:56 +0000

This is not necessarily a ZFS bug, but recently this happened with a 6TB filesystem that sees heavy use:

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

Yes, there’s no redundancy. Just one vdev on top of 6TB of dumb-as-a-rock hardware RAID 5. No, that’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?

By: nelson

nelson — Thu, 07 Feb 2008 05:07:21 +0000

with regards to the hang…er it’s more like a deadlock. we’ve let it go and it panics cluster nodes.

on a non clustered node i’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)

By: next

next — Wed, 06 Feb 2008 21:40:18 +0000

the real *busy* system causes ZFS to hang – I seem to be experiencing this as well. I’m not sure what your “hang” means, in my case it looks like nothing 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.

By: nelson

nelson — Thu, 31 Jan 2008 08:07:16 +0000

we’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’ 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’re testing