EXT4 for Linux. exFAT for removable drives. Never regretted.
I am not interested in fancy technologies. EXT2/3/4 has been here for a few decades.
this post was submitted on 04 May 2024
120 points (97.6% liked)
Linux
48365 readers
1474 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
No love for bcachefs?
Chill. That thing just hit the mainline.
Thank you brave pioneers. I just felt confident to switch to btrfs last year.
Uff, somehow missed your post. See mine. That's the FS I'm hoping to use next. I'm waiting for it to support swapfile, or alternatively read from official sources they won't ever support it, :). But yes, that's the one I'm looking forward to use.
load more comments
(1 replies)
I use f2fs on ssd's and ext4 on hdd's
I don't see the need for snapshots, I backup externally
SSDs* HDDs*
f2fs does one of the weirdest things with compression by default: the files are compressed but they still take up the same amount of blocks as the uncompressed files. This can get you the slight performance boost of compressed files, but doesnβt actually save you space which is an odd choice. You can enable a flag in the kernel but it has other effects as well.
load more comments
(1 replies)
Well since so many people recommend btrfs because "it have never lost any data for me". I want to suggest OP to never use btrfs ever. Because it has lost my data, at least three separate times, the most recent time a week ago. And it's not because of a power loss or anything, it just corrupted my files for absolutely no reason at all.
Stay away from btrfs at all costs.
"It's never lost data for me. Yet" is what they mean.
I totally agree, the only file system I've lost data with as a result of a file system corruption not caused by hardware errors or power problems in 35 years has been btrfs. FAT even served me better.
I always go LVM + BTRFS these days. I simply love the versatility.
EDIT: DO NOT DO THIS LMAO, JUST USE BTRFS, I AM SO STUPID
I'm curious, why do you use LVM with BTRFS and not just use BTRFS built in subvolumes?
Because I'm stupid and like to run my partitions across multiple drives. π
BTRFS for the OS partitions, ext4 for /home, tmpfs for /tmp. I rarely need to use snapshots, but I do use a rolling release. It's one of those things you don't need until you really fucking NEED it. Tumbleweed support is great - I can roll back a bad update in about as long as it takes to reboot.
This is exactly how and what Im using.
Home and other ext4 are backed up one form or another on by NAS.
load more comments
(1 replies)
I like btrfs but only cause it got transparent compression. I don't need the extra disk space and it only helps a bit but I just think it's neat
I used ext4 for yeeeeaaaarrssss but now I'm using LUKS+btrfs, stable, encrypted.
FS is for nubz, do these instead:
Read
dd if=/dev/sda of=/dev/stdout
Write
dd if=/dev/stdin of=/dev/sda