Inodes concept in Linux CLI - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What does the command ls -i show?

You run ls -i in a directory. What is the output showing before each filename?

Linux CLI

ls -i

A The inode number of each file

B The file size in bytes

C The file permissions

D The last modification date

💡 Hint

Think about what uniquely identifies a file on disk besides its name.

The ls -i command shows the inode number, which is a unique identifier for each file in the filesystem.

💻 Command Output

intermediate

What happens when two filenames share the same inode number?

You find two files in the same directory with the same inode number using ls -i. What does this mean?

Linux CLI

ls -i

A They are duplicate files with different content

B They are hard links pointing to the same file content

C They are symbolic links to different files

D They are files with the same name but different extensions

💡 Hint

Inodes identify file data, not just names.

Files sharing the same inode number are hard links, meaning they point to the same data on disk.

📝 Syntax

advanced

Which command shows the inode number and file type in a long listing?

Choose the command that correctly lists files with inode numbers and file types.

A ls -li

B ls -iF

C ls -lF

D ls -l -i -F

💡 Hint

Combine options to get inode, long listing, and file type.

The command ls -l -i -F shows inode numbers (-i), long listing (-l), and file type indicators (-F).

🔧 Debug

advanced

Why does deleting a file not free disk space immediately?

You delete a file but disk space does not increase. What inode-related reason explains this?

A The file has other hard links still pointing to the inode

B The inode number is corrupted and not freed

C The file is a symbolic link and not the actual data

D The file permissions prevent freeing the inode

💡 Hint

Think about how many names can point to the same inode.

If other hard links exist, the inode and data remain until all links are removed.

🧠 Conceptual

expert

How does the inode structure help the filesystem manage files efficiently?

Select the best explanation of how inodes contribute to filesystem efficiency.

A Inodes contain the full file path, so the system can find files without directory lookups

B Inodes compress file data to save disk space and speed up access

C Inodes store metadata separately from filenames, allowing multiple names to share data and quick access to file info

D Inodes encrypt file contents to protect data security

💡 Hint

Think about what inodes store and how filenames relate to them.

Inodes hold file metadata and point to data blocks, enabling multiple filenames (hard links) to share the same data and fast metadata access.

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