# moosefs/moosefs

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

Repository: https://github.com/moosefs/moosefs
Canonical: https://ross.abutalabs.com/products/moosefs
Homepage: https://moosefs.com
Language: C
License: GPL-2.0
License Family: copyleft
Topics: software-defined-storage, posix, filesystem, distributed-storage, distributed-computing, high-availability, storage, posix-compliant, ditributed-systems, erasure-coding, snapshots, backup, block-storage, file-storage, file-systems, fuse-filesystem, hpc, hpc-cluster, hpc-storage, distributed-file-system
Last push: 2026-05-18T12:06:51+00:00

## Health v2 (maintenance only)
Score: 83/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 83, release rhythm 72, longevity 100
- inputs: {"age_days": 3871, "days_push": 107, "days_rel": 107, "gap_med": 42, "n_releases_24m": 12}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1999, forks 239 (observed 2026-08-28T04:06:03.758813+00:00)

## What it is
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
- artifact type: application
- maturity: stable
- function: file-system, backup, self-hosted, developer-tools
- domain: microservices, infrastructure-as-code, self-hosted, files, big-data
- platform: windows, bsd, cross-platform, self-hosted
- tags: distributed-file-system, posix-compliant, fuse, software-defined-storage, erasure-coding, replication, block-storage, hpc, petabyte-scale, fault-tolerant, devops, linux, macos

## Member repositories
- moosefs/moosefs (main) score 83

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:03.758813+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:02:10.845658+00:00, confidence not recorded.
  - readme: https://github.com/moosefs/moosefs (fetched 2026-08-28T04:06:03.758813+00:00, sha eb5f7cbe27db)
  - homepage: https://moosefs.com (fetched 2026-08-29T10:42:05.805502+00:00, sha bc25c39170c9)
  - site_page: https://moosefs.com/advantages-and-features.html (fetched 2026-08-29T10:42:05.808001+00:00, sha 6b832552fdad)
  - site_page: https://docs.moosefs.com (fetched 2026-08-29T10:42:05.809688+00:00, sha a31f47d1b253)
- Data as of 2026-08-30T08:39:29.467469+00:00.