Ross ROSS = Recommend OSS · open-source software intelligence for agents

moosefs/moosefs

MooseFS Distributed Storage – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System / Software-Defined Storage observed · 2026-08-28

github.com/moosefs/moosefs · homepage · C · GPL-2.0 (copyleft) observed · 2026-08-28

Health v2 · maintenance only

83/100

  • Activity 83
  • Release rhythm 72
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 42
  • age_days: 3871
  • days_rel: 107
  • days_push: 107
  • n_releases_24m: 12

Full methodology

Adoption not part of the score

1999 stars · 239 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

MooseFS is an open-source, POSIX-compliant, petabyte-scale network distributed file system written in C. It spreads data across commodity servers with configurable replication, snapshots, trash bin, quotas, and block storage, presenting itself to clients as a single mounted resource via FUSE.

Use cases

  • build a petabyte-scale storage cluster from commodity hardware
  • mount a fault-tolerant POSIX file system shared across many servers
  • store backups with configurable replication and a trash bin for deleted files
  • provide block storage for VMs and databases
  • run high-performance computing cluster storage
  • scale storage capacity by adding servers without downtime
  • take atomic snapshots of files while they are being written
  • apply per-directory quotas and storage tiering policies

When to choose

  • you need a POSIX-compliant distributed file system that mounts like a local disk
  • you want fault tolerance with no single point of failure on commodity hardware
  • you need dynamically expandable capacity and on-the-fly hardware removal
  • you run HPC or large data workloads requiring parallel access to many files
  • you want snapshots, quotas, and data tiering built into the file system

When to avoid

  • you only need object storage for cloud-native apps (use S3-compatible systems instead)
  • you need a single-node file system with no cluster overhead
  • you require native Windows client support in the free edition (Windows client is PRO-only)
  • you need geo-replication across datacenters without the PRO edition
  • your workload is small enough that NFS or a local disk would suffice

Facets

application · maturity stable

file-system backup self-hosted developer-tools microservices infrastructure-as-code self-hosted files big-data windows bsd cross-platform self-hosted distributed-file-system posix-compliant fuse software-defined-storage erasure-coding replication block-storage hpc petabyte-scale fault-tolerant devops linux macos

4 sources

Member repositories

RepositoryRoleHealth v2
moosefs/moosefsmain83

For agents

markdown · JSON · MCP: product_card(name="moosefs/moosefs")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem