Fly.io ditches its homemade JuiceFS filesystem for SBD: ext4 on a bucket as a block device

Fly.io Blog · rss · 2026-10-22

Fly.io rewrote Sprites' storage layer after their modified JuiceFS stack—three separately-durable ledgers of chunks, metadata, and checkpoints—proved fragile. A dogfooding harness ran 5,000 write/checkpoint/sleep/wake/restore cycles against 400 Sprites and found some permanently unable to checkpoint. The replacement, Sprites Block Device (SBD), presents the bucket as an NBD block device so ext4 runs directly on object storage: metadata lives beside its blocks, checkpoints become versioned volume snapshots, and restore costs about as much as a restart. Tests show orders-of-magnitude reliability gains; pre-10/6 Sprites can migrate.

Original post →

More from coding & agent

coding & agent channel →