A file system supplies rules and metadata for organizing named files and directories on storage. It turns a set of addressable locations into a structure applications can navigate without managing raw block placement themselves.
How the pieces connect
Metadata can track names, allocation, permissions, timestamps, and other properties. Different designs make different choices about features and compatibility. The operating system interprets those rules through its file-system components and maps requests onto lower storage layers. A device controller does not ordinarily decide what a folder name means.
An everyday example
A removable device can be readable on one operating system and expose different functionality on another because compatibility for its file-system features differs. The physical connector and storage medium may be fully recognized while the higher-level organization remains the relevant compatibility question. These are separate stages of understanding the same piece of equipment.
Reading the information in context
Formatting selects or creates a file-system arrangement and can affect access to existing information; it is not a harmless identification step. This reference contains no format commands. When reading a storage description, distinguish the medium's physical capacity from usable file-system space and from the features the current operating system can interpret.
Storage
Note these before you change anything
Useful facts to have to hand while reading about what a file system organizes.
- A current backup before any change
- Controller mode in firmware: AHCI, RAID or NVMe
- Storage controller driver name and version
- Drive health shown by the maker's own diagnostics
Storage: Reading and writing data
- File systemfiles and folders
- Storage stackvolumes and partitions
- Controller driverNVMe, AHCI or RAID
- Controlleron the board or a card
- DriveSSD or HDD
