You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow explicit configuration of storage backend, prevent accidental switch to jjfs #3332
Currently there seems to be no config option to set the storage backend of a store. The type determination is left up to detecting identifying artefacts from the store, such as the presence of the .git or .jj dirs. This is somewhat unexpected behavior and can shift the storage routines used in unintended ways. A better way would be an explicit mounts.storage option that defaults to gitfs unless overriden in init with the --storage flag or manually configured. Default config without specifying --storage should still record gitfs as the backend to make it explicit that's how its being used.
Personally, I have the repo initialized with jj to better view history in a way I'm familiar with and I didn't intend to switch to gopass's jjfs mode. Everything was fine until I tried to run a fsck which fails due to the immaturity of the jjfs backend.
Original content that assumed jjfs was considered usable:
changed the title [-]fsck fails on jjfs, no subcommand gc[/-][+]Allow explicit configuration of storage backend, prevent accidental switch to jjfs[/+]on Feb 2, 2026
Interesting use case. Sorry for the confusion. I agree, we must never accidentally switch the storage backend. Might not be an easy fix, but we should fix this.
Activity
[-]fsck fails on jjfs, no subcommand gc[/-][+]Allow explicit configuration of storage backend, prevent accidental switch to jjfs[/+]dominikschulz commentedon Feb 7, 2026
Interesting use case. Sorry for the confusion. I agree, we must never accidentally switch the storage backend. Might not be an easy fix, but we should fix this.
fix(backend): add storage.backend config key to lock backend selection (
Bump version to 2.0.0