ZFS is excellent for database development! Create a snapshot before you try something that mess up your data and instantly restore it! If your development database is a few gigabytes, this will save you a lot of time.
True, but you can/could easily do that with LVM snapshots and merges too. We snapshot the databases (copy on write) which is instant, then if we want to roll it back we lvm merge and remount. Everything is pretty instant and it doesn't matter what filesystem you want to use.
Do LVM snapshots still cause massive performance degradation?
ZFS is excellent for database development! Create a snapshot before you try something that mess up your data and instantly restore it! If your development database is a few gigabytes, this will save you a lot of time.
Not ZFS, but filesystem snapshot technology in general. Ten years ago we were force to move from a NetApp (which included snapshot) filer to a SAN with no snapshot and that was our biggest impact. Database changes went from being minutes to hours because the DBAs now wanted to do full backups before any change.
True, but you can/could easily do that with LVM snapshots and merges too. We snapshot the databases (copy on write) which is instant, then if we want to roll it back we lvm merge and remount. Everything is pretty instant and it doesn't matter what filesystem you want to use.
Do LVM snapshots still cause massive performance degradation? https://www.nikhef.nl/~dennisvd/lvmcrap.html
ZFS is under the CDDL while Java is not under the CDDL. CDDL is an open-source licence just as the GPL.
> CDDL is an open-source licence just as the GPL But incompatible with the GPL, which mostly explains the current situation of ZFS on Linux.
It's the GPL that's incompatible with the CDDL and not the other way around, which is an important distinction. Other than other GPL variants and BSD and MIT style licenses, the GPL has restrictions which make it pretty much incompatible with everything.
Anyone here think that a "ZFS in the cloud" that anyone could inexpensively export a ZFS snapshot (or volume) to would potentially be a business model (offsite backups, etc.)?
I'm tempted to write an article: Who Needs ZFS When You Got Git, but the title IS the article. Don't get me wrong, I looove ZFS, and from a quick scan this article looks like a good intro to ZFS, particularly for someone familiar with git.
Author is not actually suggesting replacing your version control with ZFS. From the first paragraph:
> Of course, I'm not seriously suggesting you'd ditch a "proper" version control system, but it gives a good sense of what's possible at the file system level.
> Notably missing is support for merging, which ZFS does not have direct support for as far as I'm aware. That insight is critical, especially now that we are heading towards Dropbox Infinite, IPFS, Ceph and so many other non-centralized file systems. Syncing is not a solved problem at all yet. Advances can bring the same revolution as 3-way merging did to SCMs, previously dominated by file-locking mechanisms.
What was that replicated filesystem back in the 90s that promised to be the next NFS, but with disconnected operation and merging when you came back online? Coda, that's right. I had such high hopes for it in my move to using a laptop as my primary machine, but never got it working despite several attempts at it. Admittedly they weren't more than a couple hours at a given time...