mrkeyoor.comAsk

juicedata/juicefstested 03 Oct 2026commit adcca1c

juicefs review

Trial JuiceFS if shared POSIX access justifies operating and recovering a metadata database alongside object storage.

  • 550 packages
27 sto install
    Dataevaluationupdated 31 Oct 2026
    +26stars / 7d

    Trial JuiceFS when shared POSIX access over object storage is worth operating a separate metadata database. JuiceFS stores file data in object storage. Our run on October 3, 2026, at commit adcca1c checked npm installation; build and test steps were skipped. It did not establish that the Go client or a filesystem deployment works.

    Verdict

    Trial JuiceFS if shared POSIX access justifies operating and recovering a metadata database alongside object storage. Our October 3, 2026 run at adcca1c completed npm installation but skipped build and tests. Before adoption, build the Go client and validate concurrent access, metadata restore and client upgrades with your chosen database, object store and application interface.

    We ran it

    Lab card: what happened when we ran juicefs
    Lab card from our sandbox run
    Screenshot of juicefs (juicefs.com)
    juicefs.com
    Install✓ · 27s550 packages · 114 MB
    Buildn/ano build script
    Testsn/ano test script
    Known vulns310 critical · 22 high · 6 moderate · 3 low (npm audit)
    Repo1113 files~177,998 lines of source · 51.2 MB · 40 CI workflows · tests dir

    Answers from our run

    Does juicefs build from source?

    Dependencies installed in 27 seconds (550 packages), and the project has no separate build step. We cloned commit adcca1c into a clean Debian container with 3 CPUs and no project-specific setup.

    Does juicefs have tests you can run?

    Not through a standard command: the project exposes no test script or target that our harness could run.

    Does juicefs have known vulnerabilities in its dependencies?

    npm audit flagged 31 known advisories in the dependency tree at the time of our run.

    Who should not use juicefs?

    Teams that cannot maintain a separate metadata service.

    What are the alternatives to juicefs?

    s3fs-fuse, Alluxio Open Source. Trial JuiceFS if shared POSIX access justifies operating and recovering a metadata database alongside object storage.

    Setup2/5A client, metadata engine and data store must work together; our npm installation did not validate that deployment.
    Docs5/5Supplied documentation covers architecture, access methods, metadata choices, compatibility, caching tradeoffs and telemetry.
    Community4/5Last push on 2026-08-26 and 14,736 stars.Editor’s note: Supplied primary extracts do not establish current contributor participation, support responsiveness or issue-resolution outcomes.
    Maturity4/5Upstream commits to a stable storage format and documents specific maintenance fixes; our run did not test recovery or upgrades.

    How we score

    Discussed on

    1. hnA distributed Posix file system built on top of Redis and S3219 points
    2. hnJuiceFS is a distributed POSIX file system built on top of Redis and S3186 points
    3. hnJuiceFS 1.0,a cross-cloud file system that is Posix, HDFS, S3 compliant27 points
    4. hnA shared Posix file system built on top of Redis and S319 points
    5. hnJuiceFS: A distributed Posix file system built on top of Redis and S316 points

    Who it’s for

    Storage teams that need shared file access over object storage and can operate and recover the metadata database.
    Kubernetes operators evaluating shared volumes through the documented CSI driver.
    Hadoop teams evaluating the documented Java SDK.
    Engineers prepared to validate their chosen client interface, database and object store together.

    Who it’s NOT for

    Teams that cannot maintain a separate metadata service.
    Users who need original files to remain directly accessible through ordinary object-storage tools.
    Buyers seeking measured filesystem throughput, deployment validation or recovery results from this review.
    Operators unable to test metadata recovery and client compatibility before adoption.

    Setup reality

    Our run on October 3, 2026, at commit adcca1c used our lab-node:22 sandbox with 3 CPUs and 8 GB RAM. The stored harness result records npm installation succeeding in 27 seconds with exit code zero. Build and test steps were skipped with the reason "no script".

    The harness detected Node and Go, selected Node as primary, and recorded npm scripts for documentation linting and link checking. It also detected a Makefile and a tests directory. The skipped steps concern the selected npm scripts; they do not show that JuiceFS lacks build targets or tests.

    Stored parser summaries report 550 dependencies and 114 MB. Separately, the raw npm tail reports 674 added packages and an npm duration of 21 seconds. These records have not been reconciled, and neither raw figure replaces the stored summary. Audit scan coverage is unknown because scannedPackages is absent.

    The recorded npm audit result contains 31 advisories: 22 high, 6 moderate and 3 low, with none critical. These are recorded dependency advisories, not findings from a security review of JuiceFS. We did not build the Go client, mount a filesystem, deploy an interface or test a storage workload.

    Should you trial JuiceFS?

    Trial JuiceFS if your applications need shared POSIX access and your team can own metadata recovery alongside object storage. The client joins those two storage layers. That architecture makes the metadata database part of the adoption decision: the bucket contains blocks, while the database holds the mappings that make them files and directories.

    What our October 3 sandbox run established

    Our run on October 3, 2026, at commit adcca1c checked npm installation; build and test steps were skipped. The stored install result is 27 seconds with exit code zero. Our sandbox used lab-node:22 with 3 CPUs and 8 GB RAM. This correction uses that existing record and includes no new execution.

    The harness records success flags, exit codes, elapsed time and captured command tails. It records skipped steps separately, with a reason. Here, both skipped steps say "no script". Detection found Node and Go but selected Node as primary; the listed npm scripts concern documentation checks. A Makefile and tests directory were also detected. The result therefore describes the npm path selected by our harness, rather than the availability of Go build or filesystem tests.

    We did not validate a Go build, FUSE mount, CSI deployment, concurrent filesystem access, recovery or runtime performance. Skipped tests are not failed tests. The compatibility results printed in the upstream README are upstream results, not tests performed by our sandbox.

    How to read the install and audit figures

    The stored parser summaries report 550 dependencies and 114 MB. The raw install tail separately reports 674 added packages and an npm duration of 21 seconds. We have not reconciled those records against complete logs, so the raw output does not replace the stored 27-second result or dependency summary. These summaries do not establish exhaustive unique test coverage.

    Npm audit recorded 31 advisories: 22 high, 6 moderate and 3 low, with none critical. The record has no scannedPackages field, so audit scan coverage is unknown. The advisory total does not establish the security of the Go client or a deployed filesystem.

    The MrKeyoor testing methodology explains command recording and the limits of these measurements. Its supplied extract was retrieved after this run; the current methodology page does not establish which procedure version the October 3 run used.

    What the metadata database changes

    JuiceFS stores file data in object storage. Its architecture documentation says the metadata engine stores names, permissions, directory structure and file-data mappings. Original files cannot be found directly in the bucket; it contains numbered blocks instead. A trial should include restoring metadata and checking that the recovered namespace can still read the stored data.

    The README documents close-to-open consistency, atomic metadata operations and global file locks. Those are upstream capabilities that our run did not verify. The architecture documentation also describes trading some consistency for performance through more aggressive metadata caching. Test the configuration your applications will use, including concurrent access.

    What to check before deployment

    JuiceFS documents FUSE access, a Hadoop Java SDK, a Kubernetes CSI driver and an S3 gateway. Each is a deployment path beyond the npm installation our sandbox completed. Choose the required interface, then validate it with your intended metadata engine and object store.

    The v1.4.1 release notes document a minimum-client-version check for tiered storage intended to prevent metadata corruption. Include client compatibility in upgrade testing. The README also says anonymous usage reporting is enabled by default and documents --no-usage-report for mounts; review that setting against your deployment policy.

    Which alternatives fit a different requirement?

    s3fs preserves the native object format for files. Consider s3fs-fuse when access through ordinary S3 tools matters. Its README lists no atomic renames and no coordination between clients mounting the same bucket. Those limitations make it unsuitable as a replacement when those shared-filesystem behaviors are required.

    Alluxio Open Source provides caching and acceleration for structured data analytics. Consider Alluxio Open Source when the problem is accelerating analytics access to underlying storage. It can serve as a complementary layer rather than replace the storage system. Its README assigns the described FUSE-based POSIX integration for AI workloads to Enterprise; that passage does not establish the capability for Open Source.

    How to interpret the ratings

    The scores are editorial assessments, not measured performance. Setup ease uses 1 for substantial unresolved prerequisites and 5 for a directly validated setup. Documentation uses 1 for missing essential guidance and 5 for coverage of architecture, deployment and operational caveats. Community uses 1 for demonstrated limited support and 5 for demonstrated sustained participation and support. Maturity uses 1 for foundational instability and 5 for a stable design supported by operational validation. Intermediate scores reflect partial evidence; a missing evidence base remains unassessed.

    Setup ease is 2 because the client and storage services require evaluation together, while our run checked only npm installation. Documentation is 5 for the supplied architecture, interface and operational explanations. Community remains unassessed because the extracts do not establish participation or support outcomes. Maturity is 4 for the upstream stable-format commitment and documented maintenance fixes, with recovery and upgrade behavior untested by us.

    Alternatives

    ProjectWhat it isPick it when
    s3fs-fuseA FUSE mount for S3 buckets that preserves native file objects.Consider it when ordinary S3 tools must access the same files and your workload can accept its documented lack of atomic renames and coordination between mounting clients.
    Alluxio Open SourceA distributed caching platform for structured analytics.Consider it for caching and accelerating analytics access to underlying storage. Treat it as a possible complementary layer, and check edition boundaries before assuming Enterprise POSIX capabilities apply.

    What people are saying

    1. [github-trending] juicedata/juicefs

    Sources

    1. JuiceFS repository and README
    2. JuiceFS v1.4.1 release
    3. JuiceFS architecture documentation
    4. JuiceFS quick start guide
    5. JuiceFS issue tracker

    More data reviews