r/filesystems • • Jun 21 '26

I made a file search that manually reads bytes from disc for ext4, btrfs, and APFS bypassing kernel

19 Upvotes

https://github.com/dmtrKovalenko/ffs

Just wanted to share a project I've been doing for fun recently that does what I told in the title. The fun part that it is becoming progressively faster comparing to the standard file search tools the more files you have


r/filesystems • • Dec 22 '25

OpenZFS 2.4 Released With Faster Encryption Performance, Many Other Improvements

Thumbnail
phoronix.com
19 Upvotes

r/filesystems • • Sep 02 '25

Linus Torvalds Marks Bcachefs As Now "Externally Maintained"

Thumbnail phoronix.com
19 Upvotes

r/filesystems • • Oct 15 '20

XFS File-System With Linux 5.10 Punts Year 2038 Problem To The Year 2486

Thumbnail
phoronix.com
19 Upvotes

r/filesystems • • Sep 03 '25

Linux's exFAT File-System Driver Optimization Leads To 16.5x Speedup For Loading Time

Thumbnail phoronix.com
18 Upvotes

r/filesystems • • Sep 20 '21

That Didn't Take Long: KSMBD In-Kernel File Server Already Needs Important Security Fix

Thumbnail
phoronix.com
18 Upvotes

r/filesystems • • 9d ago

Is there a study on NVMe SSD wear (write amplification) comparing ext4, Btrfs, and ZFS with LUKS2?

17 Upvotes

Hi everyone,

I’m trying to make an informed decision for a single-disk NVMe setup on my PC, and I’m specifically concerned about SSD endurance (TBW/wear-out) rather than pure performance.

I’ve been digging into how different filesystems handle writes, and I keep seeing anecdotal reports that CoW filesystems like Btrfs and ZFS can generate significantly more write amplification than ext4. For example, I’ve seen claims that ZFS can produce “extremely high write load” on consumer NVMe drives due to its transaction group and ZIL behavior.

However, I haven’t been able to find a controlled, empirical study that isolates SSD wear across these three filesystems under the same conditions.

My planned setup for all three cases would be:

  • LUKS2 full-disk encryption (which I understand should not significantly amplify writes on its own).

  • For Btrfs: nodatacow disabled (i.e., CoW active), compress=zstd, space_cache=v2, and dedup explicitly turned off.

  • For ZFS: ARC cache size reduced to a reasonable limit for a desktop, and no dedup.

  • For ext4: standard data=ordered journaling mode.

My questions for the community:

  1. Does anyone know of a published paper, benchmark, or detailed blog post that actually measures SMART data (like Data Units Written or Percentage Used) over time for these three filesystems on the same NVMe drive?

  2. If no formal study exists, what are your real-world experiences with SSD wear indicators after months/years of use with these setups?

  3. Are the optimizations I listed above (Btrfs dedup off, ZFS ARC limit) actually effective at bringing write amplification closer to ext4 levels, or is the CoW overhead still significant?

I’m happy to be pointed toward academic papers, Phoronix-style benchmarks, or even well-documented forum threads. I’d just like to avoid making a choice based purely on “vibes” if there’s hard data out there.

Thanks in advance


r/filesystems • • Feb 20 '26

exFAT Achieves Better Sequential Read Performance With Linux 7.0

Thumbnail
phoronix.com
17 Upvotes

r/filesystems • • Oct 28 '20

Bcachefs Linux File-System Sent Out For Review With Exciting Feature Progress

Thumbnail
phoronix.com
17 Upvotes

r/filesystems • • Apr 06 '26

Just wanted to highlight a web site which explains FAT32 and others filesystems pretty well

Thumbnail
internals-for-interns.com
16 Upvotes

r/filesystems • • Apr 26 '22

Concerns Raised Over The "New" NTFS Linux Driver That Merged Last Year (driver maintainer has ghosted)

Thumbnail
phoronix.com
16 Upvotes

r/filesystems • • Dec 31 '25

Why no extended attribute indexing in modern file systems?

15 Upvotes

I've been reading about the Be File System. The indexing and querying of extended attributes seems like a pretty cool feature, but I can't find any present day file systems that implement it and I was wondering why.

Is there some technical obstacle? Would it degrade performance? Is it just that no one has gotten around to it? Or maybe it's just not as interesting a feature as I think it is?


r/filesystems • • Dec 22 '25

FUSE 3.18 Released With FUSE-Over-IO-uring, Statx Support

Thumbnail
phoronix.com
15 Upvotes

r/filesystems • • Nov 07 '25

IncusOS Announced As Immutable Linux OS With ZFS For Running Containers

Thumbnail phoronix.com
15 Upvotes

r/filesystems • • Sep 18 '20

Red Hat Has Been Working On New NVFS File-System (FS for non-volatile memory)

Thumbnail
phoronix.com
15 Upvotes

r/filesystems • • Mar 06 '26

Linux 7.0 File-System Benchmarks With XFS Leading The Way

Thumbnail
phoronix.com
14 Upvotes

r/filesystems • • Aug 10 '25

A Minimum Complete Tutorial of Linux ext4 File System

Thumbnail metebalci.com
14 Upvotes

r/filesystems • • Nov 03 '21

Btrfs With Linux 5.16 Seeing More Performance Optimizations, NVMe ZNS

Thumbnail
phoronix.com
14 Upvotes

r/filesystems • • Mar 20 '21

Why can't exFAT partitions be resized using standard drive/volume management software?

14 Upvotes

Standard tools like GParted, Disk Management, Disk Utility, etc. can't shrink or enlarge exFAT partitions, but proprietary/freemium software like DiskGenius can. Why is this?


r/filesystems • • Dec 02 '20

OpenZFS 2.0 release unifies Linux, BSD and adds tons of new features

Thumbnail
arstechnica.com
14 Upvotes

r/filesystems • • Oct 14 '26

XMFS: Experimental File-System Being Worked On By Huawei For Modern Linux Servers

Thumbnail
phoronix.com
13 Upvotes

r/filesystems • • Nov 17 '22

Why hasn't there been a feature-complete ext4 driver for Windows yet?

13 Upvotes

There's the once-well-known ext2fsd, but it has become abandonware for ~5 years, and it causes lots of trouble on newer Windows versions. Bo Branten took a fork of it and fixed some of its bugs two years ago, but he has yet to add any missing features like journaling or ACL.

There was also Ext2IFS, which became inactive even earlier than ext2fsd, and it does not support ext4 at all (only ext2/3).

Other ext4-for-Windows programs are user-mode volume browsers, and we're talking about drivers here.

Intriguingly, there is a highly elaborate Windows implementation of btrfs out there, which has been iterating for more than six years! In addition to following recent upstream development like zstd compression and space cache v2, the driver even supports fancy things like Linux-to-Windows user mapping and metadata passthrough to WSL! Of course btrfs is not nearly as widely adopted as ext4; yet btrfs-on-Windows is in a much better state than ext4-on-Windows, thanks to maharmstone's great work.

In contrast to the myriad of FSes in the Unix/Linux world, Windows has been relying on NTFS for every device and workload since 2001 (the release of NTFS 3.1 — its latest version), despite it lags behind ext4 in many use cases. So why not more porting of FSes onto the Windows platform? Doing that will definitely make the OS more developer-friendly, as is Microsoft constantly bragging about!

Yes I know there is WSL (which got the first stable store release yesterday); but (Hyper-V-based) WSL is just too heavy for laptops — memory consumption in the GiB even for running the tiniest ELF, and it raised the idle power of my device by as much as 25%. I think native support (contrary to relying on virtualization) for Linux things is still viable, though not top priority.

What do you think? Are ext4 and other FS drivers for Windows "not worth its salt" in 2022?


r/filesystems • • Oct 14 '22

Linux 6.1 To Allow Faster File Sharing Between Host & Guests With 9P VirtIO Optimization

Thumbnail
phoronix.com
13 Upvotes

r/filesystems • • Feb 16 '22

An update on bcachefs on the LKML

Thumbnail lore.kernel.org
13 Upvotes