Linked by Thom Holwerda on Mon 15th Nov 2010 23:37 UTC, submitted by comay
Thread beginning with comment 450153
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
I hope OpenIndiana/Ilumos switch to HammerFS. I also hope that Illumos abandons the OpenSolaris DDK and switch to a port of IOKIT for easier development and sharing of knowledge with OSX users. Personally I wished for a port of XNU open source parts to Illumos with filling missing bits with OpenSolaris.
Yikes.
The deduplication code only hit the 2.9 branch of DragonFly on the 7th of November. Not something that is advertised as a stable feature for the current version of the HAMMER FS.
http://leaf.dragonflybsd.org/mailarchive/commits/2010-11/msg00043.h...




Member since:
2005-07-06
Actually data de-dup is one of the features of HAMMERFS
http://en.wikipedia.org/wiki/HAMMER
* Keeps configurable coarse-grained filesytem history (60 days daily by default).
* History and snapshots are accessible via the live filesystem.
* Near real-time log-less streaming mirroring to slaves or backups.
* Slave can have different retention parameters.
* CRC checksumming of data and metadata.
* Minimal remount time (no fsck required).
* Designed from the ground up for large fan-out mirroring.
* Support for very large file-systems (up to 1 exabyte).
* Offline recovery after a catastrophic failure is possible.
* Ability to re-optimize the layout in the background, on a live filesystem.
* Data de-dup
* Future - multi-master clustering
* Future - data compression
I've given DragonflyBSD a tinker and what I notice is there isn't the same sort of performance penalty as I notice with ZFS so that alone makes me a big booster for the file system; first impressions are sure to win me over and HAMMERFS has definitely done that