16 ms·
ZFS is the FS for Containers in Ubuntu 16.04
- robbyt 11y agoHow is this possible, legally? Based on my basic understanding of the ZFS license, it's not possible to legally distribute ZFS and GPL code (linux kernel) together.
- deleted 11y ago[deleted]
- ZenoArrow 11y agoZFS has been available in Linux for a long time, the licence restrictions hold it back from being included in the kernel, but it's available as a FUSE filesystem. https://en.wikipedia.org/wiki/Filesystem_in_Userspace https://en.wikipedia.org/wiki/Filesystem_in_Userspace EDIT: Looking through the comments in the article, it's being suggested this isn't using the FUSE implementation of ZFS, and that somehow it's part of the kernel. Not sure how they've legally managed to do that! EDIT 2: Looks like it's a kernel module, as other comments here suggest.
- cjbprime 11y ago> Not sure how they've legally managed to do that! Answer: They haven't. :) They've just created a GPLv2 violation.
- ZenoArrow 11y agoIt looks like they got around it by distributing OpenZFS as a kernel module. If that's permitted for closed source kernel blobs, it's probably fine for this code too.
- cjbprime 11y agoIt is not permitted for closed source kernel blobs; those are violations too.
- ZenoArrow 11y agoSo using a kernel module for the closed source NVIDIA driver for Linux is a GPL violation? As far as I understood, the GPL only applies for code that is directly linked to it. A call to an external library (e.g. a kernel module) wouldn't necessarily apply. The code is being delivered as separate binaries.
- cjbprime 11y ago> So using a kernel module for the closed source NVIDIA driver for Linux is a GPL violation? Yes. Your understanding isn't correct. With NVIDIA, there's this complicated dance where you download source code from nVidia for the kernel module, then compile it on your own machine and use it -- you aren't violating copyright because you don't distribute the kernel module that you compiled for yourself on your own machine. But that kernel module does indeed violate GPLv2, and you can't distribute it legally, and neither could Canonical or nVidia (which is why they do the dance above instead).
- ZenoArrow 11y ago> "But that kernel module does indeed violate GPLv2, and you can't distribute it legally, and neither could Canonical or nVidia (which is why they do the dance above instead)." If that's the case, then why doesn't the FSF sue Linux kernel developers over licence violations? There are clearly pre-compiled binary blobs distributed along with the mainline kernel (otherwise there would be no need for the Linux-libre project to exist: https://en.wikipedia.org/wiki/Linux-libre https://en.wikipedia.org/wiki/Linux-libre ). There's little point having a licence if there's no consequences for breaking it. I suspect they don't because it's not a simple case, and that such a measure would be somewhat counterproductive for their cause.
- 11y ago
- henesy 11y agoIt says that it is OpenZFS specifically.
- davexunit 11y agoWhich is still CDDL licensed and thus GPLv2 incompatible. Here's the copyright file from the relevant commit to the Xenial kernel tree: http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/diff/zfs/COPYRIGHT?id=b65ce14d3445e8fe69b5d59aaaf2699319714179 http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/diff/z... The majority of the code in the ZFS on Linux port comes from OpenSolaris which has been released under the terms of the CDDL open source license. This includes the core ZFS code, libavl, libnvpair, libefi, libunicode, and libutil.
- alcari 11y agoOpenZFS was forked from the original Sun/Solaris ZFS code base, which Sun made available regularly. It's still CDDL.
- parasubvert 11y agohttp://zfsonlinux.org/faq.html#WhatAboutTheLicensingIssue http://zfsonlinux.org/faq.html#WhatAboutTheLicensingIssue It is fine if it is a kernel module.
- pilif 11y agoThat's what they say - others claim that even a dynamically loaded module is producing a derivative and thus you're not allowed to distribute a non-GPL-ed binary module. Matthew Garret (a kernel developer and thus a shared copyright holder of the kernel) is of the opinion that linking a binary ZFS module is not legal: https://twitter.com/mjg59/status/700021939708915712 https://twitter.com/mjg59/status/700021939708915712 https://twitter.com/mjg59/status/700073945064611841 https://twitter.com/mjg59/status/700073945064611841 https://twitter.com/mjg59/status/700074164435091456 https://twitter.com/mjg59/status/700074164435091456 As a copyright holder, he is potentially in the position of suing canonical over this (and he doesn't like them very much, so he just might)
- unethical_ban 11y agoI know zealots are necessary to keep a balance. I've typically appreciated the utility of people like RMS to the free software movement. That said, Matt Garret's Captain Ahab-like zeal of keeping one of the most useful pieces of open-source code away from Linux, while taking potshots at Ubuntu, is really off-putting. I guess I'm not so pure. Which is why I run my file server with BSD. I'm really excited to see ZFS functional in 16.04, and in fact, that got me to install the pre-beta just to mess with it.
- davexunit 11y ago>That said, Matt Garret's Captain Ahab-like zeal of keeping one of the most useful pieces of open-source code away from Linux, while taking potshots at Ubuntu, is really off-putting. Your response to a large company violating the license that Linux is distributed under is to blame Matthew Garret for pointing it out?
- davexunit 11y ago>How is this possible, legally? It's not. Canonical has blatantly violated the GPL before and gotten away with it.
- dragonwriter 11y ago> How is this possible, legally? My understanding is that it isn't under the theory of what counts as a derivative work requiring a license (and, thus, what is subject to GPLv2 in the first place) espoused by the FSF, however, I believe that view has been hotly disputed as to its accuracy under US copyright law (at least) for about as long as the GPL has existed and never been tested in court. The FSF, in general -- as is unsurprising for entity that relies on maximally leveraging copyright protections to achieve its ends -- holds to a fairly maximalist view of the legal rights of copyright owners.
- acd 11y agoZFS is great, happy its included in Ubuntu 16.04 by default.
- e40 11y agoAnyone know of Red Hat has plans to include it in default installations?
- jgworks 11y agoDoes this include a fix for this bug? https://github.com/zfsonlinux/zfs/issues/1548 https://github.com/zfsonlinux/zfs/issues/1548
- faragon 11y agoCheck if this works for your case: echo > myfile P.S. not the "solution", but may help in case you fill the disk by accident, and need to make some room before a remount cycle. P.S.2. this could help also when your disk is already 100% full, without enough space for deleting files -not enough space for new inodes- (I tested that case on ZFS NAS with no left space at all, and worked).
- wmf 11y agoThis post only mentions LXD. Will ZFS be used for Docker?
- klapinat0r 11y agoWhether docker in aptitude will be configured to use zfs by default is impossible to guess. It is however possible to say that ZFS is already supported by docker, e.g.: https://docs.docker.com/engine/userguide/storagedriver/zfs-driver/ https://docs.docker.com/engine/userguide/storagedriver/zfs-d...
- awalton 11y agoDocker switched to Alpine Linux by default, so there's that hurdle... Not to mention the giant legal question mark of loading CDDL code into a GPLv2 kernel.
- mverwijs 11y agoOne of the ideas of containers / virtualization is that the host operating system (Ubuntu, in this case) has as little to do as possible with the VM / container (Alpine, in this case). Running an Alpine container using Docker on an Ubuntu host will work just fine.
- mentat 11y agoThat's for the container package management system, not the host storage system.
- baldfat 11y agoI don't understand why BTRFS isn't gaining more support in Linux. I prefer BTRFS to ZFS with Fuse.
- ryao 11y agoZFSOnLinux does not use FUSE.
- wstrange 11y agoThis isn't ZFS in Fuse - it is a native kernel module. BTRFS has yet to reach the stability of ZFS.
- jlappi 11y agoI wonder if the licensing of the ZFS kernel module will cause any issues with its inclusion in Ubuntu?
- l1ambda 11y agoCanonical's lawyers OK'd it which is why they are including it.
- nailer 11y agoWeird. What changed in the last 10+ years?
- ryao 11y agoPeople decided to listen to lawyers who read the licenses instead of listening to statements by people claiming to know how things work without actually reading either license or asking a lawyer about it. That is quite literally the only change.
- nailer 11y agoDidn't Sun use lawyers to design the CDDL to precisely prevent this situation?
- anilgulecha 11y agoThis can be game-changing for the NAS/SAN industry. I'm surprised their lawyers gave an OK, where FSF, SFLC and friends have given a thumbs down. If their interpretation is good, suddenly the large AIX/Solaris dominated storage boxes open up to a LOT of ubuntu-based/ubuntu-derived competition. Exciting times..
- anilgulecha 11y agoBTW, if ZFS is used for the root filesystem, say hello to insanely simple OS upgrades and roll-backs :)
- StavrosK 11y agoThis is my #1 question. Can we use it for the root FS? If so, that's amazing, as there are already btrfs-based tools for snapshotting every time you run apt, etc.
- helper 11y agoThere are a couple of open bugs[1][2] related to grub and ZFS that make it a little tricky to get ZFS on your root volume, but it is doable: https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-install-Ubuntu-16.04-to-a-Native-ZFS-Root-Filesystem https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-install-Ubu.... I expect those issues to be resolved before 16.04 is released. Even with those fixes, the interactive installer doesn't support ZFS yet so you will still need to drop to a shell to actually setup your zpool and your partitions. [1]: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/ https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727... [2]: https://bugs.launchpad.net/ubuntu/+source/zfs-initramfs/+bug/1530953 https://bugs.launchpad.net/ubuntu/+source/zfs-initramfs/+bug...
- Filligree 11y agoYou could also use NixOS, which is even better at this. :) And also has native support for ZFS, btw.
- 11y ago
- nisa 11y agoLet's see how this works out. It's probably better and more stable than btrfs but this is not complicated... ZFS on Linux had issues with ARC (especially fast reclaim) and some deadlocks and AFAIK cgroups are not really supported - e.g. blkio throttling does not work. Would be great is they got this ironed out but I would be wary. Still great news!
- AstralStorm 11y agoAdditional problem is that in-kernel latencies of both btrfs and ZFS are on the high end. Essentially a show stopper for professional audio work and maybe some kinds of video streaming. Trying to completely escape disk IO in those uses is very limiting. A comparable solution using LVM and/or mdraid with ext4 on top has much better latency behavior. Sorry for no benches for you, but feel free to run a quick check using latencytop and ftrace. Phoronix has some performance comparisons if you want them.
- semi-extrinsic 11y ago> Essentially a show stopper for professional audio work (...). Trying to completely escape disk IO in those uses is very limiting. Could you expand on that? I mean, an hour of mono uncompressed 192 kHz/24bit audio is almost exactly 2 GB. Compared to professional audio equipment, 128 GB of RAM isn't very expensive ( < $2000), and that would let you keep 64 one-hour maximum-def tracks in memory. Why do you need to read from the disk with any frequency?
- satbyy 11y agoFor those who missed it, Debian Project Leader Neil McGovern gives details [1] about how licensing issues were resolved so that ZFS can be in Debian now. It is distributed as source-only dkms module. [1]: http://blog.halon.org.uk/2016/01/on-zfs-in-debian/ http://blog.halon.org.uk/2016/01/on-zfs-in-debian/
- cjbprime 11y agoThough that's not relevant to this news -- Ubuntu isn't using DKMS, they put it directly into their kernel tree, violating GPLv2.
- baldfat 11y agoOpenZFS ! I can't see why this has blown up as a violation when people didn't actually read the announcement. EDIT : ZFS is licensed under the Common Development and Distribution License (CDDL), and the Linux kernel is licensed under the GNU General Public License Version 2 (GPLv2). While both are free open source licenses they are restrictive licenses. The combination of them causes problems because it prevents using pieces of code exclusively available under one license with pieces of code exclusively available under the other in the same binary. In the case of the kernel, this prevents us from distributing ZFS as part of the kernel binary. However, there is nothing in either license that prevents distributing it in the form of a binary module or in the form of source code. http://open-zfs.org/wiki/Main_Page http://open-zfs.org/wiki/Main_Page
- throwaway2048 11y agoOpenZFS is CDDL liscensed and GPL incompatable.
- ryao 11y agoOnly if you build it into the kernel binary image loaded by the bootloader. Otherwise, it is an independent module.
- 11y ago
- ThePhysicist 11y agoZFS is nice but as far as I understand the Linux version does not yet have support for copy-on-write clones using e.g. "cp --reflink=always", which to me was reason enough to choose BTRFS instead. Apart from this the two systems seem to be quite comparable (from my limited user perspective), with BTRFS having quite good Linux support as well. Maybe someone more experienced with the COW functionality could comment on that as it would be very interesting to hear how other people deal with this.
- aidenn0 11y agoI've used both ZFS on both BSD and OpenIndiana, and I've used btrfs on linux. as recently as 4.0.5 As of 4.0.5 btrfs was IMO completely unusable as a daily file system. Some examples of issues I ran into: 1) System became unbootable with the version of btrfs I had installed and I had to use either an older or newer kernel to recover 2) I have a periodic backup of my mailbox that runs, and when it runs my system becomes completely unusable until it completes. The same script running on zfs on bsd and with ext4 or reiser3 on linux would show I/O slowdowns, but I could still use my machine. 3) In general I would run into other minor issues and the consensus in #btrfs was that since my kernel was more than 3 months old, it was probably fixed in the latest version, and why would somebody using an experimental filesystem not be tracking mainline more closely? [edit] To be fair, here's some issues with ZFS: 1) Do not ever accidentally enable dedupe on commodity hardware; it will slowly consume all your RAM if you aren't on a sun server (where 64GB of RAM is a resource constrained environment), and there aren't effective ways to undo dedupe, other than copying all the data onto a different pool. 2) You can't shrink a pool. Hugely annoying, apparently non-trivial to solve.
- rsync 11y ago"To be fair, here's some issues with ZFS:" Let me add: 3) Do not allow a pool to exceed 90% capacity ... and probably don't let it exceed 85%. ZFS does not have a defrag utility and it badly needs one. You can permanently wreck zpool performance by running it up past 90% capacity - even if you later reduce capacity back down to 75-80%. You can sort of fix it if you add additional top level vdevs to the zpool, thus farming out some IO to the new set of disks, but it's still going to be performance constrained forever. The only solution is to create a new pool and export the data to it. This is unacceptable, by the way. It is not at all reasonable to require a filesystem to stay below 80% capacity (our target "full" number at rsync.net) nor is it acceptable that hitting 90% is a (performance) death sentence. When you consider that you might have already sacrificed 25% of your physical disk just for the raidz2/raidz3 overhead, being constrained to 80% means you're only using 60% or so of your physical disks that you bought. ZFS needs defrag. Badly.
- davexunit 11y agoSorry to be a downer folks, but Canonical is violating GPLv2 by merging ZFS into their kernel tree. The CDDL and GPL are incompatible. https://twitter.com/mjg59/status/700073945064611841 https://twitter.com/mjg59/status/700073945064611841
- shmerl 11y agoThey don't need to merge it into the kernel though. If it's installed as a kernel module post installation, it doesn't violate GPL.
- davexunit 11y ago>They don't need to merge it into the kernel though. Then could you explain what this commit is: http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/zfs?id=b65ce14d3445e8fe69b5d59aaaf2699319714179 http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit... Canonical cannot ship ZFS in binary form. Kernel modules are derivative works of the kernel, and thus they must be distributed under GPLv2.
- ryao 11y agoA user editing the wiki posted incorrect information that he inferred from the use of DKMS. It happens.
- 2trill2spill 11y agoZFS is not a derivative work of the Linux kernel seeing as it was developed on Solaris and later Illumos.
- davexunit 11y agoZFS on Linux doesn't work unless it's linked against interfaces provided by Linux. This is a derivative work, and thus the combined work must be distributed under GPLv2.
- shmerl 11y agoOpenZFS, not ZFS. Those are different beasts now.
- ansible 11y agoHuh, well that's interesting news. I'm currently setting up a couple servers using LXC with btrfs. I ending up choosing LXC (as opposed to LXD, docker, rkt, etc.) because I wanted something relatively straight-forward. I just wanted some containers I could create, log in to and configure. If this was a bigger deployment, I'd take the time to use docker or something else. But for now, just being able to get going quickly is nice. For backup / failover, I can btrfs send / receive the containers to another host and start them there.
- baldfat 11y agoBTRFS uses less memory so I prefer BTRFS to ZFS for containers.
- ryao 11y agoHow did you determine that? The two should use about the same amount of memory. The only diffence is that ZFS uses ARC and btrfs uses the page cache. ARC is not reported the same way as the page cache though, which might give the appearance of requiring more.
- stubish 11y agoYeah, thats all fine and good. Nothing to announce with lxc/lxd + btrfs because it already works fine :) I do like the wizard to easily setup the zfs backend, rather than you needing to manually replace /var/lib/lxc with a btrfs partition or however you are doing it. I've been using lxc + btrfs daily for quite a while, setting up and tearing down hundreds of containers on a busy day. I stopped using lxc snapshots after I had a btfs subvolume that would crash the system when I mounted it. After that, no problems.
- ansible 11y agoI stopped using lxc snapshots after I had a btfs subvolume that would crash the system when I mounted it. After that, no problems. That's unfortunate. What operating system version were you using at the time? I've actually switched to using Ubuntu 15.10 for the container hosts so that I can get a more recent version of the btrfs tools. The intention is to upgrade to 16.04 as soon as is reasonable, and leave them there for a long time.
- weitzj 11y agoAnd what about machines without ECC RAM? I thought this is the idea for using ZFS in the first place. Or is the ECC "requirement" only important for raidz?
- ryao 11y agoECC is a prequisite for any filesystem to behave as intended. ZFS needs ECC just as much as other filesystem does. e.g. ext4, XFS, etc.
- Filligree 11y agoWithout ECC RAM, you're far more likely to get uncorrectable / unnoticeable corruption. This is not unique to ZFS, and it doesn't make ZFS worse than other filesystems. But since the reason you'd use ZFS is often to avoid any corruption, it's tradition to advise the use of ECC.
- frik 11y agoSo is ZFS more prone to defects without ECC than let's say EXT4 or NTFS? I would like to buy a notebook with ECC ram, but Intel doesn't care.
- RotsiserMho 11y agoNo, all are equally prone to errors if a bit in RAM is unexpectedly flipped. My understanding is that ZFS requires more RAM and possibly more CPU than other filesystems and those costs aren't worth it if you're going to use RAM that can't detect errors anyway.
- usefulcat 11y agoNo, no one is saying that ZFS is more prone to defects without ECC. Lack of ECC increases the risk of corruption for any filesystem. The reason you hear more about ECC in the context of ZFS is that data integrity is a key feature for many who choose to use ZFS.
- X-Istence 11y ago
- mikegerwitz 11y agoThere's a number of licensing comments here. Linking with CDDL modules is explicitly mentioned by the FSF: https://www.gnu.org/licenses/license-list.html#CDDL https://www.gnu.org/licenses/license-list.html#CDDL I'm not going to comment further on any implications of Debian/Ubuntu's decisions, since IANAL.
- g1n016399 11y agoUbuntu is doing it totally differently to Debian. Debian uses the compile-at-install-time workaround but Ubuntu ships binaries, which is a GPL violation.
- ryao 11y agoThe FSF referring to the creation of executable files, shared libraries and executable files dynamically linked to those libraries. They do not mean LKMs, which is what a ZFS kernel module is.
- AstralStorm 11y agoIn case of Linux specifically, Linus voted on the practice to provide so-called GPL entrypoints and symbols. (MODULE_SYMBOL vs MODULE_SYMBOL_GPL) This is explicitly allowed in GPL as a clause about relaxing provisions. (exception clauses such as one in Glibc or GCC) If ZFS kernel module uses only those permitted symbols, it's likely fine from legal standpoint. If not, there is a problem.
- mikegerwitz 11y agoAh, thanks for that information! I'll read into that.
- ryao 11y agoThe current ZFSOnLinux codebase does not touch any GPL exported symbols when built as a loadable kernel module.
- jpgvm 11y agoShame how most of the conversation devolved into licensing rubbish. Almost none of us are qualified to speak on that, leave it to the lawyers - which I assure you Canonical did too. With that out of the way, ZFS is by far and away the best filesystem for container workloads. Hopefully we will get deeper quota and I/O throttling support soon. I have been using ZoL in production for many years now thanks mostly to the work of Brian Behelendorf and Richard Yao. So if you find yourselves here thanks for all the work you have put into making ZoL awesome.
- 2trill2spill 11y ago> Shame how most of the conversation devolved into licensing rubbish. Almost none of us are qualified to speak on that, leave it to the lawyers - which I assure you Canonical did too. This a million times, It will be nice to have the illumos community, the FreeBSD community and now the Linux community contributing to one piece of core software. It's especially amazing considering most open source operating system projects don't share major kernel subsystems.
- ryao 11y agoYou are very welcome. I am happy to hear that it has been working well for you. :)
- brendangregg 11y agoThis is great news, and we're already using ZFS in production on Ubuntu in a few areas at Netflix (not widespread yet). Ubuntu 16.04 also comes with enhanced BPF, the new Linux tracing & programming framework that is builtin to the kernel, and is a huge leap forward for Linux tracing. Eg, we can start using tools like these: https://github.com/iovisor/bcc#tracing https://github.com/iovisor/bcc#tracing
- 2trill2spill 11y agoHow does BPF compare to dtrace?
- brendangregg 11y agoIf you browse some of the _example.txt files in https://github.com/iovisor/bcc/tree/master/tools https://github.com/iovisor/bcc/tree/master/tools , you'll see it's solving the same problems we used to solve with DTrace, plus a few extra. Here's a couple of the ZFS examples (since we're talking ZFS): # ./zfsslower Tracing ZFS operations slower than 10 ms TIME COMM PID T BYTES OFF_KB LAT(ms) FILENAME 06:31:28 dd 25570 W 131072 38784 303.92 data1 06:31:34 dd 25686 W 131072 38784 388.28 data1 06:31:35 dd 25686 W 131072 78720 519.66 data1 06:31:35 dd 25686 W 131072 116992 405.94 data1 06:31:35 dd 25686 W 131072 153600 433.52 data1 [...] # ./zfsdist Tracing ZFS operation latency... Hit Ctrl-C to end. ^C operation = 'read' usecs : count distribution 0 -> 1 : 0 | | 2 -> 3 : 0 | | 4 -> 7 : 4479 |****************************************| 8 -> 15 : 1028 |********* | 16 -> 31 : 14 | | 32 -> 63 : 1 | | 64 -> 127 : 2 | | 128 -> 255 : 6 | | 256 -> 511 : 1 | | 512 -> 1023 : 1256 |*********** | 1024 -> 2047 : 9 | | 2048 -> 4095 : 1 | | 4096 -> 8191 : 2 | | [...] The current BPF interface we're using (bcc) is Python for the frontend, and C for the backend. It's currently much more verbose than DTrace, and involves writing 10x the lines of code. For some immediate use cases at Netflix, that's not a big problem, as staff will be using BPF via a GUI (Vector), not writing these tools directly. There's also high level features it's still missing (like tracepoints and sampling), so what will be in Ubuntu 14.04 won't do everything, but it will do a fair amount: most of those _example.txt's. Some use a newer BPF interface (linux 4.5), and we've been putting the legacy versions in an /old directory specifically for Ubuntu 16.04 users.
- dekhn 11y agoI'm a conservative user, so I don't change my filesystem until my preferred distribution (Ubuntu) supports installing an FS to the root with a provided, supported kernel module. This is a huge deal for me; I will probably install a new FS on my main file server and move from ext4 to zfs.
- xenophonf 11y agoIn case you ever feel less conservative, here's how I set up my MacBook Pro to dual boot Mac OS X/FileVault and Ubuntu/ZFS/LUKS: https://gist.github.com/xenophonf/2e2d1a1550b0fb8dae98 https://gist.github.com/xenophonf/2e2d1a1550b0fb8dae98
- wstrange 11y agoOracle could put this whole legal wrangling to rest by changing the license to GPL. I am dreaming I suppose.
- protomyth 11y agoThey don't own the copyright on the patches, so it wouldn't exactly be effective.
- ryao 11y agoThis is correct.
- dmm 11y agoThey might not own the openzfs patches but they definitely own all of the zfs code. They had all contributors sign CLAs to reassign copyrights. That's how they were able to end opensolaris.
- protomyth 11y agoI'm pretty sure ZFS as last released is not as valuable without the OpenZFS contributions.
- cthalupa 11y agoFrom my understanding, Sun back in the day, and Oracle now, cannot release everything under the GPL due to contractual obligations. There's a reason they wrote the CDDL in the first place. I can't find the talks now, but I believe Cantrill and others have spoken about this previously. My memory is somewhat fuzzy, so I might be wrong on this.
- ryao 11y agoThat was Solaris and that was regarding putting all of it under an OSS license, not necessarily the GPL. There were a few tiny bits that they just could not open source. Oracle could release their fork of ZFS under any license they wish.
- melted 11y agoApple should replace the abomination that is HFS+. They almost did a few years ago, but pulled the code at the last moment.
- beagle3 11y agoDragonfly BSD's HAMMER2, when it is even half done (that is, stable for one node), is probably a much better (technical) choice than BTRFS or improving HFS+, and probably a much better legal choice than ZFS.
- e1ven 11y agoApple's choice to drop ZFS may have been influenced by the lawsuit Sun was dealing with at the time. http://www.computerworld.com/article/2539287/data-center/apple-s-support-for-zfs-may-drag-it-into-open-source-lawsuit.html http://www.computerworld.com/article/2539287/data-center/app... I'd wager they wouldn't want to adopt ZFS without an explicit license and legal indemnity from Oracle.
- ryao 11y agoI heard from a former Sun executive that Apple wanted indemnification following netapp's lawsuit. They had spent a long time negotiating over that before they had something mutually acceptable and it was supposed to be signed the day Oracle's acquisition of Sun finished. That left it up to Larry Elison, who refused to sign it and Apple decided to try its luck improving HFS+.
- zanny 11y agoThey could adopt btrfs. Darwin is open source, right?
- melted 11y agoBTRFS is still not mature, and there's a license incompatibility as well. And it's controlled by Oracle all the same. If Apple replaces the filesystem they'll likely roll their own.
- dkarapetyan 11y agoUbuntu is always slightly behind and slightly ahead of the curve. Why are they digging their heels in with lxd when docker and rkt make so much more sense?
- heavenlyhash 11y agoThis is great news. Among other incentives, ZFS has some truly excellent features for improving reliability. ZFS's built-in checksums, for example, can result in much happier stories during the onset of disk failures: where a RAID array can quietly return incorrect sector contents without noticing, and be unable to correctly differentiate between the correct and not-so-correct sectors in the event of disk loss followed by disagreements discovered during rebuilds, ZFS simply does the right thing by making checks during normal operations, and uses the same checks to confidently do the right thing during recovery. And snapshotting. Oh, snapshotting. On the other hand, I've always wished we could get a modern re-take on ZFS. As anyone who's tried it will tell you: dedup in ZFS essentially doesn't work. ZFS, internally, is not built on content-addressable storage (or, it is, but since splitting of large files into blocks doesn't take any special actions to make similar blocks align perfectly, it doesn't have anywhere near the punch that it should). As a result, dedup operations that should be constant-time and zero memory overhead... aren't. Amazing though ZFS is, we've learned a lot about designing distributed and CAS storage since that groundwork was laid in ZFS. A new system that gets this right at heart would be monumental. Transporting snapshots (e.g. to other systems for backups... or to "resume" them (think pairing with CRIU containers)) could similarly be so much more powerful if only ZFS (or subsequent systems) can get content-addressable right on the same level that e.g. git does. `zfs send` can transport snapshots across the network to other storage pools -- amazing, right? It even has an incremental mode -- magic! In theory, this should be just like `git push` and `git fetch`: I should even be able to have, say n=3 machines, and have them all push snapshots of their filesystems to each other, and it should all dedup, right? And yet... as far as I can tell [1], the entire system is a footgun. Many operations break the ability receive incremental updates; if you thought you could make things topology agnostic... Mmm, may the force be with you. [1] https://gist.github.com/heavenlyhash/109b0b18df65579b498b https://gist.github.com/heavenlyhash/109b0b18df65579b498b -- These were my research notes on what kind of snapshot operations work, how they transport, etc. If you try to build anything using zfs send/recv, you may find these useful... and if anyone can find a shuffle of these commands with better outcomes I'd love to hear about it of course :)
- ryao 11y agoThe deduplication code works, but each deduplication operation requires 3 serial IOS to lookup the information needed to check if deduplication is possible and if they are in aches, that becomes painful fast on storage with low IOPS. On my workstation where I have enough memory that the results of all of the lookups naturally fit and high IOPS storage, the deduplication code runs well. You would have a similar problem designing a system that perfectly deduplicates data at the record level if you tried.
- mark_l_watson 11y agoSorry in advance if this is a stupid question: my main Linux system is a laptop with a small SSD drive. I would like to organize my entire digital life on a 2 TB external USB drive, and be able to maintain a clone of everything on at least one other 2 TB USB drive. Is ZFS the right tool for this?
- ryao 11y agoI have backups stored on a double mirror of USB drives. The USB interface is fragile, but it does work. I cannot say that I recommend USB drives though, but if you are using USB, ZFS is not at any disadvantage versus other filesystems. For what it is worth, I am this ryao: https://github.com/zfsonlinux/zfs/graphs/contributors https://github.com/zfsonlinux/zfs/graphs/contributors
- dsr_ 11y agoIt's a tool that could work. You can use zfs send/receive to clone a zfs filesystem or snapshot. You could also use rsync, duplicity, or a bunch of other tools. The major zfs advantage here is that all your files get integrity checking.
- lmm 11y agoIf you're talking about a "static" setup where you attach both at the same time or not at all, yes. ZFS export before unplugging, ZFS import when plugged in, I can see it working very nicely. If you're talking about using one of them most of the time and syncing occasionally then any filesystem will do, you'll want a user-level tool for doing the sync (probably - sibling did mention zfs send which I don't have any experience with).
- berdario 11y agoI read some time ago that ZFS is definitely NOT the right tool for laptop/external storage, unless you actually have a zpool with mirroring/raidz (which means you have to always keep the devices connected). The reason is that when ZFS detects corruption, it'll lock down the whole fs... and prevent reading/recovery data from it, as recovering data from raidz is the expected solution in that case. I tried to google again for the description of this issue, but I couldn't find it... I found this otoh: https://groups.google.com/a/zfsonlinux.org/forum/#!topic/zfs-discuss/VEV-uKUzP14 https://groups.google.com/a/zfsonlinux.org/forum/#!topic/zfs... And things aren't that obvious, apparently: > Even without redundancy and "zfs set copies", ZFS stores two copies of all metadata far apart on the disk, and three copies of really important zpool wide metadata. Whichn means that this might not actually be a problem after all
- obelisk_ 11y agoAnyone know if this applies for Lubuntu as well? I use Lubuntu on my rencently bought new desktop for the default of LXDE. I intend to upgrade my desktop on which I put Lubuntu 15.10 (I bought a computer without OS so as not to pay the Windows tax) to Lubuntu 16.04 because I understand it'll be based on LXQt, the successor to LXDE (and it's not a matter of newer is better -- I am a fan of Qt) and also because I think Lubuntu 16.04 will be an LTS release and I've been very happy with the stability of Lubuntu 14.04 LTS which my previous main computer was and is running.
- sengork 11y agoI wonder how this would work under shared storage model for container clusters (eg. Mesos). NFS does not cut it for all use cases (eg. DBs).