Slashdot Mirror


NetApp Threatens Sellers of Appliances Running ZFS

eldavojohn writes "ZFS is licensed under the CDDL and is considered to be open source, but NetApp is sending threatening legal letters to startups who look to offer ZFS on NAS appliances. This assault on Coraid has a few people worried about the future of ZFS as NetApp rears its ugly head yet again. The CEO of Coraid replied to NetApp's demands, saying, 'We made the decision to suspend shipment after receiving a legal threat letter from NetApp Inc., suggesting that the open-source ZFS file system planned for inclusion with our EtherDrive Z-Series infringes NetApp patents.' Will NetApp effectively destroy any future ZFS might have enjoyed?"

231 comments

  1. why? by pak9rabid · · Score: 2, Insightful

    Wait...doesn't the filesystem get created by the user of the storage device? I.E., the storage system gets hooked up to your system(s), the OS sees them as raw block devices, then the user generally puts the filesystem on top of the block device.....is this not the way the EtherDrives work?

    1. Re:why? by natehoy · · Score: 4, Informative

      What you say is true for LOCAL storage, but EtherDrives are NAS (Network Attached Storage) as mentioned in the summary.

      This means they come preformatted, but the machines that access the storage are using Samba or Windows File Sharing or whatever to access it, so the client PCs do not see the filesystem on the NAS box.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    2. Re:why? by mrchaotica · · Score: 1

      This means they come preformatted

      Solution: make it format itself the first time the end user turns it on.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:why? by natehoy · · Score: 1

      You're still sending the tools to create the filesystem on the unit.

      Real solution would be to pick a filesystem that is supported by your hardware AND is unencumbered by asshattery. There are plenty of those lying about. But ZFS probably gives them some extra storage management capabilities.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    4. Re:why? by pak9rabid · · Score: 1

      OK...seeing as how Linux doesn't have kernel support for ZFS, who were they planning on marketing this to, the Solaris and BSD shops? Seems like a bad idea to sell a NAS device that isn't compatible with the most popular server OS.

    5. Re:why? by pak9rabid · · Score: 2, Insightful

      Ugh..nevermind..I misread that...me = stupid.

    6. Re:why? by overlordofmu · · Score: 1

      Nice! I am stupid too! It is good to know I am not alone.

    7. Re:why? by Anonymous Coward · · Score: 0

      Actually, that is not true. On a NetApp filer a LUN is a file that sits on their WAFL FS inside a volume that resides in an aggregate. The host that connects to that LUN will format that LUN with whatever their native FS is, but that is still sitting on top of the WAFL FS as a file.

    8. Re:why? by natehoy · · Score: 5, Informative

      I know you've already replied that you misunderstood, but just in case anyone else is confused by this...

      This is a NAS, which is itself a server. Support for the filesystem is built into the NAS box. The NAS box then exposes the data it stores on that filesystem to the network using network-appropriate protocols.

      Anyone wanting to access it would use a networking standard like Samba, Windows File Sharing, FTP, or whatever services the NAS box allows.

      Of course, they'd also access the management tools (nowadays generally a small web server also built into the NAS box).

      None of the clients would need to support the underlying filesystem that the NAS box uses. In fact, they wouldn't even be allowed to know what that filesystem is.

      Back when I had Windows boxes at home, they had absolutely no problems reading shares I made on my Linux box. The Linux box could be formatted ext, Reiser, or anything I wanted that Linux supported.

      As long as I never tried to take a hard drive out of the Linux box and put it in the Windows box, of course. Then it becomes local storage, and Windows would have to support the filesystem in order to read it.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    9. Re:why? by natehoy · · Score: 1

      True as far as it goes, but you're refuting something I never said.

      We're not talking about NetApp devices here (which you have, as far as I know, accurately described), we're talking about the target of their lawsuit, Coraid, and the product they are making that is the cause of the suit.

      Coraid is selling a NAS called the EtherDrive Z-Series which uses ZFS as its underlying filesystem. That filesystem is not exposed to anything but the EtherDrive, because the EtherDrive is a NAS solution.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    10. Re:why? by Thud457 · · Score: 1

      Real solution would be to pick a filesystem that is supported by your hardware AND is unencumbered by asshattery.

      I guess that rules out ReiserFS, then.

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    11. Re:why? by natehoy · · Score: 1

      Oh, yeah. I should have been more specific...

      ...pick a filesystem that is supported by your hardware AND is unencumbered by patent-troll asshattery

      FTFM (Fixed That For Me).

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    12. Re:why? by mysidia · · Score: 4, Informative

      ZFS is not encumbered by asshattery any more than Linux is.

      It's encumbered by a patent dispute

      While Linux is encumbered by the SCO mess, which is basically the same thing, except related to copyrights and ownership of codes, rather than ownership of the whole concept of copy on write.

    13. Re:why? by mysidia · · Score: 1

      He is talking about NAS, so it's 100% true.

      Devices that expose block devices, to which multiple clients connect using Fiber Channel, iSCSI, AoE, FCoE, SAS, SCSI, SRP, iSER, etc.

      Are called SANS not NAS.

      A NAS is a potentially more complicated device that actually hides the block device from the clients accessing it, using a protocol such as NFS or CIFS.

      As far as SANs go, some of them have an underlying filesystem, that the LUN is a file on, some of them do not, and provide other mechanisms of partitioning the storage.

      In that case, the client connecting to a SAN still only needs to know 2 things about the storage unit (1) the protocol, and (2) how to use any block device (whether local or remote)

      If it's a shared LUN, then it needs to know about the locking protocol.

      Just in the same way as a client connecting to a NAS only needs to know (1) the protocol that provides access, (2) how to work with files on any file system (whether local or remote)

      In addition, if multiple clients can connect to a NAS device, each client needs to be aware of the proper locking protocols to use (much in the way as multiple processes running at the same time on one computer need to be aware of locking protocols to write to shared files or databases).

    14. Re:why? by s73v3r · · Score: 2, Funny

      Too bad. That product would have been killer.

    15. Re:why? by jbengt · · Score: 1

      While Linux is encumbered by the SCO mess, except related to copyrights and ownership of codes, . . .

      Have you not been paying attention or do you not understand what encumbered means?
      SCO owns nothing, even it Unix copyrights could encumber Linux. (hint: nobody has found any reasonable evidence of Linux infringement of Unix copyrights)

    16. Re:why? by troll8901 · · Score: 1

      Speaking of EtherDrives, it appears from Wikipedia that they don't connect using SMB, or anything that is TCP/IP based. They use another protocol called ATA over Ethernet.

      Not sure about Coraid's or NetApp's line of products, though.

    17. Re:why? by troll8901 · · Score: 1

      AH! My mistake. You're talking about the STORAGE SERVERS, not the individual drives.

      Duh! I'm such an in-duh-vidual. Timeout for me! *blushing furiously and hiding*

    18. Re:why? by makomk · · Score: 1

      That's no solution. It'll avoid legal problems with NetApp, but part of the reason NetApp are suing Sun is that Sun owns patents on core RAID techniques (and a whole bunch of other NAS-related stuff) and are quite willing to use them.

    19. Re:why? by drinkypoo · · Score: 1

      Back when I had Windows boxes at home, they had absolutely no problems reading shares I made on my Linux box. The Linux box could be formatted ext, Reiser, or anything I wanted that Linux supported.

      Back in 1995 I maintained a Compaq 486 (at least a DX I think) which was www.circus.com. It was not only the web server and shell account machine (for six residents of a house) but also the internet gateway. Further, it was both a SMB and AppleTalk server, using samba and netatalk, and was simultaneously sharing files and printers to MacOS 7, Windows 3.1, and Unix (like my Sun 4/260) clients. All filesystems were ext2 and filesharing between all clients worked as close to flawlessly as you might imagine.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:why? by Bungie · · Score: 1

      Whoa calm down! It doesn't matter if Linux actually infringes or not, corporations will still be leary about adoption as long as there are claims out there that it does. That it is the exact definition of encumbered, the adoption of Linux is impeded by a heavy load, that being the bad publicity from the SCO and Microsoft/Novell fiascos.

      Do you remember this issue, when there was a BSD driver that was included in Linux and was re-licenced as GPL by mistake? Or how about this one, where the OpenBSD project stripped the comments from a GPL'd driver and re-licensed it as BSD? Obviously there are some copyright issues slipping through the cracks even among the different OSS projects. Since Linux has so many contributors from so many different places, it is easy for a company to start spreading claims that one piece, somewhere, might be infringing.

      As soon as the corporate lawyers get wind of that kind of thing, they'll push to avoid adoption and to migrate solutions away from Linux. Look at the Unisys LZW patent in GIF files or the Fraunhofer patents in MP3 files. Companies were panicking because they might have an MP3 stored somewhere, without any understanding of the actual issue.

      --
      The clash of honour calls, to stand when others fall.
    21. Re:why? by Bungie · · Score: 1

      There are some times when the underlying file system can matter, but the file sharing server must be aware of the limitations and deal with the problem transparently. If it doesn't, it can cause a lot of problems.

      File streams are a pretty annoying problem when the underlying file system doesn't support them. Microsoft also stopped storing metadata in alternate data streams because people would copy them to file shares and would sometimes lose the ADS data. AppleShare is an even worse nightmare because many file systems strip the resource fork. Netatalk for Linux intelligently stores the streams as separate directories so they will work on file systems like ext2. Microsoft's Services for Macintosh doesn't do this kind of thing and will only work properly on NTFS which can store them directly in alternate data streams, which FAT doesn't support.

      There are also various file permissions and attributes which depend on the file system. Newer versions of Windows file sharing supports NTFS style file/folder ACL's and Volume Shadow Copies which are not implemented the same on many other file systems. AppleTalk also expects all of the various bits of extra information stored on an HFS volume (like the file type and creator mappings).

      It appears to me that the design and features of ZFS allow it to easily support the features of other file systems without a lot of extra work. If you had the NAS running something like ext3, I think the file servering services would probably have to do a lot more work translating those features to work correctly.

      --
      The clash of honour calls, to stand when others fall.
  2. in the spirit of full disclosure.... by gandhi_2 · · Score: 1

    NetApp frequently advertises with slashdot.

    NetApp owns the idea of ZFS + NAS? The old "x on the internet" patent attack, eh?

    1. Re:in the spirit of full disclosure.... by Anonymous Coward · · Score: 0

      More bullshit from the rotting corpse that SCO^H^H^HNetApp is

    2. Re:in the spirit of full disclosure.... by PowerEdge · · Score: 1

      Yes. Cause NetApp is losing marketshare, dwindling even. Oh wait. It is 2nd only to EMC.

    3. Re:in the spirit of full disclosure.... by fuzzyfuzzyfungus · · Score: 2, Interesting

      I suspect that they are going after NAS vendors simply because the NAS vendors are a more direct threat to their business.

      NetApp probably doesn't like that Sun, now Oracle, is using "their" features in direct-attached storage for Solaris boxes; but NetApp doesn't sell direct attached storage, so that isn't as much their problem(and Larry's lawyers are probably scary).

      If, on the other hand, the world starts sprouting outfits who are combining CDDL software+commodity disks+commodity NICs+modestly custom 'lots of SAS/SATA and redundant PSUs' chassis, NetApp suddenly has a whole bunch of competitors who can undercut them good and hard. That won't mean instant death or anything; but it certainly isn't good news for them.

  3. Maybe not.. by matt-fu · · Score: 1

    Maybe not NetApp so much as Oracle.

  4. If it really does infringe... by hilather · · Score: 1

    They should go after Oracle/Sun and stop threatening people using the file system. Shenanigans!

    1. Re:If it really does infringe... by hilather · · Score: 2, Informative

      They should go after Oracle/Sun and stop threatening people using the file system. Shenanigans!

      After actually reading the article (I know what was I thinking right?), it does mention that NetApp Filed a lawsuit against Sun back in 2007..

    2. Re:If it really does infringe... by jythie · · Score: 3, Interesting

      And if I understood correctly, were not the patents involved in the lawsuit mostly invalidate?

    3. Re:If it really does infringe... by FictionPimp · · Score: 1

      And I have a iscsi/NFS/samba sun device in my server room that runs on ZFS....go figure.

    4. Re:If it really does infringe... by Anonymous Coward · · Score: 0

      Just a casual observation from a lowly citizen's view but apparently the American legal system and patent law no longer functions on principles of validity. Why would any judge make a decision factoring in the common good when the system is now tied to corporate and financial interests?

  5. Boycott by Improv · · Score: 5, Interesting

    We need a site to organise boycotts of companies that abuse the patent, trademark, or copyright system. Not everyone would need to sign on to all of them, but anyone should be able to post a call and explain their reasoning. If we got enough techies onto it who would use it at work, it could have some muscle.

    --
    For every problem, there is at least one solution that is simple, neat, and wrong.
    1. Re:Boycott by Grishnakh · · Score: 1

      How many techies actually make purchasing decisions at their workplaces? Not many. Most are made by high-up managers, under advice from sales reps.

    2. Re:Boycott by Old97 · · Score: 1

      I have a patent on such sites.

      --
      Very often, people confuse simple with simplistic. The nuance is lost on most. - Clement Mok
    3. Re:Boycott by h4rr4r · · Score: 1

      I do, if it was that way I would go find a new job in short order. Those folks do not have the knowledge to be making those decisions.

    4. Re:Boycott by oldspewey · · Score: 1

      Although there's no rational justification for it to happen, I somehow think the end result would be your boycott website being issued a DMCA takedown notice.

      --
      If libertarians are so opposed to effective government, why don't they all move to Somalia?
    5. Re:Boycott by shutdown+-p+now · · Score: 2, Insightful

      We need a site to organise boycotts of companies that abuse the patent, trademark, or copyright system. Not everyone would need to sign on to all of them, but anyone should be able to post a call and explain their reasoning.

      It's called Slashdot.

      If we got enough techies onto it who would use it at work, it could have some muscle.

      Practice has shown that you won't get enough techies that are actually in charge of software/hardware purchase decisions on any scale sufficient for it to have some muscle.

    6. Re:Boycott by bill_kress · · Score: 0, Offtopic

      Boycotts don't work when the percentage of the "Purchasing" population that cares significantly outweighs the percentage that cares. No matter how hard you protest, you will never get to every idiot out there.

      I think it would be interesting to create a 401K/IRA fund where tech workers can invest into the fund, the fund buys up significant percentage of the stock in a given company, changes it's policies and then backs down slowly to attack another company.

      As a group, the investors could target specific problem companies to go after and vote for policies they want implemented. If their policies are workable, they may even increase the rate of growth of their investments.

      In the same way, employees paid bonuses in stock could pull their stock to enable at least partial control over the company they work for (although it is pretty rare for companies to hand out voting stock to employees, probably for just this reason).

    7. Re:Boycott by Bert64 · · Score: 1

      Unfortunately, those folks make the purchasing decisions in most organizations...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    8. Re:Boycott by Grishnakh · · Score: 2, Insightful

      Of course they do. They are much better qualified to make purchasing decisions than the low-level people who will be working with the products selected. After all, the sales reps from places like NetApp told them that their expensive products are better, over expensive dinners with wine. Who do you think you are, someone important?

    9. Re:Boycott by Improv · · Score: 1

      That might be interesting, although the fiduciary duty would often compete with the value-based decisions - I would not claim that being a jerk is not profitable, even as I wish to impose enough costs on being a jerk that the more egrarious ways to be one are not done lightly or predictably. Also, this could be very expensive at times - if we wanted to buy enough stock in Amazon or Apple to penalise them for their stupid patent abuses, how expensive might that be? Could a company use predictable buyup of shares to its benefit somehow?

      I would rather help reputation reliably work by imbuing the people with better memories and organisation.

      --
      For every problem, there is at least one solution that is simple, neat, and wrong.
    10. Re:Boycott by jeffasselin · · Score: 0, Offtopic

      About the only organisation that never abused any of those is probably the Catholic Church. Unfortunately they support pedophiles, sexual abusers, and asking for favors from invisible friends in the sky.

      --
      If he explores all forms and substances Straight homeward to their symbol-essences; He shall not die.
    11. Re:Boycott by sglewis100 · · Score: 4, Insightful

      How many techies actually make purchasing decisions at their workplaces? Not many. Most are made by high-up managers, under advice from sales reps.

      Where on earth do you work, and can you find better? I'm not currently in a decision making role, although I have been, but I am in a role where I help gather requirements, evaluation specifications, invite vendors for product demos, work on getting evals / visiting labs / visiting and talking with other customers, review quotes, beat up reps on pricing, make a formal recommendation, and wait for my boss to get it done. We have a purchasing department... but they just purchase things they are told to. We also have a CFO, but if we're doing our diligence, and meeting our budget, he's not often overruling us.

    12. Re:Boycott by Vellmont · · Score: 1


      No matter how hard you protest, you will never get to every idiot out there.

      You seem to misunderstand both the nature of boycotts, and business.

      Business makes decisions almost purely on money. Boycotts are an attempt to cost the company money. Even losing 10% market share is a significant revenue hit to a company. So no, you don't need anywhere even near every idiot out there. You don't even need > 50%. You just need enough percentage for the leaders of the business to decide it's cheaper to just give in to the boycott.

      --
      AccountKiller
    13. Re:Boycott by smi.james.th · · Score: 1

      If someone organises that, I'm in.

      --
      One thing I know, and that is that I am ignorant...
  6. So, what happened? by somaTh · · Score: 2, Interesting

    The Wikipedia article on NetApp talks about them bringing a suit against Sun/ZFS and that Sun countersued, but doesn't mention the verdict. What happened there and why isn't the verdict applying here?

    --
    Nostalgia isn't what it used to be.
    1. Re:So, what happened? by brion · · Score: 4, Informative
      --

      Chu vi parolas Vikipedion?

    2. Re:So, what happened? by futuresheep · · Score: 1

      Netapp is losing, but it's not quite over: http://www.sun.com/lawsuit/zfs/

  7. ZFS was developed and trademarked by Sun by Ritz_Just_Ritz · · Score: 0

    Given that ZFS was developed and trademarked by Sun, on what grounds does Netapp have any leg to stand on here? This is crazy.

    1. Re:ZFS was developed and trademarked by Sun by dnaumov · · Score: 2, Interesting

      Easy. NetApp sues a small vendor, wins and then uses this win as leverage in their battle against Oracle.

    2. Re:ZFS was developed and trademarked by Sun by Junta · · Score: 2, Informative

      NetApp invented WAFL before ZFS. They claim ZFS itself infringes on WAFL technology.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:ZFS was developed and trademarked by Sun by BabyDave · · Score: 1

      It's about patents - NetApp claim that ZFS contains their patented technology (that NetApp incorporated into their WAFL filesystem).

    4. Re:ZFS was developed and trademarked by Sun by Technonotice_Dom · · Score: 1

      Given that ZFS was developed and trademarked by Sun, on what grounds does Netapp have any leg to stand on here? This is crazy.

      NetApp aren't disputing that Sun developed ZFS or have a trademark on the name. This is a patent case that alleges Sun, in developing the ZFS implementation have violated patents that NetApp holds on technologies. Sure, don't RTFA, but try getting to the end of the summary.

    5. Re:ZFS was developed and trademarked by Sun by h4rr4r · · Score: 1

      Nothing WAFL does was not done before, they just use do it on cheaper hardware.

    6. Re:ZFS was developed and trademarked by Sun by Galactic+Dominator · · Score: 2, Interesting

      Yes but Berkley invented FFS before WAFL. While not patented, WAFL implements many of the features of found in FFS eg cheap snapshots, meta-data structure(which allow WAFL to work as it does), etc.

      Both WAFL and ZFS are a fork of ideas and methods used in FFS. I don't know the nature of the patents NetApp holds, but if they are these features which ZFS implements then it would be terrible shame if they were able to control this market. That jeopardizes all similar FS's like HammerFS, and which ever linux fs is the next promised saviour as these are becoming more of a requirement than option.

      --
      brandelf -t FreeBSD /brain
    7. Re:ZFS was developed and trademarked by Sun by colinrichardday · · Score: 1

      Are they going to sue IHOP over WAFL technology?

    8. Re:ZFS was developed and trademarked by Sun by IICV · · Score: 1

      And the courts have said it doesn't, at least not in the way NetApp said it did the first and second time.

      So that's the end of that, I guess.

    9. Re:ZFS was developed and trademarked by Sun by adolf · · Score: 1

      I was using automatic NetApp snapshots on a hosted ISP (back when a shell account on a remote computer that actually had bandwidth was considered useful enough to pay money for) in 1994.

      FFS/UFS, AFAICT, didn't get snapshots until FreeBSD 5.

      FWIW.

    10. Re:ZFS was developed and trademarked by Sun by makomk · · Score: 1

      I'd be very surprised if FFS' implementation of snapshots is in any way similar to either WAFL or ZFS. FFS descendents generally use journalling or soft updates for consistency, whereas the WAFL and ZFS snapshots are based around the tree-of-pointers method. Not sure exactly how HammerFS works (another btree-based FS?), but it appears to have its own oddball methodology that requires running a special cleanup process on it periodically.

    11. Re:ZFS was developed and trademarked by Sun by Galactic+Dominator · · Score: 1

      You are correct, The cheap snapshots didn't come till ufs2 when Mckusick added the functionality. Much of the fs structure allowing such functionality was in place long before though like pointers and the upper/lower container layers of UFS. NetApp obviously did that well before BSD's and Solaris as well as some other things. My point is they were standing on the shoulders of giants to achieve it.

      http://www.usenix.org/event/bsdcon02/mckusick/mckusick_html/

      I'll take your word on the 94 NetApp usage, as I was still a few years away from even knowing what shell account was.

      --
      brandelf -t FreeBSD /brain
    12. Re:ZFS was developed and trademarked by Sun by Galactic+Dominator · · Score: 1

      Yes it's btree based. The special cleanup process is due to HammerFS's automatic snapshots. The fs takes a snapshot every 30 seconds, so a periodic reblocking is needed. The reblocking is trivial to implement and not much overhead either. Because of the way HammerFS is designed, it's left to the administrator of the FS to decide on the details. Reblocking is also for other things. HammerFS is also able to stream to slave computer which rocks. On the todo list is multi-master.

      http://www.mail-archive.com/kernel@crater.dragonflybsd.org/msg04235.html

      FFS/UFS2 snapshots are extremely similar to WAFL and ZFS, they are all copy-on-write block pointer implementations. To be clear though as it was pointed out earlier to me, NetApp implemented snapshot before FFS did.

      --
      brandelf -t FreeBSD /brain
  8. Fire away, Larry! by Just+Some+Guy · · Score: 1

    We need to announce loudly on Oracle forums that NetApp says that Solaris shops are using illegal software. There are few things that get Larry Ellison moving faster than the idea that someone might cost him a dollar.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:Fire away, Larry! by rattaroaz · · Score: 1

      At best, oracle would not care. At worst, they would encourage the lawsuit. This says nothing about zfs, only about freedom to use it. Oracle can give customers indemnification on solaris/zfs based stuff. What can Nexenta do, other than provide a great product? Legall, they can only be on the defense, as they probably do not have enough patents for a counter-offense. Oracle can only benefit from this, as nexenta is a competitor.

  9. Usual slashdot anaolgy by dacullen · · Score: 1

    But Sun/Oracle will fight back and cost $$$, So 1. Attack small organizations who cant afford to fight back 2. cite their capitulation as "evidence" of the validity of their patent. 3. "License" the IP to small vendors 4. Profit

    1. Re:Usual slashdot anaolgy by ducomputergeek · · Score: 1

      Except in this case, they did it wrong. They've already gone after Sun/Oracle and Sun not only fought back, but won round 1.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
  10. Id-10ts by geekmansworld · · Score: 1

    So much for our magical universal file system.

    Another case of cross-platform standards being ruined by a whiny patent abuser.

  11. Patents invalidated, awaiting appeal... by KonoWatakushi · · Score: 5, Informative

    See the second post in the recent thread on zfs-discuss: Legality and the future of zfs...

    It doesn't sound as if Netapp has a leg to stand on, so they are trying to shake down the companies while they can. Where have we seen this before?

  12. grow a set by Anonymous Coward · · Score: 0

    Wish Coraid had grown a set and told NetApp to f-off.

  13. Explains OSX Server pulling ZFS by bigredradio · · Score: 2, Insightful

    I guess this explains OSX Server walking away from ZFS because of "license issues". Since Apple walked away in the 11th hour, I wonder if there is some real validity to NetApp's argument (at least legally).

    1. Re:Explains OSX Server pulling ZFS by Joce640k · · Score: 3, Insightful

      ZFS isn't *essential* to Apple so why would they fight a patent battle in court? There's plenty of other file systems in the sea.

      --
      No sig today...
    2. Re:Explains OSX Server pulling ZFS by Lunix+Nutcase · · Score: 4, Informative

      Except that the courts and the patent office are saying otherwise in NetApp's case against Sun.

    3. Re:Explains OSX Server pulling ZFS by eddy · · Score: 4, Insightful

      We should all have learned by now that how people and companies react to legal threats doesn't have ANYTHING to do with so-called merits. 'The' SCOX case went on for about seven years and they had NOTHING. People paid them "linux tax" while they had NOTHING, could show NOTHING, made increasingly bizarre and outrageous claims and could in fact never WIN ANYTHING. People still paid.

      The lesson from that of course is that being a tick on the ass of the system it's a perfectly valid way to lift a nice salary and appear important, so really, why not?

      --
      Belief is the currency of delusion.
    4. Re:Explains OSX Server pulling ZFS by hedwards · · Score: 1

      Unless it turns out to be an easy suit, I think it would be far more likely that Apple would just pay a licensing fee to use it. I don't think they pulled it over IP concerns, I think it was pulled because it wasn't ready for prime time.

    5. Re:Explains OSX Server pulling ZFS by Amouth · · Score: 1

      If it was something that is non essential - and there is a rather long dispute - whom do they "license" it from? do they pay NetApp extortion money? maybe adding some validity to it? or do they just ignore the 10% of people using it and say we are going in this direction with no rime or reason (not uncalled for by Apple) and then after the dispute is over and there is a clear victory - they will add it back in as "fully supported" and the new way to go (cover your ears * whisper* isn't at all like the old way)

      sorry i can see apple just taking a step back and watching Sun/NetApp go at it..

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    6. Re:Explains OSX Server pulling ZFS by ais523 · · Score: 1

      The SCOX case is still going on. SCO had two appeals left (more if the Supremes decide they want to accept a case from them), and they just used one of them. (I haven't seen what their arguments are, and I don't think it's public knowledge yet; they should be hilarious when they come out, though.)

      --
      (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
    7. Re:Explains OSX Server pulling ZFS by MachineShedFred · · Score: 2, Insightful

      In order to license something, the licensor needs to be willing to enter into an agreement. Don't be so sure that NetApp wants to do that, when they can sell overpriced filers to Apple's customers.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    8. Re:Explains OSX Server pulling ZFS by gnasher719 · · Score: 1

      I guess this explains OSX Server walking away from ZFS because of "license issues". Since Apple walked away in the 11th hour, I wonder if there is some real validity to NetApp's argument (at least legally).

      I think the question for Apple was: How many engineers are needed to implement ZFS in a quality that it can be shipped, how many Macs would Apple sell more because of this, are there things that these engineers could do that benefits Apple more, then take into account that shipping ZFS invites a legal battle which again costs money and wastes time that could be better used elsewhere.

    9. Re:Explains OSX Server pulling ZFS by Anonymous Coward · · Score: 0

      Apple realized that there would be no GPL'd ZFS driver for them to steal^H^Hincorporate into OS X Server, which was a major "license" issue. Apple was waiting for the OSS community to write it but those lazy OSS developers didn't do anything and started working on btrfs instead. Now they have to wait for btrfs before they can "license" it into OS X Server. This was a major blow because we all know how seriously OS X Server is regarded in the server OS market, and how the five people who use it really needed the features of ZFS.

  14. The story so far. by AliasMarlowe · · Score: 5, Informative

    The Wikipedia article on NetApp talks about them bringing a suit against Sun/ZFS and that Sun countersued, but doesn't mention the verdict.

    Read all about it (the story so far, as presented by Sun/Oracle): http://www.sun.com/lawsuit/zfs, which provides links to a number of legal documents and patents and rulings from the PTO.
    Basically, the patent which was central to NetApp's claim of infringement was found not to apply to ZFS. A second patent asserted to be infringed was rejected on reexamination by the PTO, but NetApp is still squirming through the appeals process. The current round of threats could be NetApp's last gasp/whimper on the topic.

    --
    Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    1. Re:The story so far. by future+assassin · · Score: 1

      Sooo instead of learning from their loses and improving their product that go beyond their competitors in features/quality at the same price they rather spend the money on lawyers.

      --
      by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
    2. Re:The story so far. by makomk · · Score: 1

      If NetApp lose, they don't just lose the ability to stop Sun selling ZFS-based hardware, they lose the ability to sell any NAS or SAN kit. Sun were threatening them with patents covering things like hardware RAID, CPU design, and Ethernet bonding, and one of Sun's first actions was to try and get an injunction preventing NetApp from selling any of its hardware.

      (Oh, and Linux infringes most of these patents and Sun have consistently refused to either grant it a license or promise not to sue Linux users.)

    3. Re:The story so far. by Anonymous Coward · · Score: 0

      Except that they would most likely lose on many of those patent grounds since they are distributing the infringing works themselves as their Oracle Linux Distro.

  15. More complicated by a bit.. by Junta · · Score: 2, Insightful

    NetApp uses WAFL on their NAS. A filesystem they invented before ZFS. They claim ZFS violates patents of WAFL.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:More complicated by a bit.. by poetmatt · · Score: 4, Informative

      using WAFL on a nas is not any more inventive than using ZFS on a NAS. Again, the parent is correct.
      Using any filesystem for a NAS is not inventive. It's been around for quite some time. They're also going after distributors rather than attack the ZFS patents they purportedly precede.

      It's also quite impossible to prove any sort of patent violation for using ZFS on a NAS simply due to the competing software being patented.

      If I use a product X, of which is infringing upon product y, I am not liable for uses of product X. The patent system doesn't support 3rd party liability. it's just distributors buckling under legal threats.

    2. Re:More complicated by a bit.. by shutdown+-p+now · · Score: 1

      If I understand correctly, NetApps patents are really about their FS and not NAS, but they had only patented it in NAS context. So using ZFS normally doesn't infringe them, but using it in a NAS does - but the actual infringement is due to algorithms and techniques used in ZFS, and not due to NAS.

    3. Re:More complicated by a bit.. by mea37 · · Score: 1

      The validity of the patent can of course be challenged, though my understanding is that "using WAFL with NAS" isn't what's being claimed as patented; some thing that WAFL does is being claimed as patented, and NetApp further claims that ZFS does those same things.

      Also, you seem to think it's legal to sell a product that includes an infringing component; I'm confused why you would think this. Here's an excerpt from 35 USC 271, which defines patent infringement:

      (a) Except as otherwise provided in this title, whoever without authority makes, uses, offers to sell, or sells any patented invention, within the United States, or imports into the United States any patented invention during the term of the patent therefor, infringes the patent

      (emphasis added)

      3rd parties can absolutley get swept in, which is one of the reasons the penalties are less if the infringement isn't deemed "willful".

    4. Re:More complicated by a bit.. by reebmmm · · Score: 3, Insightful

      I use a product X, of which is infringing upon product y, I am not liable for uses of product X. The patent system doesn't support 3rd party liability. it's just distributors buckling under legal threats.

      You would be very, very wrong. Your use of an infringing product still makes you an infringer. (35 U.S.C. Sec. 271(a))("whoever without authority makes, uses, offers to sell, or sells any patented invention...). Now, there are default rules that say that a purchaser of a good is "indemnified" from claims of infringement by the seller. (See UCC Art. 2 Sec. 312) This is typically how end user avoid litigation.

      In addition, you're also wrong to think that the patent system doesn't support third party liability. It does. One party's can be sued for another person's direct infringement. It's called "indirect infringement." (35 U.S.C. Sec. 271 (b) and(c)). The rules on when this apply are stated in the statute and are not always so easy to discern. One way to think about it: a party cannot escape liability by simply knowing moving the infringement downstream.

      And, just so that you know, it is a somewhat common strategy that a patent owner sues the end user, direct infringer. There is nothing worse as a supplier than receiving about 30 letters from angry customers seeking indemnification from the infringement suit. This is a great technique to annoy the party with deep pockets and drive home the advantages of settling early.

  16. Indemnification by rayvd · · Score: 2, Insightful

    Oracle should offer to provide indemnification to vendors. They've got a large patent portfolio of their own and obviously large assets to make them a much more formidable foe to NetApp.

    1. Re:Indemnification by Lunix+Nutcase · · Score: 4, Informative

      Sun already does indemnify it's customers. Schwartz pointed this out when NetApp's rumblings against Sun first happened.

      First, the basics. Sun indemnifies all its customers against IP claims like this. That is, we've always protected our markets from trolls, so customers can continue to use ZFS without concern for spurious patent and copyright issues. We stand behind our innovation, and our customers.

    2. Re:Indemnification by fuzzyfuzzyfungus · · Score: 1

      However, Oracle does(or at least Sun did) sell ZFS-based NAS/SAN appliances(pretty cool looking, actually. 4U or so, slides out with top-loading trays for 48 SATA drives. Web interface for carving it up into pools and serving it up over ethernet).

      Thus, while they certainly have some motivation to provide indemnification to customers, because having their server users getting sued is awkward, it isn't clear that they actually mind NetApp shooting their smaller competitors in the ZFS NAS/SAN appliance space in the face for them(all the benefits, none of the bad publicity), unless those competitors are willing to pony up for a Solaris license per box, or something.

    3. Re:Indemnification by canajin56 · · Score: 1

      As as been pointed out, they do provide indemnification to vendors and users. However, indemnity doesn't make you immune from lawsuit. Patents, like it or not, protect the use and manufacture of a patented device, not just the distribution of that device. So, Sun, the vendor, and the customer all, separately, violated the parent. The patent holder thus has the right to sue separately all 3 of those entities. And, they can't lose their right to sue the vendor because of what it says in a contract they never signed.

      However, while on paper you are still being sued, Sun is allowed to stand in your stead because of the Indemnity agreement. IANAL, but I helped my wife and her sister study for their insurance licenses. If you are sued for personal injury following a car crash (or accidental injury in your home) that your insurance indemnifies for you, then your insurance company has a financial interest in the outcome. This means they have the right to stand in your stead as defendant. In fact, because of the fact that they'll pay for most-all of the judgment, the insurance company has more of an interest in the outcome of the case than you do, so you cannot say no, if they want to stand in your stead, they can regardless of your feelings. That is, if you hit somebody and cause them substantial injury, but they are your friend, you cannot have them sue you, represent yourself poorly, and then have the insurance company pay out your $2,000,000 judgment. They have the right to take your place as defendant and you cannot refuse them without losing your coverage.

      So, in this case, while technically you are not immune from suit, in practice Sun has the right, which they would almost certainly exercise, to stand in your stead as defendant, so you are, by most criteria, immune from lawsuits, thought your name would still be on the case. I'm not sure, but I don't think you'd even have to show up for court, so it really wouldn't inconvenience you at all. However, you would still get C&D letters, and still be sued.

      But again, IANAL, so I don't know it it works different than the sort of indemnity used in car and home insurance. Plus, it differs from state to state, and I'm from Canada (where it varies province to province).

      --
      ASCII stupid question, get a stupid ANSI
    4. Re:Indemnification by Macrat · · Score: 2, Interesting

      Sun already does indemnify it's customers. Schwartz pointed this out when NetApp's rumblings against Sun first happened.

      Neither Schwartz or Sun exists anymore.

    5. Re:Indemnification by Lunix+Nutcase · · Score: 1

      Schwartz may not exist but Sun does and the contracts its customer's made before Oracle bought them don't magically disappear.

    6. Re:Indemnification by Macrat · · Score: 1

      Contracts expire.

    7. Re:Indemnification by Lunix+Nutcase · · Score: 1

      And you assume they've expired or that Oracle doesn't provide the same indemnification based on what evidence? Oh wait, you have none.

  17. No need... by Junta · · Score: 1

    NetApp has been in a legal battle over WAFL v. ZFS from before the Oracle takeover. Oracle is keenly aware of all of this.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  18. NetApp by goombah99 · · Score: 4, Interesting

    Much as I hate these patent cases, perhaps this one has merit. NetApp built it's bussiness being a vendor of NAS systems that had extensible file systems that spanned clever raid structures, and automatic snapshoting and they did this long before ZFS. Those are the key features of ZFS. And when you pair that with NAS, well that's a NetApp in a box. I dont know what NetApps patents claim but what they did was not obvious at the time and they are actively a seller of that, not a patent troll.

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:NetApp by Just+Some+Guy · · Score: 5, Insightful

      NetApp built it's bussiness being a vendor of NAS systems that had extensible file systems that spanned clever raid structures, and automatic snapshoting and they did this long before ZFS. Those are the key features of ZFS.

      VMS did it earlier. Screw NetApp and their overpriced, underfeatured, patented crap. Really. I mean that.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:NetApp by marcello_dl · · Score: 0

      Indeed they are not patent trolls. Yet a probably clean room implementation of a FS with advanced but not revolutionary features get slammed. (visicalc can be said revolutionary, surely not "lets make an arbitrarily mapped and resizable RAID" or "lets the FS recover to any point in time")

      Ergo the patent system is broken even when trolls do not exploit it.

      Of course it is broken for the citizen. For people that want to make a market out of IP for their own pleasure, it is working perfectly.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    3. Re:NetApp by rayvd · · Score: 1

      I can see what you're saying as well. ZFS does a _lot_ of the things WAFL has done for years. I don't really think those approaches should necessarily be able to be patented though, but as it is now, you can see how something like ZFS -- very similar to WAFL in a lot of ways would raise some red flags and at least warrant some investigation (whether or not we agree with the principles there).

      NetApp should focus on their business model though instead. WAFL is still significantly more mature than ZFS and has a superior deduplication implementation IMO. Their stuff "just works". They've got plenty of ammo to continue competing... I suppose they realize this and are just doing their corporate "due diligence" in aggressively trying to protect their IP.

    4. Re:NetApp by Lunix+Nutcase · · Score: 5, Informative

      The case doesn't have merit because the courts have already ruled that ZFS doesn't infringe NetApp's patent No. 6,892,211 which is at the heart of their infringement claims. This is just a shakedown.

    5. Re:NetApp by BitZtream · · Score: 1

      They may have done it 'before ZFS', but neither of them were original. If they were the first it might matter, but you're not talking about anything new really from them. They were just applying old ideas to new hardware under the hood.

      MS doesn't get a patent for using mouse clicks on the next intel processor because they filed first before Apple any more than NetApp gets something special because they applied 1970s processes to 1990s SCSI drives or SATA/SAS drives now.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    6. Re:NetApp by BitZtream · · Score: 1

      I feel I should also point out:

      Those are the key features of ZFS. And when you pair that with NAS, well that's a NetApp in a box

      Its also a very obvious pairing to anyone with even a quarter of a clue in the industry, not patent worthy in the least.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    7. Re:NetApp by h4rr4r · · Score: 2, Interesting

      Bullshit, look at mainframes many of those had these features. A NAS is just a server with a bunch of disk.

    8. Re:NetApp by Just+Some+Guy · · Score: 2, Interesting

      ZFS does a _lot_ of the things WAFL has done for years. I don't really think those approaches should necessarily be able to be patented though, but as it is now, you can see how something like ZFS -- very similar to WAFL in a lot of ways would raise some red flags and at least warrant some investigation (whether or not we agree with the principles there).

      Chrome does a _lot_ of the things MSIE has done for years. I don't really think those approaches should necessarily be able to be patented though, but as it is now, you can see how something like Chrome -- very similar to MSIE in a lot of ways would raise some red flags and at least warrant some investigation (whether or not we agree with the principles there).

      I suppose they realize this and are just doing their corporate "due diligence" in aggressively trying to protect their IP.

      Screw their "due diligence". They're just being desperate assholes and everyone knows it.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:NetApp by BitZtream · · Score: 1

      Their stuff "just works".

      You do realize thats pretty much an admission that you've never actually used any of their hardware ... right?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    10. Re:NetApp by Lunix+Nutcase · · Score: 1

      So if WAFL is so much better technically then why does NetApp need to throw around bogus patent infringement claims (and yes the claims about ZFS infringing their patents has been ruled to be wrong) rather than just competing on the merit of their product?

    11. Re:NetApp by Attila+Dimedici · · Score: 2, Informative

      Much as I hate these patent cases, perhaps this one has merit. NetApp built it's bussiness being a vendor of NAS systems that had extensible file systems that spanned clever raid structures, and automatic snapshoting and they did this long before ZFS. Those are the key features of ZFS. And when you pair that with NAS, well that's a NetApp in a box. I dont know what NetApps patents claim but what they did was not obvious at the time and they are actively a seller of that, not a patent troll.

      Sorry, either ZFS violates their patents in all of its uses, or they have no claim. If I build a machine that makes widgets and patent it, then you build a machine that builds widgets using a completely different technique, my patent does not apply to your machine. This sums up a large part of the problem with software patents, it is very hard to see whether a piece of software reaches the same results as another piece of software using different methods or not.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    12. Re:NetApp by Anonymous Coward · · Score: 0

      You can only patent methods. It is entirely reasonable to assume that ZFS does the same things using different methods. You can't patent ideas no matter how hard these companies try to litigate otherwise.

    13. Re:NetApp by Bert64 · · Score: 1

      While WAFL may be more mature it won't stay that way...
      NetApp will need to seriously innovate if they want to compete with ZFS based competitors, and that will decrease their profit margins.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    14. Re:NetApp by Bert64 · · Score: 2, Insightful

      Competing on product merit is less profitable because you actually have to invest in improving your product, you can't just keep selling the same old shit at ridiculously high prices and hope the competitors don't overtake and undercut you.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    15. Re:NetApp by Wesley+Felter · · Score: 1

      WAFL may be better than ZFS, but many customers may decide that it's not $20,000 better.

    16. Re:NetApp by Vancorps · · Score: 1

      What feature does NetApp lack? If you're going to call it crap at least present some reasons, those of us that have used Hitachi, HP, and EMC storage in our SANs don't see NetApp as crap at all.

      Your claim about VMS is highly suspect as well as even modern OpenVMS lacks many of the features found in a typical NetApp SAN.

    17. Re:NetApp by Vancorps · · Score: 1

      As someone who manages 6 filers myself I can assure you that it is pretty accurate. I've yet to encounter any storage provider that is easier to setup and configure. HP and EMC have nothing on the ease of use found in NetApp. They've definitely taken some missteps along the way, VFM was terrible, so terrible they stopped selling it.

      Out of curiosity what do you find so difficult about working with NetApp hardware?

    18. Re:NetApp by Vancorps · · Score: 1

      I missed something, when was the patent case ruled to be wrong? Last I heard it was still ongoing...

      Given what I've seen about WAFL and what I've read about ZFS it doesn't seem like there is anything bogus about the claim unless you think software patents should be thrown out in general.

    19. Re:NetApp by Anonymous Coward · · Score: 1, Informative

      NetApp realizes their product (which is closed-source, patented, and if NetApp disappeared tomorrow you'd be in hell, unlike ZFS-based stuff) has a rapidly diminishing list of features or functionality that it can claim is better (or even on par) with ZFS-based appliances. They're taking the SCO route of litigation over innovation, and it's hardly the first time. Ask anyone who has used NetApp products for awhile how much has changed in the product over the last 5-10 years; now ask anyone who has used NetApp products AND Oracle/Sun's 7000 series which is more feature rich, slicker, and cheaper. NetApp still wins slightly on reliability and HA and hardware options (and the hardware options is a by-product of who they OEM their hardware from), but has already gotten trumped on performance-per-GB, features (all included in base price on Oracle/Sun platform, no less), and interface (including the most important part - analytics).

      Also bear in mind, NetApp doesn't even MAKE their hardware.. they OEM it from Dothill and Xyratex (and maybe others); they're solely a software house - and yet they haven't made any really innovative changes to it in nearly a decade. It STILL won't let you have more than 16 usable TB in one aggregate, for example, unless you use a separate technology/OS they PURCHASED YEARS AGO, and still haven't integrated properly. You're paying atrocious prices to NetApp for what is basically a product they only wrote the software for, and they haven't really done much to bring that software into this millennium. Would you pay outrageous prices for new computers running Windows 98 if it couldn't be reinstalled with a newer OS? Of course not. So why are you buying NetApp?

    20. Re:NetApp by Anonymous Coward · · Score: 1, Informative

      ZFS -alone- doesn't infringe, but put it on an NAS and you're duplicating features they made for an NAS before ZFS came out.

    21. Re:NetApp by allenw · · Score: 1

      ON-TAP lacks a decent Kerberos stack. It is embarrassingly ancient in its support of encryption types, which makes it pretty much a non-starter for secure NFS.

    22. Re:NetApp by nns6561 · · Score: 1

      Sorry, ZFS combined with a NAS could infringe a patent that ZFS by itself doesn't. It all depends on whether the NAS was included in the claims. One of the patents cited in this discussion appears to do just that. However, without fully analyzing the patent, it's hard to know the exact extent of the claims.

    23. Re:NetApp by moggie_xev · · Score: 2, Informative

      There is lots of things I agree with in this post however.... They do just work and they keep on working

      uptime 10:07pm up 634 days, 2:48 15108652057 NFS ops, 2183855307 CIFS ops, 3315 HTTP ops, 0 FCP ops, 0 iSCSI ops

      Ontap 8.0 in 7 mode does support up to 90TB in a single aggregate. However given that I am evaluating systems that scale to petabytes in a single filesystem....

    24. Re:NetApp by Coward+Anonymous · · Score: 1

      You apparently know nothing about NetApp or its products...

    25. Re:NetApp by sglewis100 · · Score: 1, Troll

      Out of curiosity what do you find so difficult about working with NetApp hardware?

      SnapMirror leaves some things to be desired, monitoring is a PITA, their web interface is CRAP, I even prefer Navisphere for friendliness. Primary deduplication is a joke, despite how many times their engineers told us "that shouldn't be possible" as we demonstrated bringing a test filer to it's knees / crashing it outright as we dealt with 1tb volumes that stored a bunch of SQL dumps that were a joke to dedupe being so similar. iSCSI performance is a joke (WAFL is great if you run a NAS, but they play in the SAN space, and WAFL really isn't helping NetApp pretend to be a block level storage provider.

    26. Re:NetApp by Attila+Dimedici · · Score: 1

      If ZFS doesn't do it the way that NetApp patented it, even if it does exactly the same thing, it is not a violation of the patent. This example will be an oversimplification but it illustrates the way patents should work (and used to work). If person A patents a system for building brick walls where you pick up a brick and apply mortar to it and then place the brick in place and then repeat with another brick, person B is not violating person A's patent if they place mortar on the surface then place a brick on the mortar and then repeat with another brick. When they are done, person B's brick wall may look exactly like person A's brick wall, but it did not violate person A's patent (for those of you who know something about masonry, I am well aware that this example is very oversimplified and would not work quite as described).

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    27. Re:NetApp by bolthole · · Score: 1

      Yet, but they dont want to "compete", because that would mean lower margins for them. So they are trying to either eliminate the competition entirely, or doing a "Buy me too! me tooo!!" play to Oracle.

    28. Re:NetApp by couchslug · · Score: 1

      "Screw NetApp and their overpriced, underfeatured, patented crap. Really. I mean that."

      One might literally screw NetApp, by vocally recommending to all and sundry not to buy their shit. :)

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    29. Re:NetApp by Lunix+Nutcase · · Score: 1

      Last december it was ruled they didn't infringe.

    30. Re:NetApp by frieko · · Score: 1

      To literally screw NetApp would require some sort of giant screwdriver capable of rotating NetApp until it bored into a piece of wood.

    31. Re:NetApp by Anonymous Coward · · Score: 1, Insightful

      The computing world is all about duplicating features, improving on things, and seeing who can do it better. If it weren't for this, we'd still be stuck with one vendor's implementation of a GUI desktop.

    32. Re:NetApp by Courageous · · Score: 1

      . Screw NetApp and their overpriced, underfeatured, patented crap. Really. I mean that.

      Really? You mean that.

      *thinks about it*

      Yeah, I guess there are some NetApp sales reps worth screwing.

      Although have you seen my VMware rep?

      C//

    33. Re:NetApp by makomk · · Score: 1

      Because firstly it's hard to compete with something that costs nothing, and secondly Sun were threatening NetApp with some very nasty broad patents that would endanger their ability to sell any NAS or SAN kit at all. (Seriously, Sun's use of its patents should be a lot scarier to competitors than NetApp's, because they potentially affect far more companies.)

    34. Re:NetApp by makomk · · Score: 1

      Not just that, but the way ZFS achieves this is very similar indeed to the way NetApp does, and the engineers designing ZFS were aware of this, and Sun were trying to extort $1 million from NetApp plus a license to all their patents over some much more vaguely broad

    35. Re:NetApp by Anonymous Coward · · Score: 0

      If MS went afyer Chrome, Google would pull out one of their patents (maybe something Bing uses). Apple finds out that Safari infinges too and is forced to defend Google with some of their patents. Microsoft pays Novell a few million dollars for a UNIX license and suddenly Novell pulls out something against Google. IBM knows they have a bigger portfolio than all of them put together, and releases a Lotus Browser that doesn't work well but infringes on all their patents (just to remind them who's in control).

      So you see, that is why all the big players know to avoid a patent pissing contest wherever possible.

    36. Re:NetApp by turbidostato · · Score: 1

      "Much as I hate these patent cases, perhaps this one has merit."

      It might have legal merit but it's obvious it can't hold water from an objective standpoint.

      NetApp is FUD-waving some patents it holds. If those patents held any real merit, it should be impossible for Coraid to violate them, using as it's the case a totally different FS technology. NetApp can try this because:
      a) Their pockets are deeper than those of Coraid, so Coraid risks a financial debacle even it they absolutly know to be on the safe side. Blame the American justice system for that.
      b) The "patents" hold by NetApp are vague assertions about some high level functionalities that shouldn't be patentable 'per se' in any sane world: were it not for the MAD if they tried that against IBM, Oracle or HP they could go against every NAS builder everywhere since basically their position is "the NAS *concept* is patented by us". Blame the American pantent system for that.

      "NetApp built it's bussiness being a vendor of NAS systems that had extensible file systems that spanned clever raid structures, and automatic snapshoting and they did this long before ZFS."

      Exactly. And that is a *concept* and it is *not* patentable (it shouldn't be). A device that offers a NAS service, RAIDed, expandable and snapshotable by means of *this* specific RAID implementation, *this* specific expanding filesystem and *this* specific snapshotting technology is certainly patentable but then NetApp obviously couldn't wave their patent portfolio against a company that uses a *different* RAID implementation, *different* filesystem and *different* RAID software.

      "And when you pair that with NAS, well that's a NetApp in a box."

      Well, you know what happens when you take four wheels, and engine and a steering wheel? You have a car. And cars are full of patents, of course, but coming the car from older saner days that didn't mean the *concept* of a vehicle with four wheels, and engine and a steering wheel was patentable and thus you can buy cars from a lot of different builders, each of them certainly with their own pool of patented inventions, instead of being forced to buy all cars from Mercedes because they patented the concept.

      NetApp already has a leading edge as you yourself demonstrate by "nominalizing" their brand: that's a "netapp" but it's still a concept. Of course NetApp would be glad if an insane legal system allows them to patent the concept so no one can compete against them no matter if they use their own technologies or not.

    37. Re:NetApp by Anonymous Coward · · Score: 0

      Really? Overpriced and under-featured? That's actually the opposite of what NetApp is known for. You really have no idea what you're talking about do you? Do you even have a clue as to what the current enterprise storage industry is like?

      NetApp offers enterprise level solutions at a fraction of the cost of it's main competitors (EMC, HP, IBM, Dell, etc.). This is one of their biggest selling points and one that frequently puts them into data centers and gives them such high customer satisfaction numbers. One of NetApp's biggest benefits is it's wealth of features, most of which are included with no separate licensing needed, so much so that NetApp is known in the industry for being very feature rich at a great price.

      EMC still has NetApp beat on overall reliability though and as a result EMC is in more mission critical environments, but it's becoming a closer race everyday from what I read, see, and hear.

      I've worked in the industry for just about 10 years now and I can easily say that my experiences with NetApp equipment, people, and technology have been far more enjoyable than those with the other guys. Hands down I will choose NetApp solutions in my data center again with no hesitations.

      -- On a side note, let's not forget that Sun sued NetApp first and NetApp simply countersued to protect their IP.

  19. NetApp Must Die! by Nom+du+Keyboard · · Score: 1

    NetApp must die. And they can be buried in the same grave with NTP.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
    1. Re:NetApp Must Die! by Anonymous Coward · · Score: 0

      NetApp must die. And they can be buried in the same grave with NTP.

      But if we do that, how will I keep my computer clocks accurate?

  20. They're afraid of ZFS by guruevi · · Score: 5, Insightful

    ZFS is a game changer in the storage industry. While people are buying $250,000 NetApp installations, the exact same hardware, performance and connectivity will go for $5000 of high-end hardware and a couple of hours work with ZFS. $250,000 will easily buy you a Petabyte worth of redundant ZFS storage. Even the reasons you would otherwise buy NetApp or another proprietary storage solution (compression, de-duplication, checksums) is all implemented by ZFS.

    NetApp recently lost their patents based on prior art (they basically ripped off somebody's paper and put in a patent for it), appealed it of course and now they are trying to squeeze the last money out of small shops before they get the smack down from the patent office. This is a very similar case to the Caldera/SCO cases.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
    1. Re:They're afraid of ZFS by macs4all · · Score: 3, Informative

      Will your 5000 dollar box call home, have a staff of engineers at the ready, replace it's own drives and be constantly updated with firmware?

      Um, NONE of those feature have ONE SINGLE THING to do with the underlying filesystem. You could make a NAS out of NTFS or HFS+ or (I'm guessing) EXT3 drives, that used something like the hard drives' SMART statuses to place orders over the intarwebs for a new HD (billed to your credit card) that would appear automagically at your doorstep. Big fucking deal.

      As for the "auto-updating" firmware: Who in the FUCK wants ANYTHING as CRITICAL as a NAS to "auto update" its FIRMWARE?!?!? It can ASK; but I SURE as FUCK don't want my NAS to suddenly be HOSED (or simply inaccessible) just because some crackhead droid at NetApp posted the wrong binary (or even the right one!) to the "updates" directory on their server.

      And as for a "staff of engineers at the ready", if your product is STABLE, you don't need "a staff of engineers at the ready", you simply need a few TECHNICIANS that can competently answer users' questions and address their problems. All those "engineers" do is ARTIFICIALLY increase the "reliability" of the product. Afterall, unless the "engineer" uses a matter-energy transporter to instantly appear at your NAS' side, it is HIGHLY unlikely that they will be able to help you regain accesss to, let alone RECOVER, your data ANY faster than a tech-support droid that you reach on the phone.

      And, as I said before, NONE of those "features" have ANYTHING to do with "WAFL vs. ZFS". It is all about APPLICATION CODE that someone added to the "NAS Controller" (read: Embedded Linux Computer) running the NAS APPLICATION.

      Jeezus! For a supposed "geek" site, some people on here are pretty fucking IGNORANT of how these SYSTEMS are designed, and just how many interlocking pieces-parts make up a NAS product. The particular filesystem used by the NAS Controller is but a small (and easily-changed by the manufactuer) part of the overall SYSTEM. Calling home to order a hard drive is only one small (and quite obvious) step from "emailing the owner" when an error is detected in the NAS, which is a feature many NAS' have (I just saw it this week on a Buffalo LinkStation NAS I was working on). Same thing with all the other "proprietary" features that NetApp sells to their oh-so-gullible customers.

      WAFL may in fact be a wonderful FS; but the "features" you mention are simply not germane to the debate. Or to WAFL.

    2. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      Psst... You fed the troll... :)

    3. Re:They're afraid of ZFS by kindbud · · Score: 3, Informative

      While people are buying $250,000 NetApp installations, the exact same hardware, performance and connectivity will go for $5000 of high-end hardware and a couple of hours work with ZFS.

      Having evaluated ZFS on a Sun server at that price point, I can state with a good degree of certainty that this is not even close to true. ZFS suffers from several show-stopping performance problems that made it unsuitable as replacement for NetApp filers even on our small applications. Last I checked, the issue we opened with Sun are still outstanding.

      ZFS is probably OK for hosting a file archive, or staging backups. It is far from OK for hosting a Oracle or Mysql database.

      --
      Edith Keeler Must Die
    4. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      When you need cutting edge, don't care about data corruption, and cheap disk, go ZFS.

      Uh? WTF! You clearly haven't got a clue.

    5. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      Yeah, it's true.

      For less than $12,000 CDN we have 18 TB of raw storage (14 TB after redundancy) in a server (4 cores, oodles of RAM, 24 drive bays, multiple NICs) that handles rsync backups of 130 remote servers every night. Another $15,000 server sits across town as a replica, just in case. With daily snapshots going back 6 months, and monthly snapshots going back another 6 months. Sometime next year, when ZFSv22+ hits FreeBSD, we'll get deduplication support for free, and should be able to keep even more daily snapshots around.

      For less than $25,000 CDN, we have a system that EMC says is impossible to build for under $100,000 US (yes, I've argued with their sales people about it). There are other companies around that have spent over $200,000 CDN to get something that can backup less than 100 servers, with under 10 TB of redundant storage. Sometimes you have to wonder about IT managers and sales pitches.

    6. Re:They're afraid of ZFS by drsmithy · · Score: 1

      The particular filesystem used by the NAS Controller is but a small (and easily-changed by the manufactuer) part of the overall SYSTEM.

      Actually, nearly all of the interesting stuff a NetApp filer (as opposed to some other NAS) does hinges on WAFL. They most certainly couldn't just swap it out and have an equally functional and performant "SYSTEM".

    7. Re:They're afraid of ZFS by Anonymous Coward · · Score: 2, Interesting

      ZFS is probably OK for hosting a file archive, or staging backups. It is far from OK for hosting a Oracle or Mysql database.

      You may want to tell that to SmugMug:

              http://don.blogs.smugmug.com/2008/10/10/success-with-opensolaris-zfs-mysql-in-production/

      Greenplum also doesn't seem to have received your message:

              http://blogs.sun.com/jonathan/entry/openstorage_and_really_big_data

      Similarly with Joyent:

              http://joyeur.com/2010/07/02/on-solaris/

      (shrug)

    8. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      I call bullshit.

      "Several show-stopping performance problems" and yet no mention of what those might be nor the scenarios in which they might occor?

      Like I said, bullshit.

    9. Re:They're afraid of ZFS by guruevi · · Score: 3, Insightful

      There is no magic that NetApp adds that would make it any faster or slower than a comparable system using ZFS. I've seen, implemented and used both systems, they both use commodity hardware. There is no reason your ZFS should work any worse when you get down to the wire than your NetApp appliance unless you're doing something wrong. If you're comparing Sun's RAIDZ with their proprietary RAID0 then you're looking at the wrong implementation for a database. If you add a couple of L2ARC and ZIL SSD caches to your ZFS system, your database should be able to sustain well over 10000 IOPS - on commodity hardware. The other problem with NetApp is it's limits - 16TB is laughable in my field (even 16PB will be laughable in less than a decade).

      When I look at NetApp's white papers, all I see is a similar implementation to ZFS. NVRAM as caches, aggregated writes, snapshots... As I said, they're afraid because ZFS does everything NetApp does and more for a heck of a lot less. NetApp seems to have stopped developing major features which could have distinguished them from other systems and instead just focuses on selling as much systems in the next few years as possible and possibly litigate to get some more cash (the SCO business model).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    10. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      I would very much like to hear more of your experiences as well as the specific issues you encountered; we're in the midst of researching/purchasing a ZFS server at that price point from those applications and no show-stoppers have come up yet.

    11. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      This is not all that similar to Caldera/SCO. The possibility of tainted knowledge and influence between WAFL and ZFS's development actually exists in this situation while Caldera/SCO boondoggle was the result of muddy agreements, contracts, court cases, and too many hands in the pot as the companies and technologies and rights changes hands over time until a group of jerks thought they were sitting on a pile of gold and got sue-happy.

    12. Re:They're afraid of ZFS by Courageous · · Score: 1

      While people are buying $250,000 NetApp installations, the exact same hardware, performance and connectivity will go for $5000 of high-end hardware and a couple of hours work with ZFS

      This claim, sadly modded as "Insightful" (um), is even more sadly lacking in evidence.

      C//

    13. Re:They're afraid of ZFS by chef_raekwon · · Score: 2, Informative

      While people are buying $250,000 NetApp installations, the exact same hardware, performance and connectivity will go for $5000 of high-end hardware and a couple of hours work with ZFS

      lies. having worked in this industry for far too long, when I see bullshit claims like this, I have to call it. There is no way in hell you will get multiple trays of 15k rpm FCAL storage and redudant FAS controllers for 5k, I dont care if you're Samuel Jackson in the negotiator.

      I run multiple datacenters with emc, hp and netapp filers -- if you pay 250k for a netapp installation, you're pretty much getting what you pay for. what you're paying for is IOPS, disk caching, and throughput. You can turn to just about any storage provider, you will pay the same price for similar enterprise grade hardware. All I ask is that when you're stringing your two cans together, you leave out the reference to how alike it is to a 'real enterprise grade' product -- because talking about petabytes of SATA isn't even in the same continent, let alone the same country.

      --
      We're like rats, in some experiment! -- George Costanza
    14. Re:They're afraid of ZFS by chef_raekwon · · Score: 1

      my my - more AC BS.

      when you require actual performance from your storage (in the environs of 6k-10k+ iops), please come back with some money in your hand.

        -- IT Management

      --
      We're like rats, in some experiment! -- George Costanza
    15. Re:They're afraid of ZFS by Anonymous Coward · · Score: 0

      I have seen NetApp killers from many vendors from last 10 years, sadly none have worked well in nfs performance compared to NetApp. (no need to even talk about maintenance what those "killer" appliances required)
      One vendor tried with full blade center and really high-end storage, and still didn't get same performance.
      Wake me up when some box can pull more than 120k nfs ops/sec in fully ha-clustered system and which don't require daily administration to keep it running.

    16. Re:They're afraid of ZFS by soppsa · · Score: 1

      There is no magic that NetApp adds that would make it any faster or slower than a comparable system using ZFS.

      Not true at all. Netapp uses commodity drives running their own weird (magic) firmware. The netapp appliance is aware of where the drives are rotationally at any given point and are able to stage/queue their writes/reads in this way for optimum performance. That is why no Netapp killer has come up in the more than a decade Netapp has been in this game. Don't work for Netapp, don't even own one right now, but they are *wonderful* if you can afford it.

  21. btrfs successor by mlts · · Score: 4, Interesting

    Even though btrfs isn't in production yet, we really need a successor to it not just to replace the filesystem, but to replace the LVM layer. ZFS isn't just a filesystem, but also goes one layer lower, coordinating RAID.

    I wish I had the cash to make an open source (GPL or BSD license preferably) bounty for the following in a filesystem/LVM replacement, since ZFS isn't going to be going past Sun hardware these days:

    1: Deduplication on the block level. This would be selectable because in some cases, there would be performance issues to it... but a good filesystem would stick heavily duplicated blocks on fast media (flash or inner cylinders).

    2: 64 bit CRCs. This way, a backup program just has to pull from the filesystem stored CRCs and it would know which files have been changed or not. This also helps with integrity checking.

    3: Compression. Selectable levels would be nice, from a fast zip based to bzip2 -v9.

    4: Encryption, perhaps like EncFS where encrypted directories can be cattached at will. Even better would be more elaborate (public key, smart card) key management.

    5: Block device encryption. It would be nice to install the OS, set a flag that all further writes will be encrypted to a key, then proceed to copy data to the machine. This way, the machine can get set up and (ab)used without waiting for disks to encrypt.

    6: TRIM support. Enough said.

    7: Ability to move data so one directory might be on a three-way mirror, while the rest of the filesystem sits on a RAID-Z equivalent. This way, critical documents are protected.

    8: Advanced snapshotting functionality. It would be great to be able to restore a machine by booting from a USB flash drive or CD, having the filesystem be configured to the hard disks at hand, then copy from a stored image, regardless of architecture or setup of the previous machine's drives were. This way, a machine could be snapshotted, it be moved to a completely different configuration, then restored. A good example of a nice way to restore would be IBM's Sysback utility for AIX, where one can completely redefine where data resides before kicking off a restore.

    9: Advanced attributes, where files can be flagged where if they are unlinked, the OS does a manual TRIM or multiple overwrite, and so on.

    10: Automatic repair of damage. Starting with Windows Server 2008, Windows does a background check to look for damage in mounted NTFS filesystems. This way, something like missing free space or other issues can be flagged before it bites someone in the next bootup. For example, when a machine is idle, it will compare written 64 bit CRCs to what is on disk to ensure that they match, and flag nonmatching files as possibly corrupt.

    11: Ability to add varying amounts of ECC to a filesystem. This way, the volume can take a lot of damage, but the files are highly likely to be still readable. A good example of this is Nero's SecureDisk, where it writes invisible ECC information to burned CDs/DVDs which can be used to piece together damaged files. This way, volumes that are stored for long term archiving can sustain damage, but there is a good chance of recovering the files, or at least knowing the files were damaged.

    1. Re:btrfs successor by Luke+has+no+name · · Score: 2, Insightful

      BTRFS already does multi-disk filesystems including RAID 0 and 1 by itself, bypassing LVM/mdadm AFAIK. RAID 5/6 is a planned feature.

      I don't know about the rest of the stuff you mentioned; I'm not a filesystem guy. Recommend any good books?

    2. Re:btrfs successor by eln · · Score: 2, Insightful

      but a good filesystem would stick heavily duplicated blocks on fast media (flash or inner cylinders).

      Why? Just because a block of data is duplicated all over your filesystem that doesn't mean it's accessed all that frequently. If I have a disk with 8,000 slightly different ghosted Linux disk images on it, I'm bound to have plenty of blocks that are identical in all of them, so deduplication would save me lots of space. However, since they're probably all just there for archival or testing purposes, and I only occasionally need to access any of them, putting those deduplicated blocks on fast storage would be a waste of my most expensive disks.

      Fast storage is for frequently accessed data, not heavily duplicated data. Most halfway decent network storage devices already have caching algorithms that will put frequently accessed data on fast storage, whether that's SSD or NVRAM (or both).

    3. Re:btrfs successor by Princeofcups · · Score: 1

      I wish I had the cash to make an open source (GPL or BSD license preferably) bounty for the following in a filesystem/LVM replacement, since ZFS isn't going to be going past Sun hardware these days:

      And it really hasn't taken off there either. All the Sun shops that I know still use Veritas volume manager and filesystem.

      --
      The only thing worse than a Democrat is a Republican.
    4. Re:btrfs successor by dgatwood · · Score: 3, Insightful

      I wish I had the cash to make an open source (GPL or BSD license preferably) bounty for the following in a filesystem/LVM replacement, since ZFS isn't going to be going past Sun hardware these days:

      ...list of requirements...

      To which I would add:

      12. BSD-licensed. What's really needed is a robust filesystem that's ubiquitous---a filesystem that is supported across operating system platforms--- and let's face it, no GPL-licensed filesystem will ever darken the door of any OS except Linux, at least not as part of the OS. Even the *BSDs won't touch a GPLed filesystem except as a from-scratch rewrite. Forget about commercial UNIX vendors. And although you can gain partial support through little tricks like FUSE, such workarounds will never be as fast, as reliable, or as integrated into the whole user experience as a native filesystem would be.

      There's little point in taking any filesystem beyond academic research into a production-quality filesystem if the resulting disks can't be moved from one machine to another without forcing users to being a single-OS shop. Most of the real world doesn't consist of single-OS shops. In fact, an ideal next-gen filesystem would integrate SAN capabilities at the filesystem level so that disks could not just be moved, but actively shared between boxes running Linux, Mac OS X, Solaris, etc. That's just not likely to happen unless you choose a much more open license than the GPL.

      Don't get me wrong, I've written and licensed code under the GPL. There's nothing inherently wrong with the GPL for tools/utilities, GUI apps, and other end-user bits. For libraries, filesystems, drivers, and other code that is tightly coupled with the OS or software built on top of it, however, the GPL is really a rather poor choice. It sends the message, true or not, that you care more about dogma than interoperability, which is generally not a good thing. Ask me why I don't run either btrfs or ZFS.... It's the license.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    5. Re:btrfs successor by dgatwood · · Score: 1

      Agreed. If anything, it's the reverse. Heavily duplicated data indicates that the file hasn't been modified in an eternity. Such files are less likely than average to ever be accessed again. What you want on fast storage are:

      • Recently modified blocks. Blocks modified recently tend to be part of active projects that the user is working on right now. Thus, recently modified files are the ones that you would most commonly expect to see modified in the near future. A good way to handle this is by using much of the fast storage as a write-back cache, lazily writing the data out to slower storage when the system is idle, and evicting clean blocks as needed in a least-recently-used (LRU) fashion or similar.
      • Properly identified "hot files"---files that are frequently read and/or written as part of the boot process, launch of commonly used apps and tools, etc. The degree of duplication among snapshots depends on how frequently you update your OS and whether the OS vendor tends to modify those particular files. As such, the number of duplicates is not a good metric for these. You pretty much just have to figure this out by the usual statistical means.

      Word of caution: you should probably specifically exclude paging files from your hot files algorithm. Swapping to flash is generally considered to be a Bad Idea (tm), and those are usually the hottest files on a system....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    6. Re:btrfs successor by Anonymous Coward · · Score: 0

      What do you mean ZFS is going to be limited to Sun hardware? It's already production ready on FreeBSD (and its off-shoots) and the file system is being ported to Linux as a module.

    7. Re:btrfs successor by Anonymous Coward · · Score: 0

      And it really hasn't taken off there either. All the Sun shops that I know still use Veritas volume manager and filesystem.

      Anyone using Veritas for rootvol's is an idiot asking for trouble. Everyone I know (apart from my own company which does use veritas on rootvol as the managers make the decisions) uses SVM, or ZFS since you can boot from a Solaris cd and recover. Good luck doing that with Veritas.

    8. Re:btrfs successor by Anonymous Coward · · Score: 0

      I'm pretty sure btrfs already supports TRIM and snapshots. Subvolumes might count for your LVM-layer replacement. IIRC, deduplication, compression, and raid-like features are planned.

    9. Re:btrfs successor by funwithBSD · · Score: 1

      I removed 90% of my VXVM licenses in a recent data center move/refresh.

      you could hear the crying over the phone, we dropped 250+ licenses.

      --
      Never answer an anonymous letter. - Yogi Berra
    10. Re:btrfs successor by Sinical · · Score: 2, Interesting

      I'm not gonna go through and do a feature check, but there is Ceph. It's still pretty early in the development, but looks pretty promising. It uses btrfs as the underlying filesystem.

      Someone put together 1.2PB of Glustre (with dual replication) at my company and it's been problem free so far...

    11. Re:btrfs successor by embobo · · Score: 1

      EVMS ( http://evms.sourceforge.net/ ) could do some of these things and shared the same vision as ZFS: "EVMS provide[d] a single, unified system for handling all of your storage management tasks." The memory is a bit fuzzy but I think it was a port/reimplementation from AIX or else IBM was involved. I think it died because it didn't integrate well into the kernel (like ZFS it smashed many layers into one).

    12. Re:btrfs successor by Kjella · · Score: 3, Insightful

      Meh, personally I'd say LGPL so you don't get slightly incompatible file systems. With a BSD license the temptation is pretty big to keep the changes for yourself and say "works on our OS" while diverging from the common code base. Either that or a very detailed and exhaustive spec with a strict conformance test suite.

      --
      Live today, because you never know what tomorrow brings
    13. Re:btrfs successor by binaryspiral · · Score: 1

      Too right. Take those deduplicated blocks of your 8000 images, then place them on SATA storage... dirt cheap vast sata disks. When you go to pull those images - even a few hundred or thousand at a time - your SATA disks will populate the cache cards in your filer with most of the duplicate blocks - and your disks will never be your bottleneck when you're pulling them back down.

      NAS tech has gotten real interesting with the introduction of good and large cache, deduplication, and giant cheap SATA disks.

    14. Re:btrfs successor by Anonymous Coward · · Score: 0

      Let's see... 1,3,7,10,11 are all featured of ZFS. If only Sun has chosen a different license....

      I don't know about 11 though. Can't RAID5/6/z/z2/z3 can provide this already? Many commercial hardware RAID cards can background scrub the data for errors and rebuild incorrect information using the parity from RAID. ZFS provide similar functions implemented in software, though it goes a step farther with block level checksums that are validated on read.

      I would add 13 - Auto-Tiering of data blocks (not volumes like EMC FAST). This is going to be standard on all data storage arrays in the future.

    15. Re:btrfs successor by Courageous · · Score: 1

      Why? Just because a block of data is duplicated all over your filesystem that doesn't mean it's accessed all that frequently

      If it were, it would likely be in a the server's RAM.

      Anyway, there is a use case where duplicative tends to also be frequently used: duplicate virtual machine disk segments.

      So it's a fine idea, in theory.

      I'm with you, however, in favoring frequency of use over the mere fact of it's duplicativeness.

      C//

    16. Re:btrfs successor by Anonymous Coward · · Score: 0

      Even though btrfs isn't in production yet, we really need a successor to it not just to replace the filesystem, but to replace the LVM layer.

      What's wrong with LVM that can't be fixed?

    17. Re:btrfs successor by dgatwood · · Score: 1

      Problem is that I doubt any of the commercial UNIX vendors or BSDs would touch LGPL in their kernel, either. Doubly so if its v3. Maybe if you could make it purely a plug-in that just links against the kernel, you *might* be able to get some of them to ship LGPL v2 (hard to say) as long as you state that you have no intention of ever moving to v3. Having a loadable filesystem would greatly complicate booting, however, forcing a boot != root environment, which is pretty ugly.

      Now you could make it dual-licensed with LGPL and the Mozilla Public License. That might be palatable.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    18. Re:btrfs successor by DamnStupidElf · · Score: 1

      2: 64 bit CRCs. This way, a backup program just has to pull from the filesystem stored CRCs and it would know which files have been changed or not. This also helps with integrity checking.

      All your other bullet points are pretty reasonable, but CRCs (especially short ones) are really not what you want in this case. A cryptographic hash gives far more probability that the exact same hash implies the same data, on the order of a 1/sqrt(2^n) probability of two random blocks colliding for an n-bit hash. A 64 bit CRC is going to see collisions between two random blocks with a probability of 1/(2^32) (and trivial collisions if someone wants to do it), and there are way more than 4 billion distinct files out there. Relying on a hash for deduplication or for backup purposes (detecting whether a file is changed) is only safe with a cryptographic hash with no known collisions, and even then there are cheaper and safer ways to determine if a file has changed, for instance with a generation number for each file and the entire file system itself that monotonically increases with each file system operation. The latter won't let you deduplicate blocks but if you must have a 0% probability of data loss instead of 1/(2^128), it would be safer than a hash to tell if a file has changed.

      I'd also like to add something; individual file versioning. Recently I was playing around with both a NetApp and a ZFS FS and I was disappointed because restoring a single file from a snapshot in both systems seems to be limited to copying the data from the snapshot back into the live file system, even though the snapshot and the filesystem basically live in the same tree of data blocks and it should be possible to simply swap the metadata blocks to instantly restore a 1.3 PB file instead of waiting for it to copy out of the snapshot. Forgive me if I missed something important about snapshots in either system, but it looked to me like there was no way to restore a single file as fast as rolling back an entire filesystem to an earlier snapshot.

    19. Re:btrfs successor by mlts · · Score: 1

      A cryptographic hash is ideal, but it takes a lot of computer cycles to compute, and if a machine is writing 1k blocks to a filesystem, and keeps having to do a SHA-512 hash on a multi-gig database container, performance will hit the toilet.

      Another idea on a filesystem, but it would have to be handled by a HSM or cryptographic co-processor is automatically cryptographically signing blocks or files. Combine this with a filesystem that is WORM, and this might be a way to get inexpensive USB hard disks, and use them for medium term archiving while ensuring no data got tampered with. The closest I've seen to this concept is Nero's SecureDisk functionality.

    20. Re:btrfs successor by DamnStupidElf · · Score: 1

      The answer to performance problems is probably hardware acceleration. Intel, AMD, and Via have provided hardware acceleration support for AES and I imagine once SHA-3 is selected it will get support as well. Or just use AES in a mode with authentication like GCM or CCM, which AFAIK is how ZFS will maintain integrity for encrypted file systems.

      Combined with a secure timestamping service and a file system with a secure merkle tree of hashes, it would be possible to just sign the root hash of the file system at appropriate times and then securely determine at a later time if certain predicates were satisfied, e.g. "no files have been modified since the last timestamped signature, although new files may have been created" by comparing the hash trees of the file system at the two points in time where it was signed.

  22. ZFS has a bright future by MobyDisk · · Score: 1

    This summary makes it sound like ZFS is teetering on the edge of destruction. I thought ZFS was used all over the place by big database warehousing organizations. I went to a PostgreSQL conference a few years back and it seemed like everyone was using it. Is ZFS in such a weak position that one patent troll could have any significant impact on it?

    1. Re:ZFS has a bright future by Lunix+Nutcase · · Score: 1

      No, it's not. In fact Sun is pretty much winning at ever corner against NetApp in the patent fight.

    2. Re:ZFS has a bright future by fuzzyfuzzyfungus · · Score: 1

      Depending on what percentage of their product portfolio Coraid just suspended shipment of, they may be in serious trouble; but that isn't really Sun/Oracle/ZFS's problem...

  23. They can't do shit by Anonymous Coward · · Score: 0

    As long as ZFS is open and free, NetApp can cry and bicker all they want. There is no way they can stop it once ZFS is out in the wild.

  24. BtrFS by C_Kode · · Score: 1

    Maybe this is the reason BtrFS is maturing at a breakneck pace. :)

    1. Re:BtrFS by Anonymous Coward · · Score: 0

      Is is April already?

    2. Re:BtrFS by Anonymous Coward · · Score: 0

      Which means it will be stable and usable sometime around the year 4010. Kinda like RieserFS

    3. Re:BtrFS by Anonymous Coward · · Score: 0

      Maybe this is the reason BtrFS is maturing at a breakneck pace. :)

      How does BtrFS not step on the same patents ZFS is accused of?

      The same company owns both now, BTW.

  25. Ummm it's their technology by CPE1704TKS · · Score: 0, Troll

    They have a patent on this technology. They deserve the right to not have compete against their own technology. End of story. You can bitch and moan over whether or not patents are fair, but that's not the issue. The issue is that as of this moment, they have a legal patent and they spent years investing and developing their snapshot technology.

    Netapp for what it's worth is a decent company, I don't think they would just go out and start a patent war for no reason. I fully support them over Sun and ZFS on this one.

    1. Re:Ummm it's their technology by Lunix+Nutcase · · Score: 5, Informative

      Sorry buddy but the courts have ruled that ZFS doesn't infringe NetApp's patents. Read here and here. Cry more.

    2. Re:Ummm it's their technology by Anonymous Coward · · Score: 0

      I dunno, supposed A fellow and I both saw an application for a file system. Both spend years working on it and come up with similar ideas how to make it better. doesn't seem right to me that because you get a patent, or started 1 day before me, I get shafted in either case borrowing nothing from you.

    3. Re:Ummm it's their technology by Anonymous Coward · · Score: 0

      ZFS was found twice not to infringe on WAFL's patents.

    4. Re:Ummm it's their technology by Anonymous Coward · · Score: 0

      You should file an amicus brief to the court that is vehemently disagreeing with you on NetApp having a leg to stand on with their patent.

    5. Re:Ummm it's their technology by Anonymous Coward · · Score: 0

      In an east Texas court of law, of all places!

    6. Re:Ummm it's their technology by swordgeek · · Score: 1

      If your premise was right, your conclusion would be too.

      However, according to court findings, ZFS does not infringe on any of NetApp's patents. Unless an appeal succeeds, THAT is the end of the story.

      The issue is that as of this moment, they are threating lawsuits against small developers over non-infringing use of a different technology.

      NetApp used to be a fairly decent company, but they're slipping very fast in my books.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    7. Re:Ummm it's their technology by binaryspiral · · Score: 1

      I'm a happy NetApp customer and do not agree with you. ZFS has been on the opensource market long enough and documented well enough to be far out of the realm of patent-tolling.

      I had an interesting candid discussion with a NetApp engineer and he also thought their legal stance on this was "dickish" and causing a lot of bad feelings overall. He's in the mindset that if they're selling a box with opensource software - fucking great! We'll sell you the support and give back to the code base with features, bug fixes, and the like. But it was nice to hear a fellow grunt in the trench speak a bit of sanity from what seems to be an insane lawsuit.

  26. Here, here... by multimediavt · · Score: 4, Insightful

    Screw NetApp and their overpriced, underfeatured, patented crap. Really. I mean that.

    I totally and completely agree with that summary of NetApp

    With that out of the way, how does NetApp have any authority to enforce a license/patent on a piece of software they did not invent, nor hold the licensing for? ZFS was created by Sun and released under the CDDL. I am confused as to where NetApp fits into this equation other than being a troll of something that isn't even theirs to begin to troll with. I will do some digging online, but this is just effed up.

    1. Re:Here, here... by Anonymous Coward · · Score: 0

      Maybe they're saying Sun licensed some patents from them, which ZFS would otherwise infringe. ZFS on a Sun box: covered. ZFS anywhere else: violation.

    2. Re:Here, here... by mea37 · · Score: 4, Interesting

      Patents are funny that way. If I patent an invention and use it in Product X, and you come along and create Product Y which infringes my patent, then I can sue you (as you expect), and also I can sue anyone who uses, sells, or offers for sale Product Y. That's one of the reasons indemnity is a big deal when corporations look at OSS solutions, and it was the basis of many of SCO's legal threats back in the day.

      So you get the store down the street to sell Product Y, I can sue the store down the street. Bob buys Product Y from the store and puts it to use, in theory I can probably sue Bob. Sue enters into an OEM arrangement with you and embeds Product Y in Product Z, I can sue Sue, and Sue's distributors and users as well. All because I have a patent on something I did in Product X.

    3. Re:Here, here... by afidel · · Score: 2, Interesting

      Netapp is claiming that ZFS infringes on multiple core WAFL (the filesystem behind their filer products) patents. They may have a point insofar as software patents are enforceable. Time and again the Sun engineers behind ZFS have referenced WAFL as being the closest comparable filesystem to ZFS. The patent enforcement against ZFS started after Sun in their pre-Oracle takeover death throws came to Netapp expecting $$$ millions for supposed patent infringement.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    4. Re:Here, here... by Luminary+Crush · · Score: 5, Interesting

      So the story goes, this dates back to some interns who worked at NetApp and then went to Sun and perhaps influenced ZFS.

      The technology in WAFL is that of a pointer-based filesystem - which itself is pretty ingenious and is only now being feature-emulated (ZFS, BRTFS, etc).

      One can say what they want of Netapp's pricing, but the technology is extremely solid and simple to operate compared to managing Linux or Solaris boxes running a filesystem as a NAS; the snapshots are without I/O penalty and you can take a lot of them, the clustering is *FAR* simpler than anything happening on general-purpose OSes, the support for protocols is industry-leading (FCoE, NFSv4, SMB 2.0 - they have a codeshare w/ Microsoft and do not use a reverse-engineered Samba implementation or run any kind of Windows storage server like competitors do).

      ZFS has a lot of promise, but does not have nearly the performance that WAFL does (considering RAID-DP versus ZFS RAID6) and has only some of the feature set of mirroring, snapshot vaulting, filesystem and file cloning, WORM-compliance, etc. Companies don't want to bet their business on a science project of roll-your-own NAS which doesn't have the feature set the Netapps do, and no serious competitor (eg a company with the ability to financially stand behind the product) in the enterprise space has anything like the feature set.

      I work for a systems integrator and I've messed with hundreds of Netapps, Sun and Linux appliances, and competitors over the years. I use ZFS at home because I can't afford a Netapp (and wouldn't want to pay the electricity bill if I could!) but if I ran an IT department I'd put my data on a Netapp FAS over a ZFS appliance any day.

    5. Re:Here, here... by Anonymous Coward · · Score: 1, Funny

      Your pointy facts and reasonable tone aren't gonna play well in this town, kid. ;)

    6. Re:Here, here... by Courageous · · Score: 1

      ZFS has a lot of promise, but does not have nearly the performance that WAFL does

      WTF? A 7310, the low end Open Storage appliance, will TOAST a 3170. A 3170 can't even touch it.

      C//

    7. Re:Here, here... by sjames · · Score: 2, Insightful

      Sadly, all of that is true even if product Y was invented entirely from first principles by people with no knowledge of X, even if they did it at the same time as X was being invented.

      How anyone can claim that granting the patent to inventor X doesn't steal from inventor Y the fruits of his labor, I cannot say.

    8. Re:Here, here... by Captain+Segfault · · Score: 1

      ZFS has a lot of promise, but does not have nearly the performance that WAFL does

      WTF? A 7310, the low end Open Storage appliance, will TOAST a 3170. A 3170 can't even touch it.

      C//

      [citation needed]

    9. Re:Here, here... by Courageous · · Score: 1

      Corporate testing as part of a 6 month study involving a large intelligence customer. But if you find Sun's blogs showing > 1GB/s sustained r/w, these blogs don't lie. Performance is confirmed. My guess is the difference lies in NetApp's use of a RAID-4 variant in order to record parity.

      C//

    10. Re:Here, here... by Captain+Segfault · · Score: 1

      Corporate testing as part of a 6 month study involving a large intelligence customer. But if you find Sun's blogs showing > 1GB/s sustained r/w, these blogs don't lie. Performance is confirmed. My guess is the difference lies in NetApp's use of a RAID-4 variant in order to record parity.

      C//

      Ultimately that sort of throughput number is CPU bound -- if it weren't, it could be improved by adding more disks.

      Actually, WAFL's RAID-4/RAID-DP (with parity on separate disks) is just fine in a copy-on-write context. Distributing parity across the disks (ala RAID-5) primarily helps for random-small-write workloads. WAFL style filesystems don't *have* random small writes! Random writes become sequential writes, because the filesystem is free to choose where they go.

    11. Re:Here, here... by afabbro · · Score: 1

      ZFS has a lot of promise, but does not have nearly the performance that WAFL does

      WTF? A 7310, the low end Open Storage appliance, will TOAST a 3170. A 3170 can't even touch it.

      C//

      [citation needed]

      Welcome to Slashdot. Please don't confuse it with Wikipedia. We're discussing, not documenting here.

      --
      Advice: on VPS providers
    12. Re:Here, here... by Courageous · · Score: 1

      I don't deal particularly with the theory of the systems, just the practice of measuring the characteristics of the ones we receive into our labs. Our testing is thorough--much more than running IOzone or the like. We usually hit these systems from 10-20 simultaneous blades, all running multiple instances of a sustained bench.

      As an aside, a NetApp 6000-series filer is no more capable of higher throughput than their 3000-series filers are. This, I have directly from NetApp. As a procurer of many, many petabytes of their gear, not only do we tend to know at least as much as their own test teams about the performance of their systems, we also get direct access to about any internal NetApp resource we care to have direct access to.

      I stand by my remark. Open Storage platforms toast NetApp platforms, at least on throughput measurements. Never have tested IOPS, however, so I won't comment there.

      Open Storage is, of course, new. And lacks on horizontal integration features. Slow, it is not. Anyone who thinks otherwise hasn't tested it. Period.

      C//

    13. Re:Here, here... by mea37 · · Score: 1

      Concurrent innovation is a major problem with the existing system; the problem I have is, I can't think of any solution that's "always" just.

      I'm aware there are those who think the just solution is to do away with patents; I'm unconvinced. The ways in which the fruits of an inventor's labor can be stolen with no patent system are more common and more blatant; if you do away with patents I believe you have to replace them with something else, and you'll still have to deal with the problem of concurrent innovation in that replacement system.

      I suspect we're reaching a point where it becomes possible to document creative work sufficiently, so that we could set standards for proving independent and concurrent innovation and award both inventors with patents; but the system will still never be perfect. (With how much certainty can you "prove" you didn't know about another's work? How much expense can be imposed to involve 3rd parties in ways that really verify timestamps?)

    14. Re:Here, here... by sjames · · Score: 1

      It is a difficult question with a lot of judgment calls. I doubt any solution would be perfect.

      However, any move in that direction would beat a system that does not even acknowledge the possibility of independent invention.

      One possibility is that actually reducing a brilliant idea to practice takes a significant amount of time. An estimate of that time would be the basis for a window of co-invention, a period where a second inventor MUST have already had the idea and been underway before the first disclosed the invention through a patent or else he still wouldn't have it.

      Part of the problem too is that the USPTO doesn't seem to take the non-obviousness requirement very seriously. That naturally increases the number of instances where more than one person or group comes up with the idea.

      Perhaps while evaluating a patent application, the USPTO should publicly describe the problem the patent is meant to solve and offer a bounty to anyone who submits a solution resembling the patent in question. If it is REALLY non-obvious to people skilled in the art, there will be no such submission. Perhaps some cutoff point can be defined. If less than X submissions, all share in the patent. If more than X, it is ruled obvious and no patent issues.

    15. Re:Here, here... by turbidostato · · Score: 1

      "However, any move in that direction would beat a system that does not even acknowledge the possibility of independent invention."

      I see it the other way around. Since inventions have to be implementations (devices, with a detailed explanations of their functionalities, their blueprints and what not) posing novelty and non-obviousness it's obvious that the chances of simultaneous independent patentable inventions are slim.

      The fact that the case of simultaneous independent patentable inventions is far from scarce points out that such patents are not so novel and not so non-obvious so they shouldn't have to be granted to start with.

    16. Re:Here, here... by turbidostato · · Score: 1

      "Your pointy facts and reasonable tone aren't gonna play well in this town, kid. ;)"

      Funny but I'd say they are gonna play even worse in NetApp's town.

      How can be the violating technology so subpar to the original and still be violating a patent? If NetApp are so superior (and I don't doubt that) why so much a hassle for a uncompeting product? Probably questions nobody at NetApp want their prospective customers to ask to themselves.

  27. When? by Anonymous Coward · · Score: 0

    When is Larry Ellison going to order a hit job on David Hitz already?

  28. Re:Alternatives to NTP by tangent · · Score: 1

    You can keep your clocks accurate with something that isn't inherently unstable and complex, like RADclock. Or for leaf nodes, you can stay with the same basic protocol but jettison a lot of the complexity by switching to SNTP.

  29. To be clear by Junta · · Score: 1

    They are not saying "on a NAS", they are saying ZFS infringes WAFL, regardless of whether it is on a NAS. My impression is that currently some prior art is seeming to render those claims moot, but the crux of it is not it being on a NAS, the crux of it is ZFS as a technology versus WAFL as a technology regardless of context. The comparison of 'x on the internet' isn't quite spot on, it's at least better than that.

    In terms of going after the 'users' rather than the 'developers', the relationship here is certainly questionable. I've seen cases where something like this is brought upon a vendor who is legally entitled to pretty much pass the liability on to a supplier. If NAS vendor X gets sued and was using Solaris, they may have a contract to pass the entire mess to Oracle. However, if NAS vendor X is using FreeBSD, NAS vendor X may well be on the hook for use of that technology.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  30. don't worry by Anonymous Coward · · Score: 0

    Netapp can try all they might to destroy ZFS, but Oracle will take care of that for them.

    - Opensolaris delays
    - Cancelling OEM contracts with big time hardware manufacturers (e.g., HP)
    - enforcing Solaris contracts on Oracle hardware only
    - Charging, charging, charging for stuff that shouldn't be, especially when they need to be free to continue growth

    Such as shame for a nice piece of technology. Hopefully others like *BSD and Nexenta can take ZFS farther. Otherwise, I guess I'll have to wait for BtrFS.

  31. Hipocrites! Check out the founders patent ideals by jpswensen · · Score: 2, Interesting

    http://blogs.netapp.com/dave/2007/09/netapp-sues-sun.html The victim has become the offender.

  32. Again... by Junta · · Score: 3, Insightful

    NetApp is suing Sun (and now Oracle) over ZFS because they *claim* it violates patents they hold that they implemented in their own WAFL fs. WAFL does predate ZFS. NetApp was granted patents in WAFL that ZFS seems to also do, but prior-art may have caused those patents to be invalid.

    They are suing vendors that also use ZFS probably because those vendors are either licensing from Oracle (in which case indemnification may just pass this on) or are using FreeBSD, which makes the link between the vendor and Oracle a bit more odd and possible has the vendor on the hook for liability.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Again... by X0563511 · · Score: 1

      So... what, did they wait for Oracle to buy Sun so they had a juicier target?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    2. Re:Again... by Captain+Segfault · · Score: 1

      No, they sued Sun well before it was bought by Oracle.

  33. NetApp Patent Lawsuit by vm · · Score: 3, Insightful

    It might be worth reading through NetApp's original ZFS patent lawsuit vs Sun before making wild speculations. It seems to me that they are now trying to sue other, smaller companies after their original attempt to sue Sun had failed.

  34. Apple, Sun, ZFS by Anonymous Coward · · Score: 1, Informative

    I guess this explains OSX Server walking away from ZFS because of "license issues". Since Apple walked away in the 11th hour, I wonder if there is some real validity to NetApp's argument (at least legally).

    Apple walked away from ZFS because they and Sun couldn't come to a licensing/support agreement:

    > Apple can currently just take the ZFS CDDL code and incorporate it
    > (like they did with DTrace), but it may be that they wanted a "private
    > license" from Sun (with appropriate technical support and
    > indemnification), and the two entities couldn't come to mutually
    > agreeable terms.

    I cannot disclose details, but that is the essence of it.

    http://mail.opensolaris.org/pipermail/zfs-discuss/2009-October/033125.html

  35. It's not worth much, it seems by Mathinker · · Score: 1

    Do you usually spout off without actually trying to figure out the facts, basing your opinion on how you like / dislike the parties involved ("a decent company")?

    If you'd have read the previous posts, you'd have easily found a link to how Netapp vs. Sun/Oracle is going in court. It seems that the Patent Office and the courts seem to think that NetApp's patents are mainly invalid because of prior art. Oooops!

    On the other hand, I'm basing this on Sun/Oracle's info page about the lawsuit. Perhaps you'd like to show us the other side?

  36. You've misspelled.... by Anonymous Coward · · Score: 0

    Screw NetApp and their overpriced, underfeatured, patented crap. Really. I mean that.

    You've misspelled the word "Fuck" there.

  37. Anonymous Coward by Anonymous Coward · · Score: 0

    let's ask netapp to pay for Sun's NFS patents :)

  38. Re:NetApp -- stupid warnings? by Anonymous Coward · · Score: 0

    They'd do lot better just making fun of ZFS.

    It's a great filesystem -- it just doesn't actually do I/O worth a d*mn.
    You know, that stuff that actual filesystems usually do well. (Well,
    yes, sometimes it can write blocks at 1/3 the rate of any other
    second rate FS. What, you want it to *read* too?)

  39. That's the problem with the BSD license by Anonymous Coward · · Score: 0

    Netapps took the BSD code, put it at the heart of the netapp, added a bit of their own code, and hey presto the netapp was born. It's just a computer with disks and a cut down OS after all.

    The problem with the BSD license is that it allows the company or individual to take the code and close source it, and then apply more stringent licenses to their own applications which run with it.

    If you support the BSD license you've got no cause moaning about this.

  40. Yeah sure. by Anonymous Coward · · Score: 0

    (Me looks at tens of DB servers in Sun hardware, running ZFS, me works in big company, with people that can actually run benchmarks)

    Of course you very conveniently ommited those "show-stopping performance problems".

  41. No patent issues in SCO's threats by Anonymous Coward · · Score: 0

    SCO were real bastards, but none of their noise involved patents, because they don't hold any patents relevant to their linux threats.

    Their "SCO Source" scam was a very vaguely-worded offer to take people's money in exchange for the use of "SCO's Intellectual Property" (copyrights? patents? trademarks? - they wouldn't say) in Linux. They first alleged to the press that there was extensive and unauthorized literal copying of Unix code in Linux, then when that claim evaporated they claimed that "methods and concepts" were introduced into Linux by IBM in violation of their contract, then all of it got shot down when the courts ruled that SCO didn't even own the Unix copyrights (recently reaffirmed in a jury trial).

    I'm sure if SCO had some patents to throw into the mix, I'm sure we would have heard all about them.

  42. Phil, is that you? by BancBoy · · Score: 1

    I can sue Sue

    -ssudio!

    --
    [UID-HeinzIntel]
  43. But who invented NAS? by Anonymous Coward · · Score: 0

    Oh yeah, Sun. Since we're on the topic of patents here's some rare uncensored candor on how these things really play out between Schwartz, Jobs, Gates, etc... http://jonathanischwartz.wordpress.com/2010/03/09/good-artists-copy-great-artists-steal/

    Sun's patent arsenal is the 800 pound gorilla you don't want to tangle with.