Project $5-5$

ESTIMATED TIME: $20$ minutes

OBJECTIVE: Troubleshoot filesystems.

DESCRIPTION: In this hands$-$on project, you view disk usage and check filesystems for errors.

$1$

Switch to a command$-$line terminal $($tty$5)$ by pressing Ctrl$+$Alt$+$F$5$ and log in to the terminal using the user name of root and the password of LINUXrocks!.

$2$

At the command prompt, type df $-$hT and press Enter. What non$-$virtual filesystems are displayed?

$3$

At the command prompt, type df $-$i and press Enter. Note how many inodes are available for use by filesystem.

$4$

At the command prompt, type fsck $/$dev$/$vg$00/$newdata and press Enter. What error message do you receive and why?

$5$

At the command prompt, type umount $/$newdata and press Enter. Next, type fsck $/$dev$/$vg$00/$newdata and press Enter. How long did the filesystem check take and why?

$6$

At the command prompt, type fsck $$f $/$dev$/$vg$00/$newdata and press Enter. How long did the filesystem check take and why?

$7$

At the command prompt, type e$2$fsck $$c $/$dev$/$vg$00/$newdata and press Enter. What does this command do$?$

$8$

At the command prompt, type tune$2$fs $$i $0/$dev$/$vg$00/$newdata and press Enter to change the interval for forced checks such that they are avoided. Is this a good idea for the ext$4$ filesystem? Why?

$9$

At the command prompt, type mount $/$dev$/$vg$00/$newdata and press Enter. Next, type the df $-$hT command and press Enter to verify that the filesystem was mounted correctly. Why did the mount command work even though you didn$$t specify the mount point directory?

$10$

Type exit and press Enter to log out of your shell.