4 ms·
Between the ZFS-like features and the advertised "novel copy-on-write metadata" scheme, I would not be surprised if it was partially based on DragonFly's HAMMER
by mioelnir 10y ago
Between the ZFS-like features and the advertised "novel copy-on-write metadata" scheme, I would not be surprised if it was partially based on DragonFly's HAMMER/HAMMER2 filesystem.
- ahl 10y agoIt would be a strange kind of NIH that excluded ZFS but welcomed HAMMER...
- feld 10y agodifferent licensing and HAMMER demands significantly less memory
- AceJohnny2 10y agoLicensing.
- deleted 10y ago[deleted]
- mindajar 10y agoIf you poke around in the the APFS kernel extension, it's not a very big binary, given the feature set. (It's a 550K extension, compared to the 2.5MB zfs.ko on FreeBSD.) I haven't disassembled it yet, but I'd wager that APFS is layered atop Core Storage btrees/CoW. Since that code's been shipping since 2011, maybe APFS stabilizes faster than a true greenfield filesystem? (That does leave me wondering how interesting an open-source APFS would be without an open-source Core Storage.)
- Freaky 10y ago> It's a 550K extension, compared to the 2.5MB zfs.ko on FreeBSD hammer.ko is 494KB in the latest DFBSD, for those wondering the obvious.
- Wildgoose 10y agoI was thinking the exact same thing! It would be fantastic if they actively helped with HAMMER2 development.