this post was submitted on 12 Sep 2023
110 points (98.2% liked)

Linux

47121 readers
1556 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
110
Bcachefs Merged Into Linux-Next (www.phoronix.com)
submitted 11 months ago by Molecular0079@lemmy.world to c/linux@lemmy.ml
17 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.world/post/4930979

Bcachefs making progress towards getting included in the kernel. My dream of having a Linux native RAID5 capable filesystem is getting closer to reality.

all 20 comments
sorted by: hot top controversial new old
[–] autotldr@lemmings.world 21 points 11 months ago (1 children)

This is the best summary I could come up with:

While Bcachefs was not merged for the Linux 6.6 cycle with one of the concerns raised by Linus Torvalds being that it hadn't been vetted via the "linux-next" staging area, that process has now begun to raise hopes of potentially seeing the new file-system driver introduced for Linux 6.7.

Overnight the Bcachefs file-system driver was added to the Linux-Next tree as that loose testing area of experimental code that hopes to get into the "next" kernel cycle.

The Bcachefs Git repository is now being pulled into Linux-Next to allow more eyes on the code and all of the automated build/test infrastructure leveraged by various individuals and vendors for testing this leading edge "-next" code.

Having Bcachefs in Linux-Next will lead to much more build testing of the code in different environments and ideally help uncover any lingering bugs before the next Linux kernel merge window opens up in about two months.

So for those interested, Bcachefs is in linux-next.

The original article contains 159 words, the summary contains 159 words. Saved 0%. I'm a bot and I'm open source!

[–] Laser@feddit.de 14 points 11 months ago

This is the best summary I could come up with:

[…]

The original article contains 159 words, the summary contains 159 words. Saved 0%.

You tried, bot. You tried.

[–] mholiv@lemmy.world 19 points 11 months ago (1 children)

So excited. The multi tiered storage feature is incredibly useful. Add in some cheap SMR as your lowest tier and you got a very cheap very big pool.

[–] Molecular0079@lemmy.world 5 points 11 months ago

That's definitely an awesome feature. As someone who's spent a small fortune running an all-SSD ZFS RaidZ array, I could have used such a feature two months ago.

[–] nulluser@programming.dev 8 points 11 months ago (4 children)

I vow from this point forward to always pronounce it, BEE-ka-chefs.

[–] Tb0n3@sh.itjust.works 5 points 11 months ago (1 children)

I swear I can only see bca chefs whenever this is posted about.

[–] taaz@biglemmowski.win 4 points 11 months ago

Ooh, it's supposed to be b cache fs

[–] LeFantome@programming.dev 4 points 11 months ago

I think it is BEE-kash-eff-ess

[–] RaivoKulli@sopuli.xyz 2 points 11 months ago

I much prefer the name of another filesystem, "butterface"

[–] dino@discuss.tchncs.de 7 points 11 months ago (2 children)

Has somebody a proper comparison with BTRFS and why somebody who is using BTRFS should look into bcachefs?

[–] Turun@feddit.de 2 points 11 months ago

Last I checked btrfs raid 5 and 6 support was still not declared as stable.

[–] RaivoKulli@sopuli.xyz 1 points 11 months ago

I'm wondering the same.

[–] JWBananas@startrek.website -4 points 11 months ago* (last edited 11 months ago) (1 children)

This would have been really nice to have a decade ago. In the age of virtualization, what's the use case?

EDIT: I'm not asking rhetorically. It really would have been nice to have 10 years ago for my use cases. What use cases do you envision for bcachefs in 2023?

[–] qprimed@lemmy.ml 11 points 11 months ago* (last edited 11 months ago) (2 children)

a striped hot ssd cache for a massive raided backend on a VM host - all done with native filesystem support sounds pretty good to me.

[–] JWBananas@startrek.website 2 points 11 months ago* (last edited 11 months ago) (1 children)

You're running local storage for a VM host? Or are you talking more like whiteboxing your own NAS?

I understand what bcachefs does. I've used bcache many years ago to do exactly what you're describing, albeit for bare metal servers. I'm asking why.

I'm just trying to understand what the use case would be in 2023 outside of a home lab, given that cost per gigabyte is basically at parity between SSDs and HDDs when you consider TCO (i.e. when you price in the extra power and cooling overhead for the HDDs, failure rates, and such).

[–] qprimed@lemmy.ml 3 points 11 months ago* (last edited 11 months ago) (1 children)

I have a pretty strong usecase for distributed Small/Medium Business bare metal VM hosts. most locations do not need NAS/SAN, and DAS will more than suffice. lower cost hardware with a near-line raided backend and SSD hotcache at FS level seems to be a pretty decent sweet spot.

obviously this is not some enterprise grade setup and YMMV, but I am pretty interested in a all-in-one FS solution. I am sure others may have more innovative setups where its even more interesting.

[–] JWBananas@startrek.website 3 points 11 months ago

Sounds like a great use case.

I'm assuming your nearline drives speak SAS? Are you doing redundant controllers on the backplane for multipathing and for fault tolerance? I'm not sure if bcachefs specifically supports it (or if that would happen at a different layer) but distros in general should support it.

TCO gets split into CAPEX and OPEX, so you come out ahead on the initial purchase even though it uses more power in the long run, which surely looks better to the business.