Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bcachefs storage driver #1744

Open
cveilleux opened this issue Oct 31, 2023 · 2 comments
Open

bcachefs storage driver #1744

cveilleux opened this issue Oct 31, 2023 · 2 comments

Comments

@cveilleux
Copy link

With bcachefs officially mainlined into linux 6.7, has anybody looked into this new filesystem?

It is similar in features to BTRFS and ZFS, so potentially a libcontainers storage driver could be written for bcachefs.

What would the Container Storage Library need in order to consider support for bcachefs?

Would you need mainstream support of bcachefs in popular distributions first?

Packaging of the bcachefs-tools available in supported distros?

Is this something the team could consider developing?

If not, would an outside pull request be considered/accepted or are new storage drivers not welcomed?

Just wanted to get the discussion started around this new filesystem that is getting some attention now.

@giuseppe
Copy link
Member

giuseppe commented Nov 8, 2023

From what I've seen, a specialized driver for a new filesystem doesn't really add much advantage as we've already experienced with BTRFS.

The overlay storage backend we've got now works with many different setups and offers features that will be difficult (if not impossible) to replicate in a different backend for bcachefs, like for example its integration with partial pulls, composefs that are we currently working on right now, as well as additional image stores.

I don't think anyone in the core team will consider such effor, but if someone in the community is interested to play with it and find it useful, it can be considered for inclusion as we did for BTRFS.

@rhatdan
Copy link
Member

rhatdan commented Nov 8, 2023

Sure, but core developers will not support it, and will tell users to move to Overlay if they find issues, or get someone in the community to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants