s3fs-fuse/s3fs-fuse

FUSE-based file system backed by Amazon S3

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 6th, 2026
Created on November 22nd, 2013
Open Issues & Pull Requests: 313 (+0)
GitHub issues: Enabled
Number of forks: 1,079
Total Stargazers: 9,982 (+0)
Total Subscribers: 172 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.7 hours
Mean response time: 43.9 days
90th percentile: 84.5 days
Tracked items: 119

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 73
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 742 days
Stale 30+ days: 72
Stale 90+ days: 69

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • need info (13)
  • dataloss (11)
  • enhancement (5)
  • help wanted (5)
  • bug (4)
  • feature request (2)
  • performance (1)
  • testing (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

s3fs is a FUSE-based file system that mounts Amazon S3 buckets on Linux, macOS, and FreeBSD, allowing S3 objects to be accessed and manipulated as if they were local files.

The tool solves the problem of integrating cloud object storage into existing file system workflows. It works by implementing a FUSE layer that translates standard file system operations into S3 API calls, preserving the native object format so that files remain accessible via other tools like the AWS CLI. The implementation supports a broad subset of POSIX semantics including reading and writing files, directories, symlinks, permissions, and extended attributes. It handles large files through multi-part uploads, performs server-side copies for renames, and offers optional encryption and MD5-based data integrity checks. Caching strategies include both in-memory metadata caching and optional local disk caching to improve performance.

Adoption suits teams that need transparent S3 access from applications or scripts expecting a file system interface, particularly where preserving object compatibility with other AWS tools is important. The tool works with Amazon S3 and other S3-compatible object stores. However, the README explicitly documents significant limitations: random writes and appends require rewriting entire objects, directory listing operations suffer from network latency, eventual consistency on non-AWS providers can yield stale reads, atomic renames are not supported, multiple clients cannot safely coordinate access to the same bucket, hard links are unavailable, and inotify only detects local changes rather than external modifications by other clients.

The project maintains steady activity with regular commits addressing bug fixes and feature improvements. Development includes responsiveness to user-reported issues and incorporation of community contributions. The codebase shows ongoing refinement of core functionality rather than major architectural shifts, with attention to compatibility across multiple operating systems and S3 implementations.