Skip to content
Snippets Groups Projects
Commit 263ee911 authored by Tom Ridley's avatar Tom Ridley
Browse files

Changing inode wording to be more user friendly

parent 85484c7d
No related branches found
No related tags found
No related merge requests found
Pipeline #188744 passed
...@@ -44,10 +44,14 @@ If you follow the links within JuDoor to KontView, more detailed statistic on da ...@@ -44,10 +44,14 @@ If you follow the links within JuDoor to KontView, more detailed statistic on da
:::info[What is an `inode`?] :::info[What is an `inode`?]
An inode (index node) is a data structure used in Unix file systems to store metadata about files and directories. It serves as a unique identifier for each file/directory on the file system. Here are the key points about inodes: An inode (index node) is a data structure used in Unix file systems to store metadata about files and directories.
* Each file/directory has an associated inode that stores its metadata, such as file type, permissions, ownership, timestamps, and pointers to the file's data blocks on disk. It serves as a unique identifier for each file/directory on the file system.
Key points about inodes include:
* Each file has an associated inode that stores its metadata, such as file type, permissions, ownership, timestamps, and pointers to the file's data blocks on disk. Each directory also has at least one associated inode that contains similar information.
* inodes are identified by a unique number within a file system. This inode number is used by the operating system to access the file's metadata and data blocks. * inodes are identified by a unique number within a file system. This inode number is used by the operating system to access the file's metadata and data blocks.
* Each file system has a fixed number of inodes determined during its creation, limiting the maximum number of files it can hold. Running out of inodes can cause issues even if disk space is available. * Each file system has a fixed number of inodes determined during its creation, limiting the maximum number of files it can hold. Running out of inodes can cause issues even if disk space is available. This is one of several reasons large numbers of small files or complex directory trees are not ideal.
* More inodes in a system can mean a longer time to look up files.
* In general, large numbers of small files leads to lower performance or performance issues.
::: :::
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment