Group: Software/FSDG distributions/Filesystems
(→Filesystems for block devices: fuse-exfat: add link to package) |
(→Filesystems for block devices: Add XFS v5) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1,618: | Line 1,618: | ||
=== Filesystems for block devices === | === Filesystems for block devices === | ||
| − | This list support for filesystems for block devices (hard disks, SSD, etc). Note that the support could be read-only, partial or not builtin the bootloader provided by the distributions you use. | + | This list support for filesystems for block devices (hard disks, SSD, etc). Note that the support could be read-only, partial or not builtin the kernel or bootloader package provided by the distributions you use. For FUSE it might not have any package for the distribution you use. |
| + | |||
| + | This can for instance be used to quickly check if a given filesystem may work when installing GNU/Linux on an ARM computer with a given bootloader. | ||
| + | |||
| + | If for instance the distribution package for u-boot doesn't support the filesystem you want to use, you could consider sending a patch to add it directly in the configuration provided by u-boot itself, to make sure all the distributions you could want to use (including in the future) has the change you need. This also lowers the cost of maintaining this change. | ||
{| class="wikitable sortable" border="1" | {| class="wikitable sortable" border="1" | ||
| Line 1,634: | Line 1,638: | ||
! F2FS | ! F2FS | ||
! NILFS2 | ! NILFS2 | ||
| + | ! NTFS | ||
| + | ! XFS v5 | ||
! ZFS | ! ZFS | ||
|- | |- | ||
| − | ! colspan= | + | ! colspan=17 | Bootloaders |
|- | |- | ||
! GRUB | ! GRUB | ||
| Line 1,650: | Line 1,656: | ||
| {{yes}} <!-- F2FS --> | | {{yes}} <!-- F2FS --> | ||
| {{yes}} <!-- NILFS2 --> | | {{yes}} <!-- NILFS2 --> | ||
| + | | {{yes}} <!-- NTFS --> | ||
| + | | {{yes}} <!-- XFS v5 --> | ||
| {{yes}} <!-- ZFS --> | | {{yes}} <!-- ZFS --> | ||
|- | |- | ||
| Line 1,664: | Line 1,672: | ||
| {{no}} <!-- F2FS --> | | {{no}} <!-- F2FS --> | ||
| {{no}} <!-- NILFS2 --> | | {{no}} <!-- NILFS2 --> | ||
| + | | {{no}} <!-- NTFS --> | ||
| + | | {{no}} <!-- XFS v5 --> | ||
| {{yes}} <!-- ZFS --> | | {{yes}} <!-- ZFS --> | ||
|- | |- | ||
| − | ! colspan= | + | ! colspan=17 | Kernels |
|- | |- | ||
! Hurd | ! Hurd | ||
| Line 1,680: | Line 1,690: | ||
| ? <!-- F2FS --> | | ? <!-- F2FS --> | ||
| ? <!-- NILFS2 --> | | ? <!-- NILFS2 --> | ||
| + | | ? <!-- NTFS --> | ||
| + | | ? <!-- XFS v5 --> | ||
| ? <!-- ZFS --> | | ? <!-- ZFS --> | ||
|- | |- | ||
| Line 1,694: | Line 1,706: | ||
| {{yes}} <!-- F2FS --> | | {{yes}} <!-- F2FS --> | ||
| {{yes}} <!-- NILFS2 --> | | {{yes}} <!-- NILFS2 --> | ||
| + | | {{yes}} <!-- NTFS --> | ||
| + | | {{yes}} <!-- XFS v5 --> | ||
| {{no}} <!-- ZFS --> | | {{no}} <!-- ZFS --> | ||
|- | |- | ||
| − | ! colspan= | + | ! colspan=17 | API |
|- | |- | ||
! FUSE | ! FUSE | ||
| Line 1,710: | Line 1,724: | ||
| ? <!-- F2FS --> | | ? <!-- F2FS --> | ||
| ? <!-- NILFS2 --> | | ? <!-- NILFS2 --> | ||
| + | | {{yes}}<ref>See the {{DistroPackage|guix|ntfs-3g}} package for more details.</ref> <!-- NTFS --> | ||
| + | | ? <!-- XFS v5 --> | ||
| ? <!-- ZFS --> | | ? <!-- ZFS --> | ||
|- | |- | ||
Latest revision as of 19:42, 16 December 2025
Contents
Introduction
This article is about filesystems support and might be extended to take into account block device technologies too like LVM,RAID, etc.
Choosing a filesystem
Using the default filesystem currently proposed during the installation of your distribution is a good idea. It makes sure that the filesystem is properly integrated and that the distribution trusts it enough (with data integrity, and security[1]) to propose it by default.
For external medias like USB keys and so on, filesystems with unix permissions (like ext4) can also usable by less technical users: gnome-disks has a "Take Ownership..." function [2] that can set the right permissions to make these usable, though "Take Ownership..." could be slow if there are a huge number of files.
General comparison
| Filesystem | protection against data corruption | Linux status | Limitations |
|---|---|---|---|
| Bcachefs | Not safe according to Linus Torvalds[3]. |
|
|
| btrfs | Less safe (status from September 2025).[5] | maintained | |
| ext2 | Less safe: because there is no journal, data can be corrupted during improper shutdown for instance. | maintained | |
| ext3 | maintained | ||
| exfat | maintained |
|
|
| ext4 | Safest. | maintained | |
| NTFS | Not safe: no ability to repair the filesystem without nonfree software. | maintained | |
| ReiserFS 3 | Not safe: fsck can corrupt ReiserFS 3 images[6]. |
|
|
| XFS v4 | |||
| XFS v5 | maintained |
Creation without root
Sometimes it can be useful to create filesystems without root permissions. This is used to format files that are owned by the user (and not root) with a given filesystem. Some filesystem utilities even enable to populate the filesystem with data coming from a directory and/or store arbitrary files or directories inside the given filesystem without needing to mount the filesystem (which typically requires root permissions in one way or another).
| Filesystem | Creation without root | Utilities required | Guix image support |
|---|---|---|---|
| BTRFS | mkfs.btrfs -r ./directory [...] |
|
Yes |
| exFAT | exfatprogs 1.2.9 and exfat-utils 1.4.0 don't seem to support that | ? | No |
| ext2, ext3, ext4 | mke2fs -d ./directory [...] |
|
Yes |
| F2FS | mkfs.f2fs [...] && sload.f2fs -f ./directory [...] |
|
Yes |
| FAT12, FAT16, FAT32, VFAT | mkfs.msdos [...] && mcopy -bsp -i [...] |
|
Yes |
| HFS+ | Might be possible with hpcopy and hpmkdir |
|
No |
| JFS | jfsutils 1.1.15 don't seem to support that | ? | No |
| NILFS2 | nilfsutils 2.2.11 don't seem to support that | ? | No |
| NTFS | ntfscp can copy regular files, but it is unclear how to copy directories or other file types (/dev/ nodes, symlinks, etc) |
|
No |
| SquashFS | mksquashfs ./directory [...] |
|
No |
| XFS | Might be possible since xfsprogs 6.17.0 (patch merged in 6.17.0) |
|
No |
And for other things than filesystems:
| patition type | Creation without root | Utilities required | Guix image support |
|---|---|---|---|
| LUKS (v1 and/or v2) | May be possible with cryptsetup-reencrypt | No | |
| swap | mkswap --file [...] |
|
Yes |
Defaults
The defaults filesystems used are often a good indication of what filesystems are best supported by the distribution.
| Distribution | Defaults | Comments | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dragora 3.0 beta2 |
|
In the graphical installer, the "FILE SYSTEM SELECTION" default choice is set to ext3. Beside that there is no defaults for the partitioning. | ||||||||||||||||
| Dynebolic | ||||||||||||||||||
| Guix 1.4.0 |
|
|||||||||||||||||
| Hyperbola | ||||||||||||||||||
| LibreCMC | ||||||||||||||||||
| Parabola | ||||||||||||||||||
| ProteanOS | ||||||||||||||||||
| PureOS 10 (byzantium) |
|
|
||||||||||||||||
| Replicant 6.0 | ||||||||||||||||||
| Trisquel 10 (nabia) | ||||||||||||||||||
| Ututo S | ||||||||||||||||||
Filesystems
| Distributions | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dragora 3.0 beta2 | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 11 (aramo) | Ututo S | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| btrfs |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| erofs |
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| exfat |
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ext2 |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ext3 |
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ext4 |
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| f2fs |
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| fat |
|
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| hfs |
|
No[17] | No[18] | No[19] |
|
No[20] |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| hfs+ |
|
No[21] | No[22] | No[23] |
|
No[24] |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| jfs |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| minix |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| nilfs2 |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ntfs |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| reiser4 |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| reiserfs |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| XFS v4 |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| XFS v5 |
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Dragora 3.0 beta2 | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 11 (aramo) | Ututo S | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Distributions | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
More detailed Guix status
Guix has many areas where only some filesystems are supported. Because of that making a more detailed status about that is interesting.
| Filesystems | guix system: operating-system: file-systems | guix system image |
|---|---|---|
| btrfs | yes:rootfs[31] | Yes |
| ext2 | Yes | Yes |
| ext3 | Yes | Yes |
| ext4 | yes:rootfs[31] | Yes |
| F2FS | yes:rootfs[31] | No |
| FAT16 | Yes | Yes |
| FAT32 | Yes | Yes |
| JFS | yes:rootfs[31] | No |
| XFS | yes:rootfs[31] | No |
Block device layer
| Distributions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dragora | Dynebolics | Guix i686-linux and x86_64-linux (x86 GNU/Linux) | Guix i586-gnu (HURD) | Hyperbola | LibreCMC | Parabola | ProteanOS | PureOS 10 (byzantium) | Replicant 6.0 | Trisquel 11 (aramo) | Ututo S | |||||||
| dmraid | ||||||||||||||||||
| LDM[32] | ||||||||||||||||||
| LUKS 1 |
|
Yes | Yes | |||||||||||||||
| LUKS 2 |
|
Yes | Yes | |||||||||||||||
| md RAID (with mdadm) | ||||||||||||||||||
| LVM2 |
|
Yes | Yes | |||||||||||||||
| nonraid[33] | ||||||||||||||||||
Upstream projects
Filesystems for block devices
This list support for filesystems for block devices (hard disks, SSD, etc). Note that the support could be read-only, partial or not builtin the kernel or bootloader package provided by the distributions you use. For FUSE it might not have any package for the distribution you use.
This can for instance be used to quickly check if a given filesystem may work when installing GNU/Linux on an ARM computer with a given bootloader.
If for instance the distribution package for u-boot doesn't support the filesystem you want to use, you could consider sending a patch to add it directly in the configuration provided by u-boot itself, to make sure all the distributions you could want to use (including in the future) has the change you need. This also lowers the cost of maintaining this change.
| Project | Version | AFFS | AFS | BFS | BTRFS | EXFAT | EXT2 | EXT4 | FAT | F2FS | NILFS2 | NTFS | XFS v5 | ZFS | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bootloaders | ||||||||||||||||
| GRUB | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
| u-boot | No | No | No | Yes | Yes | Yes | Yes | Yes | No | No | No | No | Yes | |||
| Kernels | ||||||||||||||||
| Hurd | ? | ? | ? | ? | ? | Yes | ? | Yes | ? | ? | ? | ? | ? | |||
| Linux | Yes | ? | ? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | |||
| API | ||||||||||||||||
| FUSE | ? | ? | ? | ? | Yes[34] | ? | ? | ? | ? | ? | Yes[35] | ? | ? | |||
Read-only filesystems for block devices
This list support for filesystems for block devices (hard disks, SSD, etc).
| Project | Version | CRAMFS | EROFS | SquashFS |
|---|---|---|---|---|
| Bootloaders | ||||
| GRUB | No | No | Yes | |
| u-boot | Yes | Yes | Yes | |
| Kernels | ||||
| Hurd | ? | ? | ? | |
| Linux | Yes | Yes | Yes | |
| API | ||||
| FUSE | ? | ? | ? | |
References
- ↑ See the Unmaintained filesystems as a threat vector lwn.net article for more details.
- ↑ It is at least present in PureOS 10 (byzantium), Trisquel 11 (aramo) and Guix, so it is probably available everywhere. To use it, once gnome-disks is launched, you need to select the right partition, and then find a button with some gears and click on it, it will show a menu with the "Take Ownership..." option.
- ↑ https://web.archive.org/web/20240422185730/https://lore.kernel.org/lkml/CAHk-=whDuqyVC6xMkOnNt2EeTd-s4uqa3sYghj5UzkELFW2bpw@mail.gmail.com/
- ↑ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2c61db29f27
- ↑ According to the Bcachefs maintainer, the 30 August 2025, "btrfs is still eating filesystems - they may be better than they were, but I still see reports regularly, and they don't seem to be taking reliability seriously"
- ↑ https://en.wikipedia.org/wiki/ReiserFS#fsck
-
↑ 7.07.17.27.37.4
The Linux kernel documentation for the REISERFS_FS option tells that:
Reiserfs is deprecated and scheduled to be removed from the kernel
in 2025. If you are still using it, please migrate to another
filesystem or tell us your usecase for reiserfs.
In practice it is not available anymore since Linux 6.13, so if you need to migrate your data, you will need to use in one way or another Linux 6.12 or earlier. kenrel.org lists the versions currently maintained and it is also possible to install (older) GNU/Linux distributions that ship a Linux version earlier than 6.13. - ↑ According to the Linux XFS driver documentation, "[Support for mounting V4 filesystems] will default to yes until September 2025". This means that some distributions that use the defaults will most likely end up disabling support for XFS v4.
- ↑ 9.09.1 According to the Linux XFS driver documentation, "In September 2030, support [for XFS v4] will be removed from the codebase entirely [in Linux]"
- ↑ 10.0010.0110.0210.0310.0410.0510.0610.0710.0810.0910.1010.11 This tells if that filesystem can be used in a system.scm system definition.
- ↑ 11.0011.0111.0211.0311.0411.0511.0611.0711.0811.0911.1011.11 Since users simply run commands manually during the manual installation, they can easily use the (packaged) tools to create new filesystems and add them to /etc/fstab for automatic mounting.
- ↑ The installation fails with an error.
- ↑ 13.013.1 There is no HURD installer yet.
- ↑ After creating the rootfs with mkfs.ext4 from Guix, in Replicant, it says "Corrupted <vendor> SD card" in the notification bar.
- ↑ We can easily view the card content with "File Manager". It also detects a new MicroSD card when it is just formatted.
- ↑ The installation fails with an error.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils package.
- ↑ There is no hfsutils repository in the manifest.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs package.
- ↑ There is no hfsprogs repository in the manifest.
- ↑ The installation fails with an error.
- ↑ The graphical installer complains about some UUID related issue
- ↑ In the graphical installer, the installation fails with: "The installer has encountered an unexpected problem. [...]", and we then get a stacktrace. If we manually install with the same system.scm we'd probably get the exact same stacktrace.
- ↑ Once installed, the rootfs is mounted with FUSE and ntfs-3g.
- ↑ The installation succeeds, but then sudo and policykit are broken due to wrong permissions. So users can't install any software. It's also a very bad idea to use NTFS since there is at the time of writing no way to safely repair corrupted NTFS filesystems with free software: The only tools we have are in ntfs-3g and they are way too experimental and dangerous so they are probably not shipped by any distribution.
- ↑ 30.030.130.2 According to the reiser 4 wiki, upstream Linux has no reiser4 support.
- ↑ 31.031.131.231.331.4 https://guix.gnu.org/manual/devel/en/guix.html#FOOT10
- ↑ Linux has "Windows Logical Disk Manager (Dynamic Disk) support", but it only support the format until Windows Vista with MBR only. This was verified by reading the Linux driver in Linux 6.18-rc6.
- ↑ https://github.com/qvr/nonraid
- ↑ See the fuse-exfat package for more details.
- ↑ See the ntfs-3g package for more details.