Building mountOSMaker

Commented on mountOS · Nov 2, 2026
Thanks for your interest! These are indeed two of the key challenges in designing filesystems over object storage. Rename: mountOS doesn’t use S3 copy+delete. We have a separate metadata service (dataserv), with database transactions ensuring atomic rename. File contents are stored as immutable objects, so rename only updates metadata without moving or copying S3 objects. Time travel: We use versioned metadata rather than periodic full snapshots or event-log replay. Historical versions can be accessed by timestamp, and independent forks can be created from previous points in time. One minute represents the time-selection granularity, not a full snapshot taken every minute. The fundamental design separates POSIX filesystem semantics from the underlying object storage operations

Commented on mountOS · Oct 26, 2026
mountOS lets you mount S3 and object storage as a native POSIX filesystem on Mac, Windows, Linux, or Kubernetes, with built‑in forks, time‑travel and version history. It runs on your own infrastructure and stays free up to 10 TiB. I'd love to hear what you think and any ideas for improvement 😊