There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

What file systems are you using on your devices and why?

I want to learn more about file systems from the practical point of view so I know what to expect, how to approach them and what experience positive or negative you had / have.

I found this wikipedia’s comparison but I want your hands-on views.

For now my mental list is

  • NTFS - for some reason TVs on USB love these and also Windows + Linux can read and write this
  • Ext4 - solid fs with journaling but Linux specific
  • Btrfs - some modern fs with snapshot capability, Linux specific
  • xfs - servers really like these as they are performant, Linux specific
  • FAT32 - limited but recognizable everywhere
  • exFAT - like FAT32 but less recognizable and less limited
mayidar ,

I use Btrfs for my root partition to be able to rollback if something goes wrong after update. XFS: in all other cases, since I hate the lost+found directory on ext4. Although I don’t think there’s any significant difference between ext4 and xfs in performance and reliability.

cyborganism ,

I’m curious now about BTRFS.

How do you roll back in case of problems?

mayidar ,

discovery.endeavouros.com/…/02/

Basically, I just followed this tutorial for my EndeavourOS installations. It’s as easy as choosing an older entry in GRUB. Fedora offers something similar by default, and I think Tumbleweed does too.

Moreover I’m now playing with Arkane Linux (arkanelinux.org), immutable flavour of Arch, it features another magic with btrfs and rollbacks without snapshots and GRUB

Zikeji ,
@Zikeji@programming.dev avatar

Bookmarking Arkane. I’m a huge fan of Fedora Atomic but miss AUR.

cyborganism ,

Oh ok cool! I’m going to check it out.

I’m taking a lot of notes for my next install. Trying to build something solid with Kubuntu.

Kualk ,

Take snapshot. If problem occurs, manually change boot label to use snapshot label.

savvywolf ,
@savvywolf@pawb.social avatar

I’ve been basically using btrfs on a lot of my disks because of the features it has.

Before I switched to a borg based system, my backups partition used btrfs for compression.

My main OS disk is btrfs so I can use timeshift snapshots, which are really worth checking out if you tinker with your system a lot.

I have two more btrfs partitions software raid0’d together for my steam library, nix store and other big but loosable things.

And my main home folder uses btrfs because I think the checksumming thing it does is more reliable for error detection, and cow is more fault tollerant on power failure?

… And I now fell like I’m one of those people with an over engineered storage solution. I just never get rid of old ssds or hard disks!

seaQueue , (edited )
@seaQueue@lemmy.world avatar

Btrfs, ZFS and ext4. My servers use ZFS, my client machines mostly use btrfs and I have a sprinkling of ext4 partitions for specific workloads. I’m all in on CoW filesystems for snapshots, send receive, transparent compression and reflinks. I like btrfs on client machines and SBCs because it’s easily available (baked into the kernel) and doesn’t require maintaining dkms or holding kernel versions until ZFS supports them and because snapshot handling and other filesystem admin tasks are simple and straightforward. I run ZFS wherever data integrity is important, eg: storage servers and backup targets, but largely prefer working with btrfs.

soundconjurer ,
@soundconjurer@mstdn.social avatar

@Psyhackological
Work stations all run Ext4.
Main server: Ext4 on main partition, ZFS RAIDZ2 on the data.
Secondary server: BTRFS on main, BTRFS RAID1 on data.

If BTRFS could natively encrypt and had stable RAID6, I'd be using it probably on everything.

eager_eagle ,
@eager_eagle@lemmy.world avatar

F2FS, because solid state and speed

sgibson5150 ,

Random thoughts, no particular order

I think btrfs was the default the last time I installed Bazzite, but I don’t really know anything about it so I switched it to ext4. I understand the snapshot ability is nice with rolling release distros, though.

It’d been ages since I’d used FAT32 for anything until I made a Debian live USB when I was setting up my pi-hole on an old Core2Duo recently. It would only boot on FAT32 for reasons I probably once knew. 😆

NTFS was an improvement over the FATs what with the journaling, security, file streams, etc. I use it wherever I still use Windows (work).

Most of my general purpose USB flash drives use exFAT. I like not having to worry about eject/unmount.

Jesus_666 ,

NTFS feels rock solid if you use only Windows and extremely janky if you dual-boot. Linux currently can’t really fix NTFS volumes and thus won’t mount them if they’re inconsistent.

As it happens, they’re inconsistent all the time. I’ve had an NTFS volume become dirty after booting into Windows and then shutting down. Not a problem for Windows but Linux wouldn’t touch the volume until I’d booted into Windows at least once.

I finally decided to use a storage upgrade to move most drives to Btrfs save for the Windows system volume and a shared data partition that’s now on ExFAT because it’s good enough for it.

rjek ,

ext4 because I value my data and don’t want to lose it. I used to mess about with ZFS for mass storage but it’s a university course to learn how to use and have decent performance.

I used to use XFS, but ext4 caught up.

And I used to use XFS… on something other than Linux.

gerdesj ,

xfs has reflinks. That means you can copy huge wodges of data nearly for free on one filesystem. For backup systems this is a killer feature. Veeam rolling up incremental backups into the last full happens in seconds because pointers to blocks are juggled around rather than the data blocks themselves.

xfs has been around for a very, very long time. I use it for larger filesystems eg Nextcloud, Zoneminder and the like (and Veeam backup repos that are not object storage). I use ext4 by default.

pfSense boxes - zfs because the alternative is ufs.

RPi - OverlayFS (with ext4 and tmpfs) gets you a generally read only filesystem with changes held in RAM. Ideal for kiosks, appliances and keeping memory sticks alive.

Windows - NTFS, it works well and has streams and there aren’t many other options (ReFS is a bit new but it does have reflinks)

Diplomjodler3 ,

Ext4 cause that’s the default and I’m lazy.

bionicjoey ,

Based

Ooops ,
@Ooops@feddit.org avatar

BTRFS raid on LUKS-encrypted devices (no LVM, all unlocked with one password via SystemD encrypt hooks).

mat ,
@mat@linux.community avatar

Honestly I saw btrfs in the arch install guide and read about it because I thought the name sounded funny. I used it until I distro hopped to NixOS couldn’t figure out how to install it with btrfs, so I’m back on ext4.

Maybe I’ll give it another try next hop, which is likely soon since Qt theming seems impossible on Nix. :/

ChickenPasaran ,
@ChickenPasaran@piefed.social avatar

Ext4 with LVM.

I like BTRFS and it's features but sadly Debian doesn't have a preset for it in it's installer so the only way to use it is to manually partition and I absolutely suck at that.

Magister ,
@Magister@lemmy.world avatar

Btrfs in a luks container so it’s encrypted.

fossphi ,

Btrfs, for the compression and CoW. I’ve been using it since a couple years. It seems stable for my use. I need to fully wrap my head around how snapshots work, though.

henfredemars ,

You mentioned CoW. I’m really taking advantage of this because I have multiple Wine prefixes that have lots of duplicate data. I want to give every application it’s own prefix, and my underlying file system allows me to duplicate the blocks so the prefixes are basically free where before it’s several hundred megabytes just to make a new prefix.

avidamoeba , (edited )
@avidamoeba@lemmy.ca avatar

Ext4 and ZFS.

  • Ext4 for system disks because it’s default in OS installers and it works well. I typically use it on top of LVMRAID (LVM-managed mdraid) for redundancy and expansion flexibility.
  • ZFS for storage because it’s got data integrity verification, trivial setup, flexible redundancy topologies, free snapshots, blazing fast replication, easy expansion, incredible flexibility in separating data and performance tuning within the same filesystem. I’d be looking into setting up ZFS on root for my next machine. Among other things that would enable trivial and blazing fast backup of the system while it’s running - as simple as syncoid -r rpool backup-server:machine4-rpool.
xilliah ,

Thank you little amoeba 🦠

avidamoeba ,
@avidamoeba@lemmy.ca avatar

biased random walk dance

thingsiplay ,

Ext4 for everything when possible, because its reliable and proven. I’m looking towards Btrfs for my next system drive, as it is mature now and has good features. But I would use Ext4 for everything else still. For interoperability that doesn’t understand Ext4 it would be NTFS when supported, otherwise fallback to FAT32.

That’s the entirety of my knowledge and what I use when I have to format it myself. :D

henfredemars ,

I respect your reliable and proven comment. I really love the features of BTRFS and that’s why I use it, but I also really care about my data. I have secondary installations that use EXT4 and work very well.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •