File System: Difference between revisions

Revision as of 08:07, 6 July 2025

File System

A file system is a method and data structure that an operating system uses to manage files on a disk or partition. It provides the mechanisms for creating, reading, writing, and deleting files as well as managing storage space on the physical media. File systems are crucial for both personal and enterprise computing as they determine how data is organized, stored, and accessed.

Introduction

In computing, a file system is responsible for the logical organization of files, storage, and retrieval. It provides a way for users and applications to store data in a structured manner, enabling efficient access and management. File systems abstract the underlying physical storage, allowing users to interact with files using human-friendly names rather than complex binary data. With the advent of various storage media, file systems have evolved to optimize for different types of operations and hardware characteristics.

History

The concept of a file system originated with early mainframe computers in the 1950s, where data was stored in punch cards and magnetic tapes. As technology progressed, the need for more sophisticated data management techniques emerged. In the 1960s and 1970s, operating systems such as MULTICS and UNIX introduced hierarchical file systems that organized data into directories and subdirectories, leading to a more intuitive structure for users.

Throughout the years, several innovations in file system design have emerged to accommodate the growing complexity of data storage and retrieval. For instance, the introduction of hard disk drives (HDD) in the late 1970s necessitated the development of file systems capable of managing larger volumes of data. Notable examples include the FAT (File Allocation Table) file system developed by Microsoft, which became one of the most widely used file systems for personal computers.

In the 1980s and 1990s, advancements in technology led to the development of more robust file systems, such as NTFS (New Technology File System) introduced by Microsoft with Windows NT. NTFS offered features like file system journaling, which improved reliability, and support for larger files and volumes. Concurrently, UNIX-based systems adopted file systems like ext2 and later ext3 and ext4, which included improvements in performance and features such as journaling and extended attributes.

In the 21st century, the emergence of flash storage devices and solid-state drives (SSD) prompted further innovation in file systems, including those designed specifically for these technologies like APFS (Apple File System) and Btrfs (B-tree file system). These new file systems provide enhancements such as snapshot capabilities, dynamic allocation, and improved performance.

Design and Architecture

The design and architecture of a file system involve several key components and concepts, which collectively dictate how data is structured, stored, accessed, and managed. Understanding these components is essential to grasp the functioning of different file systems.

1. File Hierarchy

The file hierarchy is a core component of most file systems, resembling an inverted tree structure where files are organized within directories (or folders). This structure allows for easy navigation and organization of files. The root directory sits at the top of the hierarchy, with subsequent subdirectories leading to individual files.

2. Metadata

Metadata is essential for file systems, as it provides information about files, such as their size, type, permissions, creation date, and modification date. Most file systems store metadata in a separate structure from the actual file data, allowing for quick access and management.

3. Block Allocation

Storage on disk drives is typically organized in fixed-size blocks or clusters. A file system uses block allocation to manage how data is physically stored. File systems may utilize contiguous allocation, linked allocation, or indexed allocation, each having its advantages and disadvantages in terms of performance and fragmentation.

Contiguous Allocation stores files in consecutive blocks on the storage medium, minimizing seek time but leading to fragmentation as files are created and deleted over time.
Linked Allocation links file blocks using pointers, facilitating efficient storage but possibly resulting in increased seek time due to non-contiguous storage.
Indexed Allocation maintains an index block to keep track of the various blocks of a file, providing a balanced approach to performance and fragmentation concerns.

4. Journaling

File systems often implement journaling as a means of enhancing data integrity and recovery. A journal, or log, records changes made to the file system before they are committed. In the event of a system crash or power failure, the file system can be restored to a consistent state by replaying the journal entries.

5. Access Control and Permissions

Another critical aspect of file systems is how they manage user access and permissions. This security feature dictates what users can do with each file, including reading, writing, or executing. Most modern file systems support Access Control Lists (ACLs) that allow for fine-grained control over file permissions.

Usage and Implementation

File systems are implemented across various operating systems and storage mediums, each tailored to meet specific needs regarding performance, reliability, and usability. They play a critical role in the functioning of operating systems, databases, and applications.

1. Operating Systems

Different operating systems utilize specific file systems to store and manage data. For example:

**Windows** primarily uses NTFS for its Windows NT-based operating systems, while FAT32 is often employed for external drives and compatibility with older systems.
**Linux** supports a variety of file systems, including ext3, ext4, Btrfs, and XFS, among others, allowing users to choose based on their performance and reliability needs.
**macOS** employs APFS, which optimizes performance for SSDs, enabling features like snapshot capabilities and space-efficient storage.

2. Specialized File Systems

Aside from standard file systems, there are specialized files systems designed for specific applications:

**Database File Systems**: These file systems support data management more akin to databases, optimizing for transactional workloads and enabling multi-user access. Examples include ZFS (Zettabyte File System) and Oracle's DBFS.
**Network File Systems**: These file systems allow files to be shared among multiple users across a network. NFS (Network File System) and SMB (Server Message Block) are well-known examples that enable remote file access and collaboration.

3. Flash Storage and SSDs

The design of file systems for flash storage and SSDs emphasizes performance and endurance. File systems like APFS, F2FS (Flash-Friendly File System), and ext4 with SSD optimizations consider the unique characteristics of flash memory, such as wear leveling and reduced random write speed, to maximize efficiency and lifespan.

Real-world Examples

Numerous file systems exist, with varying features and performance metrics. Below are some prominent examples:

1. FAT32

FAT32 (File Allocation Table 32) is one of the oldest file systems still in widespread use today. Introduced by Microsoft in the 1970s, FAT32 supports file sizes up to 4 GB and volumes up to 8 TB. It is compatible with virtually all operating systems, which contributes to its popularity for external drives and flash storage.

2. NTFS

NTFS provides advanced features such as journaling, file permissions, encryption, and support for large files and volumes. As the primary file system for Windows, NTFS is utilized in many enterprise environments, offering a robust solution for data protection and integrity.

3. ext4

ext4 is a widely used file system in Linux environments, known for its speed, reliability, and ease of use. It includes a journaling feature, supports large files (up to 16 TB), and provides backward compatibility with ext3. ext4’s design allows for a more efficient allocation of space, reducing fragmentation and enhancing performance.

4. APFS

APFS is the file system introduced by Apple for macOS and iOS that optimizes for flash storage. APFS features such as snapshot capability, space sharing, and strong encryption address modern storage and security needs, making it an ideal choice for Apple's devices.

5. Btrfs

Btrfs is a modern file system for Linux that offers advanced features like snapshots, RAID support, and volume management. Btrfs is designed to facilitate easier management of disk storage and aims to address many limitations found in older file systems.

Criticism and Controversies

While many file systems have garnered significant attention for their advancements and features, they also face criticism and controversies concerning their design and implementation.

1. Fragmentation

One of the significant challenges that file systems encounter is fragmentation, a phenomenon where data is not stored in contiguous blocks, leading to performance degradation. File systems like FAT32 and NTFS can suffer from fragmentation over time, resulting in increased seek times and slower read/write speeds. Various defragmentation tools attempt to mitigate this issue, but they can be time-consuming and imperfect solutions.

2. Limited Compatibility

Some file systems have limited compatibility across different operating systems. For example, NTFS is not natively supported by macOS for writing, which can lead to data transfer challenges between different systems. This lack of interoperability highlights the importance of utilizing widely adopted file systems for external storage.

3. Complexity and Management

File systems such as Btrfs and ZFS offer powerful features, yet their complexity can be a barrier to users and system administrators. Properly configuring and managing advanced features, including snapshots and RAID configurations, requires significant expertise and can introduce risks if not done correctly.

Influence and Impact

File systems have been instrumental in shaping the way data is stored, managed, and retrieved. Their design and functionality have profound implications in numerous contexts.

1. Data Integrity and Recovery

File systems with advanced features, such as journaling, contribute to data integrity by ensuring that systems can recover to a consistent state after failures. This capability is crucial for enterprise applications and systems that require high availability and reliability.

2. User Experience

The organization and access provided by file systems highly influence user experience for individuals and businesses alike. File systems that allow intuitive navigation, effective search capabilities, and quick access to data result in improved productivity and satisfaction.

3. Innovation and Development

The ongoing development of new file systems pushes the envelope in data management technologies, influencing the broader landscape of computing. Newer file systems cater to the demands of modern hardware, such as SSDs and cloud storage, leading to innovations that can change foundational computing principles.

References

@@ Line 1: / Line 1: @@
+== File System ==
+A '''file system''' is a method and data structure that an operating system uses to manage files on a disk or partition. It provides the mechanisms for creating, reading, writing, and deleting files as well as managing storage space on the physical media. File systems are crucial for both personal and enterprise computing as they determine how data is organized, stored, and accessed.
 == Introduction ==
-A file system is a vital component of modern computer architectures that organizes, stores, retrieves, and manages data on storage devices. File systems enable users and applications to interact with data through a hierarchical structure of files and directories, providing methods for data identification, access, and management. Depending on the specific implementation, a file system can dictate how data is formatted, stored, and managed on various types of storage media.
-== History or Background ==
+In computing, a file system is responsible for the logical organization of files, storage, and retrieval. It provides a way for users and applications to store data in a structured manner, enabling efficient access and management. File systems abstract the underlying physical storage, allowing users to interact with files using human-friendly names rather than complex binary data. With the advent of various storage media, file systems have evolved to optimize for different types of operations and hardware characteristics.
-The evolution of file systems is tied closely to advancements in computer technology and the need for efficient data management. In the early days of computing, data was typically stored on punch cards or magnetic tape, necessitating rudimentary methods for data organization. As hard disk drives (HDDs) and solid-state drives (SSDs) became prevalent, more sophisticated file systems were developed.
+== History ==
+The concept of a file system originated with early mainframe computers in the 1950s, where data was stored in punch cards and magnetic tapes. As technology progressed, the need for more sophisticated data management techniques emerged. In the 1960s and 1970s, operating systems such as MULTICS and UNIX introduced hierarchical file systems that organized data into directories and subdirectories, leading to a more intuitive structure for users.
+Throughout the years, several innovations in file system design have emerged to accommodate the growing complexity of data storage and retrieval. For instance, the introduction of hard disk drives (HDD) in the late 1970s necessitated the development of file systems capable of managing larger volumes of data. Notable examples include the FAT (File Allocation Table) file system developed by Microsoft, which became one of the most widely used file systems for personal computers.
+In the 1980s and 1990s, advancements in technology led to the development of more robust file systems, such as NTFS (New Technology File System) introduced by Microsoft with Windows NT. NTFS offered features like file system journaling, which improved reliability, and support for larger files and volumes. Concurrently, UNIX-based systems adopted file systems like ext2 and later ext3 and ext4, which included improvements in performance and features such as journaling and extended attributes.
+In the 21st century, the emergence of flash storage devices and solid-state drives (SSD) prompted further innovation in file systems, including those designed specifically for these technologies like APFS (Apple File System) and Btrfs (B-tree file system). These new file systems provide enhancements such as snapshot capabilities, dynamic allocation, and improved performance.
+== Design and Architecture ==
+The design and architecture of a file system involve several key components and concepts, which collectively dictate how data is structured, stored, accessed, and managed. Understanding these components is essential to grasp the functioning of different file systems.
+=== 1. File Hierarchy ===
+The file hierarchy is a core component of most file systems, resembling an inverted tree structure where files are organized within directories (or folders). This structure allows for easy navigation and organization of files. The root directory sits at the top of the hierarchy, with subsequent subdirectories leading to individual files.
-The first file systems emerged with early operating systems such as CP/M (Control Program for Microcomputers) in the 1970s, which introduced a basic structure for organizing files on floppy disks. The development of UNIX in the late 1960s and its introduction of the hierarchical file system structure had profound implications for subsequent file system designs. This system employed a tree-like structure, allowing for seamless navigation and file management.
+=== 2. Metadata ===
-As personal computing became common in the 1980s and 1990s, various proprietary file systems emerged, including FAT (File Allocation Table) used by MS-DOS and later Windows operating systems, and HFS (Hierarchical File System) adopted by Apple's Macintosh systems. The latter half of the 20th century also saw the emergence of advanced file systems such as NTFS (New Technology File System), which introduced features like journaled file systems and support for large files.
+Metadata is essential for file systems, as it provides information about files, such as their size, type, permissions, creation date, and modification date. Most file systems store metadata in a separate structure from the actual file data, allowing for quick access and management.
-== Design or Architecture ==
+=== 3. Block Allocation ===
-File systems are designed with several key components and concepts that dictate how data is stored and accessed. The two primary components of a file system are the file and the directory.
-=== File Structure ===
+Storage on disk drives is typically organized in fixed-size blocks or clusters. A file system uses block allocation to manage how data is physically stored. File systems may utilize contiguous allocation, linked allocation, or indexed allocation, each having its advantages and disadvantages in terms of performance and fragmentation.
-A file is the basic unit of storage in a file system. Each file is identified by a unique name and may consist of a variety of data types, ranging from text and images to executable code. File systems support various file attributes, including size, type, creation date, modification date, and permissions, which control access by users and applications.
+* '''Contiguous Allocation''' stores files in consecutive blocks on the storage medium, minimizing seek time but leading to fragmentation as files are created and deleted over time.
+* '''Linked Allocation''' links file blocks using pointers, facilitating efficient storage but possibly resulting in increased seek time due to non-contiguous storage.
+* '''Indexed Allocation''' maintains an index block to keep track of the various blocks of a file, providing a balanced approach to performance and fragmentation concerns.
-=== Directory Structure ===
+=== 4. Journaling ===
-Directories, also known as folders, are used to organize files into a hierarchical structure. This tree-like architecture allows users to create nested directories, facilitating easier file management and retrieval. Directory entries can include metadata about the contained files, enhancing information management capabilities.
-=== Allocation Methods ===
+File systems often implement journaling as a means of enhancing data integrity and recovery. A journal, or log, records changes made to the file system before they are committed. In the event of a system crash or power failure, the file system can be restored to a consistent state by replaying the journal entries.
-File systems employ differing allocation methods to manage how files are stored on disk. Common allocation strategies include:
-* '''Contiguous Allocation''': Files are stored in a contiguous block of storage. This method simplifies access speed but can lead to fragmentation over time.
-* '''Linked Allocation''': Each file consists of a linked list of blocks, which allows non-contiguous storage but requires additional overhead for managing links.
-* '''Indexed Allocation''': An index block is utilized to point to the various data blocks of a file. This method balances fragmented storage with ease of access.
-=== Metadata Management ===
+=== 5. Access Control and Permissions ===
-Modern file systems store extensive metadata for files and directories. This metadata contains information necessary for file retrieval and manipulation, including the location of the file on the storage device, access control information, and attributes affecting file behavior.
-=== Journaling and Recovery ===
+Another critical aspect of file systems is how they manage user access and permissions. This security feature dictates what users can do with each file, including reading, writing, or executing. Most modern file systems support Access Control Lists (ACLs) that allow for fine-grained control over file permissions.
-To enhance data integrity, many contemporary file systems utilize journaling techniques, which log changes before they are applied. In the case of a power failure or crash, this feature facilitates recovery of the file system to a consistent state, minimizing data loss and corruption.
 == Usage and Implementation ==
-File systems are implemented across a wide range of operating systems and storage devices. Their usage varies by context, from personal computing to enterprise-level data management systems.
-=== Operating Systems ===
+File systems are implemented across various operating systems and storage mediums, each tailored to meet specific needs regarding performance, reliability, and usability. They play a critical role in the functioning of operating systems, databases, and applications.
-Different operating systems adopt various file systems natively:
-* '''Windows''': Utilizes several file systems, including FAT32, exFAT, and NTFS. NTFS is prevalent due to its support for larger files and advanced features such as encryption, compression, and permissions.
+=== 1. Operating Systems ===
-* '''Unix/Linux''': Commonly uses file systems such as ext3, ext4, XFS, and Btrfs. These systems are preferred for their stability, performance, and advanced features, especially in server environments.
-* '''macOS''': Utilizes APFS (Apple File System), which is designed for SSDs, featuring space efficiency, strong encryption, and snapshots.
+Different operating systems utilize specific file systems to store and manage data. For example:
+* **Windows** primarily uses NTFS for its Windows NT-based operating systems, while FAT32 is often employed for external drives and compatibility with older systems.
+* **Linux** supports a variety of file systems, including ext3, ext4, Btrfs, and XFS, among others, allowing users to choose based on their performance and reliability needs.
+* **macOS** employs APFS, which optimizes performance for SSDs, enabling features like snapshot capabilities and space-efficient storage.
+=== 2. Specialized File Systems ===
+Aside from standard file systems, there are specialized files systems designed for specific applications:
+* **Database File Systems**: These file systems support data management more akin to databases, optimizing for transactional workloads and enabling multi-user access. Examples include ZFS (Zettabyte File System) and Oracle's DBFS.
+* **Network File Systems**: These file systems allow files to be shared among multiple users across a network. NFS (Network File System) and SMB (Server Message Block) are well-known examples that enable remote file access and collaboration.
+=== 3. Flash Storage and SSDs ===
+The design of file systems for flash storage and SSDs emphasizes performance and endurance. File systems like APFS, F2FS (Flash-Friendly File System), and ext4 with SSD optimizations consider the unique characteristics of flash memory, such as wear leveling and reduced random write speed, to maximize efficiency and lifespan.
+== Real-world Examples ==
+Numerous file systems exist, with varying features and performance metrics. Below are some prominent examples:
+=== 1. FAT32 ===
+FAT32 (File Allocation Table 32) is one of the oldest file systems still in widespread use today. Introduced by Microsoft in the 1970s, FAT32 supports file sizes up to 4 GB and volumes up to 8 TB. It is compatible with virtually all operating systems, which contributes to its popularity for external drives and flash storage.
+=== 2. NTFS ===
+NTFS provides advanced features such as journaling, file permissions, encryption, and support for large files and volumes. As the primary file system for Windows, NTFS is utilized in many enterprise environments, offering a robust solution for data protection and integrity.
+=== 3. ext4 ===
+ext4 is a widely used file system in Linux environments, known for its speed, reliability, and ease of use. It includes a journaling feature, supports large files (up to 16 TB), and provides backward compatibility with ext3. ext4’s design allows for a more efficient allocation of space, reducing fragmentation and enhancing performance.
+=== 4. APFS ===
+APFS is the file system introduced by Apple for macOS and iOS that optimizes for flash storage. APFS features such as snapshot capability, space sharing, and strong encryption address modern storage and security needs, making it an ideal choice for Apple's devices.
+=== 5. Btrfs ===
+Btrfs is a modern file system for Linux that offers advanced features like snapshots, RAID support, and volume management. Btrfs is designed to facilitate easier management of disk storage and aims to address many limitations found in older file systems.
+== Criticism and Controversies ==
+While many file systems have garnered significant attention for their advancements and features, they also face criticism and controversies concerning their design and implementation.
-=== Embedded Systems ===
+=== 1. Fragmentation ===
-Many embedded systems utilize specialized file systems to manage storage resources efficiently. Examples include FAT for simple devices and JFFS2 (Journaling Flash File System) for flash memory devices, catering to the unique constraints of memory-limited environments.
-=== Cloud Storage ===
+One of the significant challenges that file systems encounter is fragmentation, a phenomenon where data is not stored in contiguous blocks, leading to performance degradation. File systems like FAT32 and NTFS can suffer from fragmentation over time, resulting in increased seek times and slower read/write speeds. Various defragmentation tools attempt to mitigate this issue, but they can be time-consuming and imperfect solutions.
-Cloud storage solutions employ distributed file systems that allow for data storage across multiple servers. Technologies like Google File System (GFS) and Hadoop Distributed File System (HDFS) optimize file storage and retrieval in a distributed computing environment, enhancing reliability and scalability.
-== Real-world Examples or Comparisons ==
+=== 2. Limited Compatibility ===
-Different file systems provide distinctive features, and their choice often reflects the requirements of specific applications or user needs.
-=== NTFS vs. FAT32 ===
+Some file systems have limited compatibility across different operating systems. For example, NTFS is not natively supported by macOS for writing, which can lead to data transfer challenges between different systems. This lack of interoperability highlights the importance of utilizing widely adopted file systems for external storage.
-NTFS supports larger file sizes and volumes compared to FAT32, making it more suitable for modern computing needs, particularly concerning security features like file permissions and encryption. However, FAT32 remains widely used, especially for compatibility with older systems and devices like USB drives.
-=== ext4 vs. Btrfs ===
+=== 3. Complexity and Management ===
-While ext4 is known for its performance and reliability, Btrfs offers advanced features such as snapshotting, built-in RAID capabilities, and self-healing mechanisms. Btrfs, still under development, aims to offer a comprehensive solution for managing larger data volumes and enhancing data integrity.
-=== APFS vs. HFS+ ===
+File systems such as Btrfs and ZFS offer powerful features, yet their complexity can be a barrier to users and system administrators. Properly configuring and managing advanced features, including snapshots and RAID configurations, requires significant expertise and can introduce risks if not done correctly.
-Apple’s APFS is optimized for SSDs, implementing features like space sharing, cloning, and snapshots, while HFS+ is the older file system used across macOS before APFS. Transitioning to APFS indicates a significant advancement in performance and organizational capabilities for Apple users.
-== Criticism or Controversies ==
+== Influence and Impact ==
-Various file systems face scrutiny for limitations or drawbacks relevant to their design and implementation. Criticisms often center on performance issues, scalability, data integrity vulnerabilities, and lack of interoperability.
-=== Performance Concerns ===
+File systems have been instrumental in shaping the way data is stored, managed, and retrieved. Their design and functionality have profound implications in numerous contexts.
-Certain file systems can exhibit performance degradation under heavy loads, specifically those not designed for high transaction environments. For instance, while NTFS is robust, it can show slowdowns when managing a large number of files or in fragmented states.
-=== Data Integrity Issues ===
+=== 1. Data Integrity and Recovery ===
-While journaling file systems enhance data integrity, the complexity involved may lead to situations where corruption occurs under specific conditions, such as power failures or hardware malfunctions, if the system fails to write the journal correctly.
-=== Interoperability Limitations ===
+File systems with advanced features, such as journaling, contribute to data integrity by ensuring that systems can recover to a consistent state after failures. This capability is crucial for enterprise applications and systems that require high availability and reliability.
-Some file systems lack cross-platform support, limiting their usefulness in mixed-environment settings. For example, while NTFS can be read on Linux systems with specific software, its write capabilities are often restricted without supplementary drivers.
-== Influence or Impact ==
+=== 2. User Experience ===
-The influence of file systems extends beyond their basic functionality, fundamentally shaping how data is managed and utilized in computing.
-=== Impacts on User Experience ===
+The organization and access provided by file systems highly influence user experience for individuals and businesses alike. File systems that allow intuitive navigation, effective search capabilities, and quick access to data result in improved productivity and satisfaction.
-File systems greatly influence the user experience, as efficient data management can enhance productivity and accessibility. Users’ interactions with databases, applications, and their filesystem's operations directly affect their ability to find and manage files.
-=== Technological Advancements ===
+=== 3. Innovation and Development ===
-As data consumption expands exponentially, robust file system designs adapt to emerging trends in technology, including cloud computing, big data, and enhanced security protocols. Developers continuously work to enhance scalability and user efficiency in data handling.
-=== Future Directions ===
+The ongoing development of new file systems pushes the envelope in data management technologies, influencing the broader landscape of computing. Newer file systems cater to the demands of modern hardware, such as SSDs and cloud storage, leading to innovations that can change foundational computing principles.
-Emerging technologies such as non-volatile memory (NVM) and storage-class memory (SCM) require innovative file system designs that optimize performance while maintaining data integrity, security, and accessibility. As devices and their data storage capabilities evolve, so too must the systems that manage them.
-== See also ==
+== See Also ==
-* [[Filesystem Hierarchy Standard]]
+* [[Access Control List]]
-* [[File system permissions]]
+* [[Cluster (computing)]]
-* [[Comparative overview of file systems]]
+* [[Journaling file system]]
-* [[File system metadata]]
+* [[Metadata]]
-* [[Distributed file system]]
+* [[Solid-state drive]]
-* [[Journaling file systems]]
+* [[Network File System]]
+* [[Unix file system]]
+* [[File extension]]
 == References ==
-* [https://www.microsoft.com/en-us/learn/ntfs-vs-fat32.aspx Microsoft NTFS vs FAT32 Comparison]
+* [https://www.microsoft.com/en-us/windows/windows-10-specifications Microsoft Windows 10 Specifications]
-* [https://ext4.wiki.kernel.org/index.php/Main_Page Ext4 Wiki - The Linux Kernel]
+* [https://www.linux.org/ Linux.org]
-* [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs Wiki - The Linux Kernel]
+* [https://developer.apple.com/filesystems/ Apple File System Overview]
-* [https://developer.apple.com/apfs/ Apple APFS Overview]
+* [https://wiki.archlinux.org/title/Filesystem Arch Linux Filesystem Documentation]
-* [https://docs.microsoft.com/en-us/windows/win32/fileio/file-system-architecture Windows File System Architecture]
+* [https://www.oracle.com/database/technologies/standard-file-system.html Oracle Database File System]
-* [http://www.haiku-os.org Haiku Operating System: File Systems]
+* [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs Wiki]
-* [https://www.linuxfoundation.org Linux Foundation - File Systems Overview]
-* [https://www.freebsd.org/doc/handbook/geom.html FreeBSD Handbook: GEOM]
 [[Category:File systems]]
 [[Category:Computer storage]]
-[[Category:Computing]]
+[[Category:Computer science]]