#Bcachefs was about to hit #linux-next (a pre-requisite for mainline inclusion[1]), but missing Signed-off-by lines seems to come in between:
https://lore.kernel.org/all/20230911125359.5a61d30a@canb.auug.org.au/ #kernel #LinuxKernel
[1] https://lore.kernel.org/all/CAHk-=wjUX287gJCKDXUY02Wpot1n0VkjQk-PmDOmrsrEfwPfPg@mail.gmail.com/
#bcachefs #linux #kernel #linuxkernel
@dekkzz76 I'm interested, #bcachefs' first-class support of caching devices and encryption are particularly interesting.
The fact it adds that *without* adding #ZFS' flaws of mostly requiring devices all the same size and not coping well with downgrading (enterprise assumptions™) is also part of what interests me (these are essential features #btrfs provides).
I'm probably going to wait for #SQLite and other #databases to have time to implement what support they need for it.
#bcachefs #zfs #btrfs #sqlite #databases
#bcachefs won't make it into #Linux #kernel 6.6, but is not far off. For details see Linus replies starting here:
https://lore.kernel.org/all/CAHk-=wjUX287gJCKDXUY02Wpot1n0VkjQk-PmDOmrsrEfwPfPg@mail.gmail.com/t/#u
"""I suspect any further changes are better done in-tree. The out-of-tree thing has been done.
[…] issues that I have with this, and Christoph did mention a big one: it's not been in linux-next.
So these kinds of "I'll just ignore _all_ basic rules" kinds of issues do annoy me.
[…] if you actually want this
upstream, you need to work with upstream […]"""
Dear #Linux lazyweb,
In my research preparing for my install of my new laptop, I ran across #BCacheFS and it sounds intriguing.
Does anyone have any experience to share about this #filesystem?
Um, actually I was just reading a thread on #LKML where Linus is being Linus (brutally honest, these days it is illegal for anyone but Linus to be) and #bcachefs doesn't look ready for me to try. So my excuses for getting a #FrameworkLaptop are one fewer.
#lkml #bcachefs #FrameworkLaptop
"The thing that actually bothers me most about this all is the personal arguments I saw. That I don't know what to do about. I don't actually want to merge this over the objections of Christian, now that we have a responsible vfs maintainer."
Linus Torvalds Reviews The Bcachefs File-System Code - Phoronix
https://www.phoronix.com/news/Linux-Torvalds-Bcachefs-Review
Linus looked into the #bcachefs submission:
https://lore.kernel.org/all/CAHk-%3DwhaFz0uyBB79qcEh-7q%3DwUOAbGHaMPofJfxGqguiKzFyQ@mail.gmail.com/ #Linux #kernel
` I'm still not actually convinced the locks *work* correctly, but I'm not seeing huge red flags. […]
I did *not* look at any of the internal bcachefs code itself […]
That said, I do think that the prerequisites should go in first and independently, and through maintainers. […]
The thing that actually bothers me most about this all is the personal arguments I saw. […] `
@jbzfn @LWN 16 years of active development, and #Btrfs still is not stable. I really wanted this to eclipse #ZFS when it released, but it hasn't come close.
I'm still optimistic of its development, but it's not without its warts, of which it has plenty.
https://arstechnica.com/gadgets/2021/09/examining-btrfs-linuxs-perpetually-half-finished-filesystem/
#Bcachefs however? That shit is hot. It's already stable, and supports all the Btrfs features and more. And it's not a management nightmare. Win!
Kent posted a status update about his plans to mainline #bcachefs: https://lore.kernel.org/lkml/20230712025459.dbzcjtkb4zem4pdn@moria.home.lan/
"""
- bcachefs is now marked EXPERIMENTAL […]
- Josef's stepping up to do some code review[…]
- six locks, mean and variance have been moved into fs/bcachefs/ […]
- Prereq patch series has been pruned down a bit more [and also moved] to their own branch: https://evilpiepirate.org/git/bcachefs.git/log/?h=bcachefs-prereqs […] The remaining prereq patches are pretty trivial, with the exception[…]
#bcachefs #linuxkernel #linux #kernel #filesystem
Linus Torvalds calls for calm as #bcachefs misses #Linux 6.5 :linux:
https://www.theregister.com/2023/07/10/linux_6_5_rc1_bcachefs/
One thing I found interesting in the ongoing discussion about #bcachefs inclusion into the #Linux #kernel was this statement from Eric Sandeen:
```Folks in and around filesystems and storage at Red Hat find bcachefs to be quite compelling and interesting, and we've spent some resources in the past several months to investigate, test, benchmark, and even do some bugfixing.```
https://lore.kernel.org/all/d2a06111-c8c6-cdb6-c8ac-ae7148742786@sandeen.net/
Kent revived the recent discussion[1] on #bcachefs inclusion into the #Linux #kernel two days ago:
https://lore.kernel.org/all/20230706155602.mnhsylo3pnief2of@moria.home.lan/
/me abstains from trying to give a brief summary here, as that is most likely not really helpful given the discussion
Kent Overstreet has opened a request for #bcachefs to be included in version 6.5 of the Linux kernel: https://lore.kernel.org/lkml/20230626214656.hcp4puionmtoloat@moria.home.lan/
Having to compile it from source has kept me from testing it up to now, but if this happens I'm definitely going to play around with it, as I see some caching features I'm missing in #btrfs which I would love to test.
Kent submitted #bcachefs to Linus for inclusion into the #Linux #kernel:
https://lore.kernel.org/lkml/20230626214656.hcp4puionmtoloat@moria.home.lan/
His patchset besides the #filesystem code itself also included some changes for other subsystems – unsurprisingly this wasn't much welcomed[1]. #LinuxKernel
[1] that's the diplomatic description
#bcachefs #linux #kernel #filesystem #linuxkernel