LoginSign Up
← Back to all sparks
M

MooseFS

INFRA · APIS
Velocity0.0

Fault-tolerant, highly available distributed file system

moosefs.com ↗

A year of pure maintenance while the 4.x line clears the runway for MooseFS 5.

distributed-storagemaintenance-branchdata-integritymajor-version-prepsecurity-hardeningpackaging
◆Current state
MooseFS has shipped nothing but maintenance releases across the entire visible window. The last release carrying real capability work was 4.58.0, which fixed partial readdir and added directory-in-parts reading for multi-million-file directories; everything after it is correctness, packaging, and hardening. The 4.59.x releases are single-issue fixes reported by the community and by external security researchers.
◆Where it's heading
The line is consolidating rather than expanding. Two signals point the same way: 4.59.1 quietly updated license handling specifically so licenses can be refreshed ahead of MooseFS 5 migrations, and 4.58.4 spent its effort on Fedora spec files and a bootstrap rewrite. That is a project stabilizing a shipping branch and widening distribution while the next major version is built elsewhere.
◆Prediction
The 4.59.x branch keeps absorbing community bug reports at a low cadence until MooseFS 5 arrives; the license-compatibility work in 4.59.1 is the clearest evidence that migration is the next milestone rather than more 4.x features.

◆Recent moves

  1. 2mo ago

    MooseFS 4.59.2 restores background chunk integrity testing

    A single-issue release restoring background chunk testing, which had stopped running entirely so integrity verification scans were silently skipped. It fits the pattern of the 4.59.x branch: community-reported correctness work, no new surface.

    View source ↗
  2. 2mo ago

    MooseFS 4.59.1 fixes chunkserver OOB read, preps MooseFS 5 licenses

    Fixes an out-of-bounds read in the chunkserver, drops fadvise calls that added overhead without measurable benefit, and folds in findings from external security research. The license-handling change here is the release's most forward-looking line — it exists to let operators update licenses before moving to MooseFS 5.

    View source ↗
  3. 2mo ago

    MooseFS 4.58.4 adds Fedora packaging and logging refactor

    Build-system and logging work: Fedora spec files, a bootstrap.sh replacing autogen.sh, a printflike macro cleanup, and a silenced AddressSanitizer false positive. Distribution breadth rather than product change.

    View source ↗
  4. 7mo ago

    MooseFS 4.58.3 tightens storage-class validation and setuid

    Three small corrections — storage-class option validation, clearing auxiliary groups before setuid, and a descriptor resize bug. Explicitly a no-feature release, and characteristic of how the branch now operates.

    View source ↗
  5. 7mo ago

    MooseFS 4.58.2 adapts master-to-master timeouts for large RAM

    The most operationally consequential fix in this window: masters holding around 500 GiB of RAM could exceed a hardcoded 10-second fork limit during metadata sync. The leader now measures fork duration and raises follower timeouts itself, and MASTER_TIMEOUT is renamed MATOMA_TIMEOUT. This is the kind of scale-driven fix that comes from large production deployments, not from lab testing.

    View source ↗
  6. 10mo ago

    MooseFS 4.58.1 completes the flock segfault fix

    Completes a flock segfault fix that 4.57.7 had only partially addressed, plus CLI and ACL error-message polish. A follow-up release cleaning up after an earlier incomplete patch.

    View source ↗