What Filesystem? - Lemmy.world

What filesystem is currently best for a single nvme drive with regard to performance read/write as well as stability/no file loss? ext4 seems very old, btrfs is used by RHEL, ZFS seems to be quite good… what do people tend to use nowadays? What is an arch users go-to filesystem?

XFS is a possibility
That's what I use.
Btrfs or xfs. Sometimes ext4.
I use ext4 for my desktop and zfs for my media server. Ext4 is faster, ZFS is more accurate and less corruptable.
I usually just use EXT4, but perhaps you should check out F2FS. It’s designed for solid state storage mediums, as while most were created with traditional spinning hard discs in mind
WHAT IS Flash-Friendly File System (F2FS)? — The Linux Kernel documentation

At the end of the day though after all of our storage tests conducted on Clear Linux, EXT4 came out to being just 2% faster than F2FS for this particular Intel Xeon Gold 5218 server paired with a Micron 9300 4TB NVMe solid-state drive source

I’ll suggest XFS.

F2FS vs. EXT4 File-System Performance With Intel's Clear Linux

ITT 5 answers by 4 people

btrfs is great for system stability because of snapshots. You can set it up to automatically make snapshots at a timed interval or every time you run pacman.

If something breaks, you can just revert to a previous snapshot. You can even do this from grub. It’s a bit hard to set up, so if you want, you could use an arch based distro which automatically sets it up like GarudaOS.

Wow, first time I’ve seen GarudaOS recommended by someone who’s not me. Awesome distro, daily driver on my gaming rig.
I use it for home and work! I quite like it though I miss latte dock still, dragging windows from the top bar was just so useful for me
There are dozens of us. Dozens!
Too bad btrfs still doesn’t support encryption natively, unlike ext4.
How much is ext4 filesystem-level encryption actually used though?
I guess not much on desktop Linux, but every Android phone uses it. Really wish every Linux desktop would start encrypting their /home partition by default, which is the standard by many other operating systems.
I’m pretty sure default Android runs almost always on F2FS.
Got any source for that? Android has traditionally always used ext4 afaik, not sure if that changed in the last few years.

Motorola Mobility has used F2FS in their Moto G/E/X and Droid phones since 2012. Google first used F2FS in their Nexus 9 in 2014.[18] However Google’s other products didn’t adopt F2FS until the Pixel 3 when F2FS was updated with inline crypto hardware support.[19]

Huawei has used F2FS since the Huawei P9 in 2016.[20][21] OnePlus has used F2FS in the OnePlus 3T.[22] ZTE has used F2FS since the ZTE Axon 10 Pro in 2019.[23]

I assume since Google is involved that more and more Android phones will use to F2FS in the future.

So only a handful of devices support F2FS
It’s still quite a lot. Samsung is the inventor of F2FS and has a market share of 33%.
Or OpenSUSE , all setup out of the box for btrfs, snapshots, grub roolback, and cleanup timers, etc.
ext4 works perfectly fine for me and most people.
I’m using btrfs for my desktop/laptop and ZFS for my NAS and router. Both seem pretty robust.

Ext4 being “old” shouldn’t put you off. It is demonstratively robust with a clear history of structure integrity. It has immense popularity and a good set of recovery tools and documentation. These are exactly what you are looking for in a filesystem.

I’m not saying EXT4 is the best for your requirements, just that age of a file system is like fine wine.

Calling Ext4 “old” is like saying that MySQL isn’t webscale
Episode 1 - Mongo DB Is Web Scale

YouTube
If you’re married stay away from ReiserFS.
Even now? I remember when it was new I tried it, must have been 20 or so years ago. Super fast for the time, but had a nack for randomly corrupting data. After the third reformat, I went back to ext2.
Hans Reiser murdered his wife.
Oh. I did not know that! I thought it was some vague reference to losing entire weekends fixing the corrupt data.
Comparison of file systems - Wikipedia

why is the a column called “murders your wife”
Wikipedia vandalism from ages ago.
It’s an old version of the article.
Ah, ReiserFS. I remember when it was the cool kid’s choice. Then with the murdering it went out of style. They were weird times.
It has been suggested by some that there is no relationship between Reiser murdering wives and ReiserFS murdering file systems, but most steer clear of both out of an abundance of caution.

Ext4 is old, but fast and very robust. You won’t loose data or corrupt the filesystem if your system looses power. It can even survive partial wipes, if you accidentally overwrite the first few megs of you drive with a messed up dd, nearly all your data will be recoverable, including filenames and directory structure.

It doesn’t have very fancy features, but it is the best tested and most robust option available.

You won’t loose data or corrupt the filesystem if your system looses power.

Some secondary storage devices ignore standards and outright lie about sectors being successfully written when they are actually scheduled to be written out of order. This causes obvious problems when power failure prevents the true writes from completing.

It really depends on your priorities. Single drive is good for a home system with nothing really important on it… once you get to wanting to keep it and where recovery from backups is too much downtime, you want at least a drive mirror… nothing wrong with exr4+mdraid for that, although you don’t get the checksumming that zfs gives it will me pretty fast & if a drive fails you can run degraded on one drive until you get the new drive in.

I’ve been running zfs for 10 years and not lost a single byte of data even after doing stupid shit like tripping over the sata cables and disconnecting half the drives. It’s survived multiple drive failures (as long as the failures are on different bits of the disk, it recover get a clean copy onto a third drive, but it’s a brown trousers moment when stuff like that happens).

Downsides, it aint fast, and it does tend to like lots of memory. You want it on your fileserver, not your gaming system.

IMO there’s no point in a single drive zfs… it’ll warn you faster that the drive is f*cked but what do you do then?

I agree. Love ZFS for the NAS, but for a single drive desktop system, it is almost pointless and in my experience slower for desktop usage. ZFS is great for what it was designed for.
I run ext4 inside lvm (inside luks)

O use ext4 at home and im servers that are not SLES HANA DB ones.

On SLES HANA servers I use ext4 for everything but the database partitions, for which SAP and SUSE support and recommend XFS.

In a few occasions people left the non-db partitions as the default on SUSE install, btrfs, with default settings. That turned out to cause unnecessary disk and processor usage.

I would be ashamed of justifying btrfs on a server for the possibility of undoing “broken things”. Maybe in a distro hopping, system tinkering, unstable release home computer, but not in a server. You don’t play around in a server to “break things” that often. Linux (differently from Windows) servers don’t break themselves at the software level. For hardware breakages, there’s RAID, backups, and HA reduntant systems, because if it’s a hardware issue btrfs isn’t going to save you - even if you get back that corrupted file, you won’t keep running in that hardware, nor trust that “this” was the only and last file it corrupted.

Facebook was using btrfs for some usecases. Not sure what you mean by breaking things?
Most comments suggesting btrfs were justifying it for the possibility of rolling back to a previous state of files when something breaks (not a btrfs breakage, but mishaps on the system requiring an “undo”).
Ah, I see. While that use may be a good plan for home server, doing that for production server seems like a bandaid solution to having a test server and controlling deployed changes very carefully.
Exactly. A waste of server resources, as a productions server is not tinkerable, and shouldn’t “break”.
I still swear buy F2FS, been super reliable and very good perf
Unfortunately it’s not future proof. Max filesystem size is only 16 TB.
I like btrfs cause of transparent compression but I’m pretty sure other filesystems like ZFS have that too
Most people should use ext4. Only use something else if you want to tinker and don’t need long term data storage.
Ext4 for general pupose linux. Zfs for bsd network drives
oh I just read up on this last knight. Yes ext4 is old but it is used because it is still works quite well. btrfs, dis anyone say that as butfarts, can handle much larger partitions ext4 maxes out at a few tb while btfrs can get much larger. ZFS can handle a around a billion tb but it needs a lot more resources to to even start

ext4 maxes out at a few tb Max filesystem size is 1 EiB = 1048576 TB.

More than enough!

eh which ever value it is smaller then btfrs or zfs

ext4.

Never used arch; just slackware and then enterprise linux.

I have two drives in my machine, nvme and a sata. Nvme is my root partition and it is set to btrfs, because I love snapshots, they are just a must for me. The sata is my home partition and it is on ext4. Ext4 and is tried and true and I don’t want to risk losing my personal files.

Hi all. Apologies to hijack this thread. Figured it should be OK since it’s also on the topic of file systems.

Long story short, I need to reinstall Nobara OS and I plan to install Nobara on my smaller SSD drive with btrfs and set my /home folder to my larger nvme. I’m thinking of using ext4 for my /home and have snapshots of the main system stored on the nvme. Looking for a sanity check to see if this is OK or if I should be doing things differently. Thanks.

So you’re going to make snapshots of the ext4 filesystem onto the BTRFS one?

On the contrary, my intention is to make snapshots of the OS (btrfs) and my idea is to store the snapshots on the /home nvme drive (ext4).

I don’t know if that’s the standard practice or if I’m over complicating things. My SSD is only 240Gb (I think) while my nvme is a 1Tb drive, thus the intention to store snapshots on the nvme. Maybe the 240Gb is sufficient for say a month’s worth of snapshots plus the OS?

It’s more important to backup your /home than /. /home is where you store your crucial files.

Yes, that’s true. Then again, I’m mainly using my PC for gaming and most of what will be in /home will be game installs. I have my photos and music backups in a separate HDD.

I think at the end of the day, what I’m trying to achieve with the btrfs snapshots is to be able to roll back my OS in case a system update goes wrong, or I did something I shouldn’t have. :p