Inodes concept in Linux CLI - Mini Project: Build & Apply

Understanding Inodes in Linux

📖 Scenario: You are learning how Linux stores information about files using inodes. Each file has an inode that holds metadata like file size, permissions, and location on disk. Understanding inodes helps you manage files better.

🎯 Goal: Learn how to check inode numbers of files and count files using inode-related commands in Linux.

📋 What You'll Learn

Use the ls -i command to list files with their inode numbers

Create a directory and files inside it

Use the find command to count files by inode

Display the inode number of a specific file

💡 Why This Matters

🌍 Real World

Understanding inodes helps in file system management, troubleshooting disk space issues, and recovering files.

💼 Career

System administrators and developers use inode knowledge to manage Linux servers and optimize storage.

1

Create a directory and files

Create a directory called myfiles and inside it create two empty files named file1.txt and file2.txt using the mkdir and touch commands.

Linux CLI

# Your code here

Hint

Use mkdir myfiles to create the folder, then cd myfiles to enter it, and touch file1.txt file2.txt to create the files.

2

List files with inode numbers

Use the ls -i command inside the myfiles directory to list the files along with their inode numbers.

Linux CLI

mkdir myfiles
cd myfiles
touch file1.txt file2.txt
# Your code here

Hint

Run ls -i to see inode numbers next to each file name.

3

Find and count files by inode

Use the find . -inum command to find files by their inode number. First, get the inode number of file1.txt using ls -i file1.txt, then use find . -inum [inode_number] to find it. Replace [inode_number] with the actual number.

Linux CLI

mkdir myfiles
cd myfiles
touch file1.txt file2.txt
ls -i
# Your code here

Hint

Use command substitution to store the inode number, then use find . -inum with that number.

4

Display inode number of a file

Print the inode number of file2.txt using the ls -i file2.txt command.

Linux CLI

mkdir myfiles
cd myfiles
touch file1.txt file2.txt
ls -i
inode=$(ls -i file1.txt | cut -d' ' -f1)
find . -inum $inode
# Your code here

Hint

Use ls -i file2.txt to show its inode number and file name.

Practice

1. What does an inode in a Linux file system primarily store?

easy

A. The path to the file's location

B. The file name and its extension

C. Metadata about a file like permissions and size

D. The content of the file

Solution

1. Step 1: Understand inode purpose

   An inode stores metadata such as file permissions, ownership, size, and timestamps, but not the file name.

2. Step 2: Differentiate inode from file name storage

   The file name is stored separately in directory entries, not in the inode itself.

3. Final Answer:

   Metadata about a file like permissions and size -> Option C

4. Quick Check:

   Inode = Metadata [OK]

Hint: Inodes store file info, not names or content [OK]

Common Mistakes:

• Thinking inode stores file names
• Confusing inode with file content
• Assuming inode stores file path

2. Which command correctly shows the inode number of files in a directory?

easy

A. ls -i

B. ls -l

C. ls -a

D. ls -h

Solution

1. Step 1: Recall ls command options

   The ls -i command lists files with their inode numbers.

2. Step 2: Verify other options

   ls -l shows detailed info without inode, ls -a shows hidden files, ls -h shows sizes in human-readable form.

3. Final Answer:

   ls -i -> Option A

4. Quick Check:

   ls -i = inode numbers [OK]

Hint: Use ls -i to see inode numbers quickly [OK]

Common Mistakes:

• Using ls -l expecting inode numbers
• Confusing ls -a with inode display
• Trying ls -h for inode info

3. Given the output of ls -i shows two files with the same inode number, what does this indicate?

medium

A. The files are hard links pointing to the same data

B. The files have identical names

C. The files are located in different directories

D. The files are symbolic links

Solution

1. Step 1: Understand inode sharing

   Two files with the same inode number mean they share the same data on disk, which happens with hard links.

2. Step 2: Differentiate link types

   Symbolic links have different inodes; identical names or directories don't affect inode numbers.

3. Final Answer:

   The files are hard links pointing to the same data -> Option A

4. Quick Check:

   Same inode = hard links [OK]

Hint: Same inode means hard links share data [OK]

Common Mistakes:

• Confusing symbolic links with hard links
• Assuming same inode means same name
• Ignoring inode uniqueness

4. You run ls -i but get an error: ls: invalid option -- 'i'. What is the likely cause?

medium

A. Not having permission to list files

B. Using a non-Linux system where ls lacks -i option

C. Typing the command incorrectly as ls -l

D. The directory is empty

Solution

1. Step 1: Analyze error message

   The error says invalid option -- 'i', meaning the ls command does not recognize -i.

2. Step 2: Identify environment cause

   This often happens on non-Linux systems (like some Unix variants) where ls lacks the -i option.

3. Final Answer:

   Using a non-Linux system where ls lacks -i option -> Option B

4. Quick Check:

   Invalid option = unsupported ls -i [OK]

Hint: Check OS if ls -i option fails [OK]

Common Mistakes:

• Assuming typo in command
• Thinking permission causes option error
• Assuming empty directory causes option error

5. You want to find all files in a directory that share the same inode number (hard links). Which command pipeline helps you identify these files?

hard

A. find . -type l

B. ls -i | sort | uniq -d

C. ls -l | grep '^d'

D. ls -i | cut -d' ' -f1 | sort | uniq -d

Solution

1. Step 1: Extract inode numbers from ls -i output

   The inode number is the first field in ls -i output, so use cut -d' ' -f1 to get it.

2. Step 2: Find duplicate inode numbers

   Sorting and using uniq -d lists inode numbers that appear more than once, indicating hard links.

3. Final Answer:

   ls -i | cut -d' ' -f1 | sort | uniq -d -> Option D

4. Quick Check:

   Duplicate inodes = hard links [OK]

Hint: Extract inode field then find duplicates [OK]

Common Mistakes:

• Using uniq -d without extracting inode field
• Confusing symbolic links with hard links
• Using find for symbolic links instead