mrkeyoor.comAsk

rustfs/rustfstested 24 Aug 2026commit 3b0a28d

rustfs review

RustFS merits an acceptance trial for teams seeking an Apache 2.0 S3-compatible object store.

  • Build timed out
  • Tests timed out
43 sto install
  • 1,222 packages
Self-Hostedevaluationupdated 01 Nov 2026
+176stars / 7d

Evaluate RustFS if you need an Apache 2.0 object store with S3 compatibility, but require deployment acceptance tests before entrusting it with authoritative data. RustFS is a distributed object storage system built in Rust. Our run on August 24, 2026, at commit 3b0a28d did not establish runtime readiness: both build and test commands timed out.

Verdict

RustFS merits an acceptance trial for teams seeking an Apache 2.0 S3-compatible object store. Our August 24, 2026, run at 3b0a28d established unfinished source commands, not failed storage operations. The current README reports broader availability than that checkout, and the supplied issue histories include fixes and corrected diagnoses. Choose a pinned deployment, test your clients and recovery procedures, and make the migration decision from those results.

We ran it

Lab card: what happened when we ran rustfs
Lab card from our sandbox run
Screenshot of rustfs (rustfs.com/download)
rustfs.com/download
Install✓ · 43s1222 packages
Build✗ timed out · 900s
Tests✗ timed out · 900sran, no count parsed
Repo2385 files~1,221,515 lines of source · 53.2 MB · 28 CI workflows · Dockerfile

Answers from our run

Does rustfs build from source?

Dependencies installed in 43 seconds (1222 packages), and the build failed. We cloned commit 3b0a28d into a clean Debian container with 3 CPUs and no project-specific setup.

Do rustfs's tests pass?

We could not finish them: the suite was still running after 15 minutes in our container.

Who should not use rustfs?

Buyers who need this review to establish production durability, throughput or complete S3 compatibility: our sandbox did not test those properties.

What are the alternatives to rustfs?

SeaweedFS, MinIO. RustFS merits an acceptance trial for teams seeking an Apache 2.

Setup2/5Retained assessment: both source commands timed out at 900 seconds in our sandbox; the documented Docker route was not tested.
Docs4/5Explicit runtime-identity, mount-permission, feature-boundary and topology guidance supports this documentation assessment; deployment success was not verified.
Community4/5Detailed supplied issue discussions show artifacts, technical responses and closure follow-through; this score does not measure adoption or guaranteed support.
Maturity2/5Retained assessment of the recorded release-candidate scope: distributed mode was under testing and our run supplied no runtime validation; current-release maturity was not rescored.

Discussed on

  1. hnRust MinIO Alternative38 points
  2. hnShow HN: RustFS – Migrate from MinIO via simple binary replacement10 points
  3. hnRustFS vulnerability: Hardcoded token with privileged access6 points
  4. hnHardcoded Auth Token in RustFS (CVE-2025-68926)5 points
  5. hnRustFS: High-performance distributed object storage for MinIO alternative5 points

Who it’s for

Storage operators comparing an Apache 2.0 S3-compatible server with their existing storage.
Developers who can budget for source compilation and test their exact clients.
Teams able to evaluate recovery, upgrades and topology changes with disposable data before migration.

Who it’s NOT for

Buyers who need this review to establish production durability, throughput or complete S3 compatibility: our sandbox did not test those properties.
Contributors expecting a completed source build within our 900-second command limit on this sandbox.
Operators planning to grow a single-node single-drive deployment in place: the current README requires a new deployment and migration through S3.

Setup reality

Our sandbox recorded an installation step of 43 seconds and 1,222 dependencies. It had 3 CPUs and 12 GB of RAM. The build and test commands each reached the stored 900-second limit, with exit code 124 and timedOut set to true. The retained build tail is empty; the test tail contains compilation output, including RustFS 1.0.0-rc.3 crates and tokio-test. Neither outcome establishes a compiler defect or a failed assertion.

The documented Docker route requires mounted data, log and applicable TLS paths to be accessible to the container's runtime identity, UID/GID 10001:10001. We did not launch that container or verify uploads, downloads or deletion. Prepare mount permissions, replace default credentials and configure TLS before evaluating a network-accessible instance.

What our run establishes

Our run on August 24, 2026, checked commit 3b0a28d in the lab-rust:1 sandbox. Our build and test commands each timed out after 900 seconds. Installation completed in 43 seconds, and the stored dependency count is 1,222.

The harness records each command's outcome, elapsed time, exit code and timeout flag separately. Its overall build_failed status must be read alongside those details: both unfinished commands have exit code 124 and timedOut set to true. The build has no retained output tail. The test tail ends with compilation output rather than a test-result footer, so it does not establish whether any assertions ran elsewhere in the log. Parsed test counts are absent.

This was a source setup attempt, not a storage workload trial. We did not verify a running server, Docker deployment, S3 client compatibility, object durability, node-loss recovery, KMS restart recovery, upgrades or throughput. The audit result is absent, and scan coverage is unknown. The testing methodology explains the publisher's command-outcome reporting and limits; its current text does not establish which methodology version governed this older run. No new execution underlies this correction.

For contributors, the useful result is a budget constraint: this sandbox did not complete either command within its limit. A longer run or a different build environment would be needed to determine completion. For storage buyers, the next useful step is an acceptance trial against a pinned deployment, with recoverable data and explicit failure tests.

Current feature status differs from the tested checkout

RustFS documents S3 compatibility for supported features and an Apache 2.0 license. Those are reasons to investigate it, while compatibility with your application's operations remains something to verify.

The README at our recorded commit marked distributed mode, lifecycle management and RustFS KMS as under testing. The supplied current README marks all three available. That is a change in the project's stated status, not a result from our sandbox. The current README defines available features as shipped and covered by its CI gates; we did not independently run those gates.

The current README also draws boundaries that matter to deployment planning. Swift and SFTP require opt-in build features. MinIO on-disk compatibility is a preview behind rio-v2, outside the default build, and MinIO-encrypted objects are not readable by RustFS. A single-node single-drive deployment cannot expand in place or become a pool; moving to a multi-drive topology requires a new deployment and S3 migration. Consult the RustFS README before choosing the initial layout.

The listing report was corrected and closed

Issue #6218 initially described listed keys whose HEAD and GET requests returned 404. Later investigation changed the interpretation of the captured examples. On August 29, the reporter confirmed that version-qualified reads returned the complete object bodies. The problem involved a stale per-node version stack after delete markers reached only part of the cluster, rather than demonstrated loss of those captured objects.

The issue was closed through #6977 on August 31. In the supplied September 1 follow-up, the reporter still planned field validation on a build containing the fix. Closure records an upstream resolution; that extract does not establish the outcome of the planned validation. A useful acceptance test therefore compares flat listings with reads during lifecycle deletion and rolling maintenance, while preserving version IDs and per-node evidence when results disagree.

The supplied readiness report, #6286, was also closed after a fix, with a maintainer requesting a retest. It should not be presented as an unresolved defect in the current project. We did not reproduce it or verify its resolution. Likewise, no independently fetched extract for the earlier KMS restart report was supplied, so this review does not repeat it as an established current limitation.

Alternatives depend on the job

SeaweedFS documents S3 object storage and a POSIX file system over the same data. Evaluate it as a replacement candidate when shared file and object access is a requirement. That is a documented capability, not evidence that it will outperform RustFS or meet your durability requirements. Its README provides the deployment paths to investigate.

The MinIO repository states that it is no longer maintained. Its README points readers to AIStor Free for a standalone edition and AIStor Enterprise for a distributed edition with commercial support. Treat those as separate product evaluations; the old community repository is not a default recommendation for a newly maintained deployment. MinIO's client tooling can also be a complement to an S3 evaluation rather than a replacement storage server.

How to read the retained scores

The numerical scores below retain the recorded assessment. The rubric is 1 for substantial documented obstacles, 2 for material constraints requiring evaluation, 3 for adequate evidence for the stated scope, 4 for detailed supporting evidence with clear limits, and 5 for strong evidence including independent verification in the relevant scope. These are editorial judgments, not benchmark results or production certifications.

Setup ease is 2 because neither source command completed within the sandbox limit, while Docker remains a documented but untested route. Documentation is 4 for explicit mount-permission instructions, feature boundaries and topology warnings. Community is 4 for the supplied issue discussions' detailed artifacts, technical responses and follow-through; it does not measure adoption or support response guarantees. Maturity remains the recorded 2 for the evaluated release-candidate scope, where distributed operation was marked under testing and our runtime validation was absent. It is not a fresh numerical assessment of the current release.

Alternatives

ProjectWhat it isPick it when
SeaweedFS gh↗Documents an S3 object store and a POSIX file system over the same data.Evaluate it as a replacement candidate when applications need both file and object access; verify its behavior with your workload.
MinIO gh↗An AGPLv3 S3-compatible object storage repository that now states it is no longer maintained.Consider it for an existing installation's maintenance or migration assessment. For a new deployment, separately investigate the AIStor editions named by its README.

What people are saying

  1. [github-trending] rustfs/rustfs

Sources

  1. RustFS README
  2. Ghost object report
  3. Distributed readiness outage report
  4. KMS restart persistence report

More self-hosted reviews