Not quite. Bcachefs can be used on any drive, but it shines the best when you have a fast + slow drive in your PC (eg NVMe + HDD), so the faster drive can be used as a cache drive to store frequently accessed data.
Not OP, but yes, that's pretty much how it works. (ZFS scrubs do not defrgment data however).
Fragmentation isn't really a problem for several reasons.
-
Some (most?) COW filesystems have mechanisms to mitigate fragmentation. ZFS, for instance, uses a special allocation strategy to minimize fragmentation and can reallocate data during certain operations like resilvering or rebalancing.
-
ZFS doesn't even have a traditional defrag command. Because of its design and the way it handles file storage, a typical defrag process is not applicable or even necessary in the same way it is with other traditional filesystems
-
Btrfs too handles chunk allocation effeciently and generally doesn't require defragmentation, and although it does have a defrag command, it's almost never used by anyone, unless you have a special reason to (eg: maybe you have a program that is reading raw sectors of a file, and needs the data to be contiguous).
-
Fragmentation is only really an issue for spinning disks, however, that is no longer a concern for most spinning disk users because:
- Most home users who still have spinning disks use it for archival/long term storage/media that rarely changes (eg: photos, movies, other infrequently accessed data), so fragmentation rarely occurs here and even if it does, it's not a concern.
- Power users typically have a DAS or NAS setup where spinning disks are in a RAID config with striping, so the spread of data across multiple sectors actually has an advantage for averaging out read times (so no file is completely stuck in the slow regions of a disk), but also, any performance loss is also generally negated because a single file can typically be read from two or more drives simultaneously, depending on the redundancy config.
-
Enterprise users also almost always use a RAID (or similar) setup, so the same as above applies. They also use filesystems like ZFS which employs heavy caching mechanisms, typically backed by SSDs/NVMes, so again, fragmentation isn't really an issue.
That link is for kernel 5.14, so I'd say those results are pretty much invalid for most users (unless you're actually on it, or the 5.15 LTS kernel). There have been a ton of improvements in every filesystem since then, with pretty much every single kernel release.
A more relevant test would be this one - although it talks about bcachefs, other filesystems are also included in it. As you can see, F2FS is no longer the fastest - bcachefs and XFS beat it in several tests, and even btrfs beats it in some tests. F2FS only wins in the Dbench and CockroachDB benchmarks.
Or they could just get you to execute the command without your knowledge (eg: all the people who just blindly copy-paste commands, or pipe scripts from the net into sudo). Or it could be a compromised github account/repo (supply-chain attack). Or even the ol' techsupport scam where they get gullible users to install stuff...
No, it's an actual attack. But we don't know for sure if it's being exploited actively in the wild. This vulnerability has existed ever since PCs adopted UEFI (~2006).
Ah, AR, that infamous state where a mother killed her three babbys.
Interesting, I didn't know you could create clusters with it! That looks promising then. I was planning to install Proxmox for my homelab but didn't like that it was a whole distro, which shipped with an ancient kernel...
To be fair, even Apple Music and Tidal are trash on Android. And Apple is a $3 trillion company with over 150k employees.
At least it's a bit more full-featured than Fedora 39, where they just updated to Gnome 45 and called it a day, and KDE users didn't even get anything new at all.
I find wet wipes handy for that. Just chuck a packet in your pocket, and give yourself a quick wipedown when you're in the stall.