Skip to main content

Section 5.4 File System Implementation: vsfs

We now start looking at how a file system is organized on a disk. Start by reading the Files System Implementation chapter, sections 40.1 and 40.2, and the preamble. These introduce the basic structure of a simple file system and discuss the key aspects of it.

Practice 5.4.1.

Practice 5.4.2.

    True or False: The space allocated to the inode list determines how many files the system can hold.
  • True.

  • False.

Read section 40.3 about the inode structure.

Practice 5.4.3.

Which of the following is information that we can find in an inode?
  • The permissions on the file.
  • The name of the user who owns the file.
  • How many disk blocks the file takes.
  • Where on disk the file contents reside.
  • Which directory the file is in.
  • A pointer to the next inode on the list.

Practice 5.4.4.

What is the purpose of the multi-level index?
  • To allow the storage of large files that occupy too many blocks on disk.
  • To allow faster access to the file contents.
  • To have one inode store information about multiple files.
Read section 40.4 about how directories are organized.

Practice 5.4.5.

    True or False: A directory that contains no files will have no directory entries.
  • True.

  • False.

Practice 5.4.6.

    True or False: The contents of a directory are stored in its inode.
  • True.

  • False.

Read sections 40.5, 40.6.

Practice 5.4.7.

    True or False: The number of I/O operations needed to read a file from disk depends on both the size of the file as well as the depth of the directory level where the file is located.
  • True.

  • False.

Practice 5.4.8.

    True or False: Reading a file also includes performing a write request on the file’s inode.
  • True.

  • False.

Skim through sections 40.7, 40.8.
You have attempted of activities on this page.