# XFS file system

**URL:** <https://community.fly.io/t/xfs-file-system/6043>\
**Category:** General\
**Created:** [July 18, 2022, 10:28pm UTC](https://community.fly.io/t/xfs-file-system/6043 "2022-07-18T22:28:55Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kaz](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kaz/32/15109_2.png) [@kaz](https://community.fly.io/u/kaz)\
**Post date:** [August 9, 2024, 6:14pm UTC](https://community.fly.io/t/xfs-file-system/6043/5 "2024-08-09T18:14:22Z")

</div>

The PR has been merged. You can create an unformatted block device. The future is already here!

BUT, our Linux kernel support neither xfs nor zfs.

```auto
root@e2867529cd12e8:/go# cat /proc/filesystems 
nodev sysfs
nodev tmpfs
nodev bdev
nodev proc
nodev cgroup
nodev cgroup2
nodev cpuset
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev tracefs
nodev securityfs
nodev sockfs
nodev bpf
nodev pipefs
nodev ramfs
nodev hugetlbfs
nodev rpc_pipefs
nodev devpts
        ext3
        ext2
        ext4
        squashfs
nodev nfs
nodev nfs4
nodev autofs
        fuseblk
nodev fuse
nodev fusectl
nodev overlay
nodev ceph
nodev mqueue
nodev selinuxfs
nodev pstore

```

Let me confirm adding these additional filesystems significantly affect our Linux kernel’s memory footprint. That’s the only concern I have.

---

_[View the full topic](https://community.fly.io/t/xfs-file-system/6043)._
