This wikipedia article compare general and technical information for a number of file systems including Linux and UNIX file systems.
There is also a good resource available from Novell:
Linux offers a number of file systems. This paper discusses these file systems, why there are so many, and which ones are the best to use for which workloads and data. Not all data is the same. Not all workloads are the same. Not all filesystems are the same. Matching the file system to the data and workload allows customers to build efficient scalable and cost effective solutions. The next section of this document describes four general workload areas. It is important to understand these different workloads and their requirements, as these drive requirements into file systems. This will also serve as a guide in comparing and contrasting the various file systems available in the market today.
You may also find our own articles useful:
- Understanding UNIX / Linux file system part
- Understanding UNIX/Linux filesystem Superblock
- Surviving a Linux Filesystem Failures
- Understanding UNIX/Linux filesystem Inodes
- Understanding UNIX/Linux filesystem directories
- Understanding UNIX/Linux symbolic (soft) and hard links
- Why isnâ€™t it possible to create hard links across file system boundaries?
|Category||List of Unix and Linux commands|
|Firewall||CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04|
|Network Utilities||dig • host • ip • nmap|
|OpenVPN||CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04|
|Package Manager||apk • apt|
|Processes Management||bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time|
|Searching||grep • whereis • which|
|User Information||groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w|
|WireGuard VPN||CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04|