3 ms·

A applaud your repertoire of OS experience. Perhaps because HAMMER (+HAMMER2) is BSD licenced, it might have better potential as a Linux kernel module. I also

A applaud your repertoire of OS experience. Perhaps because HAMMER (+HAMMER2) is BSD licenced, it might have better potential as a Linux kernel module. I also recommend trying out Bcachefs. It's developed on Debian so that's your best bet to give it a shot.

xte 8y ago
I tried out bcachefs in the recent past but... Well... for now it's only a classic, usable, stable fs... All the nice features are only promises in development, no snapshot, no replication, nothing is there only a stable fs that seems no different than ext... On license of course there is a problem but if we have zfs ported well... I think it can be circumvented, only I fear that in GNU/Linux land (especially -Linux part) there are too many people that do not consider at all modern needs, most of them are programmer's with no sysadmining background, they do not even understand why we desperately need new storage and "Big&Powerful" are absolutely happy because actual paleolithic storage solution means business opportunities... Remember Andrew Morton with it infamous "rampant layer violation" against zfs or NetApp that ask SUN "to unfree" zfs to avoid disrupting storage market... IMO we have lost after Ubuntu ditch desktop the opportunity of a generic end-users GNU/Linux desktop and due to hw&sw evolution commercial-side we desperately need to innovate again as a FOSS community, DragonflyBSD is a very little substantial single-man-show project but it innovate, GNU keep innovate a bit despite a super-slow evolution and GuixSD is IMO the future of any OS, like it's "father" NixOS, the first IaC-builtin OSes in the world, but we need more, and with more manpower instead of wasting energy in evanescent crappy web-derived tech from GnomeShell extensions to Electron-based (cr)apps. Storage in that sense is the basis since on storage we can design package managers and init systems, so in turn installers and in turn the rest of the OS. Having a modern, powerful storage, something like Plan9 propose years ago, something like Hammer, zfs, nilfs2, stratis etc are a thing that need to evolve and spread in GNU/Linux world or we can't really evolve...
- loeg 8y ago
  > Well... for now it's only a classic, usable, stable fs ... nothing is there only a stable fs that seems no different than ext... It's a CoW filesystem, which should provide some inherent crash/power-fail safety that ext does not have (at least, as usually configured — and data logging has huge overhead).
  - xte 8y ago
    Sorry my not-so-good English sometimes make me express concept in a convoluted/wrong way, on my previous post s/no/not much/ (different) than ext, it's an interesting project however today is only that IMO a thing to follow, prize, support but not use regularly apart if you want to help it's developments... On logging overhead... Well, yes and no, the logfs I tried do have overhead at garbage collection/cleaning but that overhead does not seems really important in practical terms. It demand a bit of careful design of storage layout and load prediction but nothing more than that. I do not see practical advantage for most server usage however I see significant advantage for some server usage and certainly for desktop usage. Also potential future development is certainly interested... Imaging a package manager integrated with a logfs how effective can be only in terms of "immutable servers/IaC" applications, imaging how NixOS/GuixSD generations can easily and instantly switch, how can you deep and easily analyze datasets and systems... Also overhead is there, a bit, today, but tomorrow can be significantly reduced if we have physical storage developed with logging in mind.
loeg 8y ago
Sure, HAMMER(2) is licensed for portability elsewhere. The trick would be adapting Dragonfly's VFS interface (and locking!) to your target platform. It has diverged from FreeBSD in ways that make that non-trivial, and Linux's system is even more different.

xte 8y ago

I tried out bcachefs in the recent past but... Well... for now it's only a classic, usable, stable fs... All the nice features are only promises in development, no snapshot, no replication, nothing is there only a stable fs that seems no different than ext... On license of course there is a problem but if we have zfs ported well... I think it can be circumvented, only I fear that in GNU/Linux land (especially -Linux part) there are too many people that do not consider at all modern needs, most of them are programmer's with no sysadmining background, they do not even understand why we desperately need new storage and "Big&Powerful" are absolutely happy because actual paleolithic storage solution means business opportunities... Remember Andrew Morton with it infamous "rampant layer violation" against zfs or NetApp that ask SUN "to unfree" zfs to avoid disrupting storage market... IMO we have lost after Ubuntu ditch desktop the opportunity of a generic end-users GNU/Linux desktop and due to hw&sw evolution commercial-side we desperately need to innovate again as a FOSS community, DragonflyBSD is a very little substantial single-man-show project but it innovate, GNU keep innovate a bit despite a super-slow evolution and GuixSD is IMO the future of any OS, like it's "father" NixOS, the first IaC-builtin OSes in the world, but we need more, and with more manpower instead of wasting energy in evanescent crappy web-derived tech from GnomeShell extensions to Electron-based (cr)apps. Storage in that sense is the basis since on storage we can design package managers and init systems, so in turn installers and in turn the rest of the OS. Having a modern, powerful storage, something like Plan9 propose years ago, something like Hammer, zfs, nilfs2, stratis etc are a thing that need to evolve and spread in GNU/Linux world or we can't really evolve...

loeg 8y ago
> Well... for now it's only a classic, usable, stable fs ... nothing is there only a stable fs that seems no different than ext... It's a CoW filesystem, which should provide some inherent crash/power-fail safety that ext does not have (at least, as usually configured — and data logging has huge overhead).
- xte 8y ago
  Sorry my not-so-good English sometimes make me express concept in a convoluted/wrong way, on my previous post s/no/not much/ (different) than ext, it's an interesting project however today is only that IMO a thing to follow, prize, support but not use regularly apart if you want to help it's developments... On logging overhead... Well, yes and no, the logfs I tried do have overhead at garbage collection/cleaning but that overhead does not seems really important in practical terms. It demand a bit of careful design of storage layout and load prediction but nothing more than that. I do not see practical advantage for most server usage however I see significant advantage for some server usage and certainly for desktop usage. Also potential future development is certainly interested... Imaging a package manager integrated with a logfs how effective can be only in terms of "immutable servers/IaC" applications, imaging how NixOS/GuixSD generations can easily and instantly switch, how can you deep and easily analyze datasets and systems... Also overhead is there, a bit, today, but tomorrow can be significantly reduced if we have physical storage developed with logging in mind.

loeg 8y ago

Sure, HAMMER(2) is licensed for portability elsewhere. The trick would be adapting Dragonfly's VFS interface (and locking!) to your target platform. It has diverged from FreeBSD in ways that make that non-trivial, and Linux's system is even more different.