Error: Data error: error transforming block

[tve]

I'm getting an error when starting ZeroFS:

2026-01-07T08:28:42.008479Z  INFO zerofs::cli::server: Loading or initializing encryption key from object store
Waiting for zerofs
2026-01-07T08:28:45.768416Z  INFO zerofs::cli::server: Cache allocation - Disk: 1.00GB, Memory: 1.00GB
2026-01-07T08:28:45.768429Z  INFO zerofs::cli::server: SlateDB in-memory block cache: 1000 MB
2026-01-07T08:28:45.769874Z  INFO zerofs::cli::server: Opening database in read-write mode (compactor disabled)
2026-01-07T08:28:45.769905Z  INFO slatedb::db::builder: opening SlateDB database [path=zerofs-nocompact, settings={"flush_interval":"30s","wal_enabled":false,"manifest_poll_interval":"1s","manifest_update_timeout":"300s","min_filter_keys":1000,"filter_bits_per_key":10,"l0_sst_size_bytes":134217728,"l0_max_ssts":16,"max_unflushed_bytes":1000000000,"compactor_options":null,"compression_codec":null,"object_store_cache_options":{"root_folder":"/var/cache/zerofs/bucket_a032870c","max_cache_size_bytes":1000000000,"part_size_bytes":4194304,"cache_puts":true,"preload_disk_cache_on_startup":null,"scan_interval":"3600s"},"garbage_collector_options":{"manifest_options":{"interval":"60s","min_age":"60s"},"wal_options":{"interval":"60s","min_age":"60s"},"compacted_options":{"interval":"60s","min_age":"60s"},"compactions_options":{"interval":"60s","min_age":"60s"}},"default_ttl":null}]
Error: Data error: error transforming block
Zerofs failed code=1

This is probably user error? It would be nice for the error to provide more details or a hint about where to look?

[tve]

Hmm, looks like an incompatibility between 0.22.9 and 0.23.3: filesystem created using the former and trying to open it using the latter fails.

[Barre]

Releases are not currently compatible with each other while waiting for 1.0. Hopefully, the storage format is probably almost stable now.

[tve]

I understand your point, it would be helpful to note in the release notes when a new version is incompatible with the prior one...

Depending on how much work a migration or backwards-compatible patch is it may be worth your time to implement it 'cause it allows users to upgrade easily and thereby test the new versions. I'm kind'a stuck on 0.22 now unless I hit a bug or a new version has a significant new feature.

[sadjokerrr]

Same to me

[tidux]

I got bit by this trying to mount a v1.0-created bucket with v0.19 on another machine (mistakenly doing cargo install zerofs instead of using the installer) and then trying to remount it with v1.0. Is all my data just hosed?