381
Linus Torvalds Begins Expressing Regrets Merging Bcachefs
(www.phoronix.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Aug 2024
381 points (98.5% liked)
Linux
47366 readers
2399 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You might as well say use fat32 it just works.
FAT32 does not just work for my Linux OS.
To people who just want to browse the web, use Office applications and a few other things, ext4 just works and FAT32 really just doesn't.
I get the point you're trying to make, FAT32 also has a small file size and is missing some features, ext4 is like that to for instance Bcachefs.
But FAT32 (and exFAT and a few others) have a completely different use cases; I couldn't use FAT32 for Linux and expect it to work, I also couldn't use ext4 for my USB stick and expect it to just work as a USB stick.
Why not? It can be adapted to a smaller drive size fairly easily during filesystem creation.
True, but for me and many others USBs are also just massively portable. Since macOS, Windows and many others (phones, consoles, smart TVs...) don't speak ext4 but do all speak FAT32 and exFAT, that makes exFAT the way to go on USB drives.
ExFAT and FAT32 are not the same.
I know they're not, I never said they were
Not really. It has a quite small file size limit afaik.
Like there's not a bunch of stuff EXT 4 can't do that BTRFS and whatever this other acronym soup can do.
It's the entire point of my post. E x t 4 does work but it doesn't do the stuff these other file systems do so they are an advantageous choice for some things.
One point: ext4 has a maximum file size of 16TiB. To a regular user that is stupidly huge and of no concern but it's exactly the type of thing you overlook if you "just use ext4" on anything and everything then end up with your database broken at work because of said bad advice.
Use the filesystem that makes the most sense for your use case. Consider it every single time you format a disk. Don't become complacent! Also fuck around with the new shit from time to time! I decided to format my Linux desktop partitions with btrfs over a decade ago and as a result I'm an excellent user of that filesystem but you know what? I'm thinking I'll try bcachefs soon and fiddle around more with my zfs partition on my HTPC.
BTW: If you're thinking about trying out btrfs I would encourage you to learn about it's non-trivial maintenance tasks. btrfs needs you to fuck with it from time to time or you'll run out of disk space "for no reason". You can schedule cron jobs to take care of everything (as I have done) but you still need to learn how it all works. It's not a "set it and forget it" FS like ext4.
For a few years I used a distro that had btrfs as default, including scheduled automatic maintenance. Never had to bother about manual balancing or fiddeling with the FS.
I have 52 terabytes of BTRFS, I've been on it for about 5 years.
I think we're just talking about different priorities. For me stability is the most important in production. For you features seem to matter more. For me it's enough if a file system can store, write, read and not lose files. I guess it depends on what the use case and the budget are.
Yeah, some people have needs that you don't have. That's why I commented on your blanket statement of just use EXT4.
I have BTRFS in production all over the place. Snapshots are extremely useful for what I do.
ext4 aims to not lose data under the assumption that the single underlying drive is reliable. btrfs/bcachefs/ZFS assume that one/many of the perhaps dozens of underlying drives could fail entirely or start returning garbage at any time, and try to ensure that the bad drive can be kicked out and replaced without losing any data or interrupting the system. They're both aiming for stability, but stability requirements are much different at scale than a "dumb" filesystem can offer, because once you have enough drives one of them WILL fail and ext4 cannot save you in that situation.
Complaining that datacenter-grade filesystems are unreliable when using them in your home computer is like removing all but one of the engines from a 747 and then complaining that it's prone to crashing. Of course it is, because it was designed under the assumption that there would be redundancy.
Which is exactly why you'd want to run a CoW filesystem with redundancy.
Well, yes use-case is key. But interestingly ext4 will never detect bitrot/errors/corruption. BTRFS will detect corrupted files because its targeted users wants to know. It makes it difficult to say what's the more reliable FS because first we'd have to define "reliable" and the perception of it and who/what do we blame when the FS tells us there's a corrupted file detected?. Do we shoot the messenger?
It also does not support unix file permissions - so for most installs it does indeed not work.
No. You can layer ext4 with LVM and LUKS to get a lot of features (but not all) that you get with BTRFS or ZFS. FAT is not suitable for anything other than legacy stuff.
My point is there are features that you don't get in EXT that are completely reasonable to use and workflows.
When someone says just use EXT4, they're just missing the fact that people may want or need those other features.
Your response to FAT is exactly my point.