# SBD: We Have a Filesystem at Home

DevFeed: [SBD: We Have a Filesystem at Home](<https://devfeed.tech/articles/sbd-we-have-a-filesystem-at-home-95252.md>)

Original publisher: [Read original article](<https://fly.io/blog/sprites-block-device/>)

Author: Daniel Botha

Published: 2026-10-22T00:00:00Z

Content type: release

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [Ext4](<https://devfeed.tech/topics/ext4.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>), [Disk image](<https://devfeed.tech/topics/disk-image.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [mount](<https://devfeed.tech/topics/mount.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>)

Tags: [block](<https://devfeed.tech/tags/block.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [database](<https://devfeed.tech/tags/database.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [device](<https://devfeed.tech/tags/device.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [ext4](<https://devfeed.tech/tags/ext4.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [linux](<https://devfeed.tech/tags/linux.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [networking](<https://devfeed.tech/tags/networking.md>), [object](<https://devfeed.tech/tags/object.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [servers](<https://devfeed.tech/tags/servers.md>), [storage](<https://devfeed.tech/tags/storage.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>)

## AI overview

Sprites replaces its heavily modified JuiceFS setup with the Sprites Block Device (SBD): a daemon presents bucket-backed storage to Linux as an NBD block device, which Sprite formats as ext4. The prior design stored a 100 GB disk image and relied on separate JuiceFS metadata and checkpoint databases; writeback could leave metadata pointing to an object that was never uploaded, and cloned checkpoints could share that missing chunk. SBD keeps volume metadata with the blocks in the bucket, caches locally, uploads dirty blocks in the background, and flushes when durability must be guaranteed. Checkpoints record block snapshots and volume versions in SBD's catalog; restore rewinds the volume in place. SBD verifies blocks read from storage and restarts the Sprite if its daemon dies, favoring a clean restart over continued use of an untrusted disk. The post reports that stress testing and design partner feedback found SBD orders of magnitude more reliable, and says it will replace the old filesystem.

## Source excerpt

I have unkind things to say about people who make their own pasta. Here, I'll only use them as an example of how not to think when you're building infrastructure. It's unfairly easy to believe that the harder you work on something, the better it gets. But infra is about making the $1 bag of spaghetti: a simple thing that works well (and doesn't require you to spend a week scraping flour out of the corners of your kitchen). When work on Sprites started, it was a new kind of infra for a new kind of product. So when we couldn't find the right filesystem in the pasta section, we made our own. It was clever, and that's exactly why we didn't like it. This post introduces its replacement, the Sprites Block Device (SBD). It's the bag of spaghetti you grab off the shelf, and the only difference you'll notice is better reliability. It was always object storage Our stance on one core aspect of Sprites' storage hasn't changed from v1: the root of a Sprite's disk is object storage, not the NVMe in whatever server the Sprite happens to be running on. That's what lets a Sprite sleep, wake on a different server, and still find its files where it left them. The durable state of a Sprite is, more or less, a location in a bucket. We wrote about why, at length, with feeling. The thing about object stores is they can't change part of an object. To change one byte, you have to replace the whole thing. That's a bad cultural fit for Linux programs which rewrite a few bytes in the middle of a file all the time. Something has to handle that translation. At launch, that something was a heavily modded version of JuiceFS. In stock form, JuiceFS splits storage into the data (as chunks in the bucket) and the metadata (a map of which chunks make up which files) in a database. That's not how we used it, though. Our hot rodded version ran a rewritten SQLite metadata backend, kept durable with Litestream. It stored exactly one file: a 100 GB disk image, mounted on a loop device with ext4 inside. Linu