Hacker News new | ask | show | jobs
by linsomniac 1263 days ago
Kind of wish HAMMER2 development switched to Linux and got a big boost in visibility and exposure. I've been excited about it for ~15 years, but I've never gotten enough round-tuits to put it to any real use. I'd love to switch my rsync+ZFS snapshots backup servers over to HAMMER, but ZFS works great except for deduplication.
2 comments

>I'd love to switch my rsync+ZFS snapshots backup servers over to HAMMER

Why don't you do that? You don't need linux to be happy, quite be opposite actually, install DFly and have fun.

As I said, I haven't made the time: it's not just installing DFly, I've got to convert all my backup code to work with HAMMER, track down issues, figure out updates, etc... Really the thing I want to try about HAMMER is the deduplication, ZFS deduplication perpetually seems to require more RAM than I have to give it

HAMMER2 is really impressive, and Matthew Dillon's work on it and the rest of DragonFly is spectacular. I guess I feel like DragonFly is limiting the exposure that HAMMER could have. I know long ago there was an early aborted effort to port it, not sure it was ever very serious.

Linux has a history of rejecting any actually good file systems.

This includes but isn't limited to Tux3 and ReiserFS 4 & 5.

What was the story with tux3? It looks like it "read and wrote it's first file" in August 2008, and then had it's last update a few months later in Dec 2008. If if never got out of heavy development phase, being in the kernel wasn't the right place for it.

ReiserFS 4, it's been a very long time since I thought about it, but ISTR there were technical issues the needed to be addressed to bring it in mainline, and personality issues didn't help any, but that's a fading memory. Which is unfortunate, because ReiserFS had some great features.

On the other hand, btrfs made it into the kernel fairly easily, as a counterpoint. It's a unusual situation because it's been fairly broken and in heavy development for much of it's life in kernel, but early in-kernel versions were actually working fairly good (in my experience, I ran some fairly early versions in my laptop for a year or two with good luck, then an OS update brought in a new version and I had terrible corruption issues.