RH134 - ch14s03

Bookmark this page

Lab: Configuring and Managing File Systems and Storage

In this review, you will create an LVM logical volume, mount a network file system, create a swap partition that is automatically activated at boot, configure temporary unused files to be cleaned from the system, and use ACLs to protect a directory.

Outcomes

You should be able to:

Create an LVM logical volume.
Mount a network file system.
Create a swap partition that is automatically activated at boot.
Configure temporary unused files to be cleaned from the system.
Use ACLs to protect a directory.

Copy any files or work you wish to keep to other systems before resetting. Reset the workstation, servera, and serverb systems now, unless you just finished resetting them at the end of the last exercise.

On workstation, run lab rhcsa-compreview2 start to start the comprehensive review. This script creates the necessary files to set up the environment correctly.

[student@workstation ~]$ lab rhcsa-compreview2 start

Instructions

Perform the following tasks on serverb to complete the comprehensive review.

Configure a new 1 GiB logical volume called vol_home in a new 2 GiB volume group called extra_storage. Use the unpartitioned /dev/vdb disk to create partitions.
The logical volume vol_home should be formatted with the XFS file-system type, and mounted persistently on /home-directories.
Ensure that the network file system called /share is persistently mounted on /local-share across reboot. The NFS server servera.lab.example.com exports the /share network file system. The NFS export path is servera.lab.example.com:/share.
Create a new 512 MiB partition on the /dev/vdc disk to be used as swap space. This swap space must be automatically activated at boot.
Create a new group called production. Create the production1, production2, production3, and production4 users. Ensure that they use the new group called production as their supplementary group.
Configure your system so that it uses a new directory called /run/volatile to store temporary files. Files in this directory should be subject to time based cleanup if they are not accessed for more than 30 seconds. The octal permissions for the directory must be 0700. Make sure that you use the /etc/tmpfiles.d/volatile.conf file to configure the time based cleanup for the files in /run/volatile.
Create the new directory called /webcontent. Both the owner and group of the directory should be root. The group members of production should be able to read and write to this directory. The production1 user should only be able to read this directory. These permissions should apply to all new files and directories created under the /webcontent directory.

From workstation, open an SSH session to serverb as student.
[student@workstation ~]$ ssh student@serverb ...output omitted...

Switch to the root user.

[student@serverb ~]$ sudo -i
[sudo] password for student: student
[root@serverb ~]#

Create a 2 GiB partition on /dev/vdb.

[root@serverb ~]# parted /dev/vdb mklabel msdos
[root@serverb ~]# parted /dev/vdb mkpart primary 1GiB 3GiB
[root@serverb ~]# parted /dev/vdb set 1 lvm on

Create a logical volume called vol_home using the 2 GiB partition you created on /dev/vdb. Name the volume group extra_storage.
Declare the /dev/vdb1 block device as a physical volume.
[root@serverb ~]# pvcreate /dev/vdb1 ...output omitted...
Create the extra_storage volume group using /dev/vdb1.
[root@serverb ~]# vgcreate extra_storage /dev/vdb1 ...output omitted...
Create a 1 GiB logical volume named vol_home.
[root@serverb ~]# lvcreate -L 1GiB -n vol_home extra_storage ...output omitted...

Format vol_home with the XFS file-system type, and mount it on /home-directories.

Create a directory called /home-directories.
```
[root@serverb ~]# mkdir /home-directories
```

Format /dev/extra_storage/vol_home with the XFS file-system type.

[root@serverb ~]# mkfs -t xfs /dev/extra_storage/vol_home
...output omitted...

Persistently mount /dev/extra_storage/vol_home on /home-directories. Use the structure's UUID when creating the entry in /etc/fstab.

[root@serverb ~]# lsblk -o UUID /dev/extra_storage/vol_home
UUID
988cf149-0667-4733-abca-f80c6ec50ab6
[root@serverb ~]# echo "UUID=988c...0ab6 /home-directories \
xfs defaults 0 0" >> /etc/fstab
[root@serverb ~]# mount -a

Ensure that the network file system called /share is persistently mounted on /local-share across reboot. The NFS server servera.lab.example.com exports the /share network file system. The NFS export path is servera.lab.example.com:/share.
Create the /local-share directory.
[root@serverb ~]# mkdir /local-share
Append the appropriate entry to /etc/fstab so that the network file system available at servera.lab.example.com:/share is persistently mounted on /local-share across reboot.
[root@serverb ~]# echo "servera.lab.example.com:/share /local-share \ nfs rw,sync 0 0" >> /etc/fstab
Mount the network file system on /local-share based on the entry in /etc/fstab.
[root@serverb ~]# mount /local-share

Create a new 512 MiB partition on the /dev/vdc disk to be used as swap space. This swap space must be automatically activated at boot time.

Create a 512 MiB partition on /dev/vdc.

[root@serverb ~]# parted /dev/vdc mklabel msdos
[root@serverb ~]# parted /dev/vdc mkpart primary linux-swap 1MiB 513MiB

Make the swap space on /dev/vdc1.

[root@serverb ~]# mkswap /dev/vdc1
...output omitted...

Activate the swap space so that it persists across reboot. Use the structure's UUID when creating the entry in /etc/fstab.

[root@serverb ~]# lsblk -o UUID /dev/vdc1
UUID
cc18ccb6-bd29-48a5-8554-546bf3471b69
[root@serverb ~]# echo "UUID=cc18...1b69 swap \
swap defaults 0 0" >> /etc/fstab
[root@serverb ~]# swapon -a

Create the production1, production2, production3, and production4 users. Ensure that they use the new group called production as their supplementary group.
[root@serverb ~]# groupadd production [root@serverb ~]# for i in 1 2 3 4; do useradd -G production production$i; done
Configure your system so that it uses a new directory called /run/volatile to store temporary files. Files in this directory should be subject to time based cleanup if they are not accessed for more than 30 seconds. The octal permissions for the directory must be 0700. Make sure that you use the /etc/tmpfiles.d/volatile.conf file to configure the time based cleanup for the files in /run/volatile.
Create a file called /etc/tmpfiles.d/volatile.conf with the following content.
d /run/volatile 0700 root root 30s
Use the systemd-tmpfiles --create command to create the /run/volatile directory if it does not exist.
[root@servera ~]# systemd-tmpfiles --create /etc/tmpfiles.d/volatile.conf
Create a new directory called /webcontent. Both the owner and group owner of the directory should be root. The group members of production should be able to read and write to this directory. The production1 user should only be able to read this directory. These permissions should apply to all new files and directories created under the /webcontent directory.
Create the /webcontent directory.
[root@serverb ~]# mkdir /webcontent
Use setfacl to configure permissions on /webcontent so that the group members of production have both read and write permissions to it, with the exception of the production1 user, who should only be granted read permission.
[root@serverb ~]# setfacl -m u:production1:rx /webcontent [root@serverb ~]# setfacl -m g:production:rwx /webcontent
Use setfacl to set the default permissions on /webcontent so that the permissions you applied in the preceding step also apply to all new files and directories created under the /webcontent directory.
[root@serverb ~]# setfacl -m d:u:production1:rx /webcontent [root@serverb ~]# setfacl -m d:g:production:rwx /webcontent
Exit the root user's shell.
[root@serverb ~]# exit logout
Log off from serverb.
[student@serverb ~]$ exit logout Connection to serverb closed.

Evaluation

On workstation, run the lab rhcsa-compreview2 grade script to confirm success on this exercise. Correct any reported failures and rerun the script until successful.

[student@workstation ~]$ lab rhcsa-compreview2 grade

Finish

On workstation, run lab rhcsa-compreview2 finish to complete this exercise. This script deletes the files and resources created throughout the exercise and ensures that the environment is clean.

[student@workstation ~]$ lab rhcsa-compreview2 finish

This concludes the comprehensive review.

Discuss Red Hat System Administration II

Go to community

Is It possible to reset root password when the system is on multi-user.target?

jennifer1987

27 lip 2023

Hi thereWell, i have a question, Is It possible to reset root password when the system is on multi-user.target? I was not be able to found a foro o some information related with this and another question that I have, If the grub menu dont show up, is it posible to reset the root password?

991

Red Hat System Administration II (RH134)

Haley_Ruccio

21 lip 2023

Build the skills to perform the key tasks needed to become a full-time Linux administratorRed Hat System Administration II (RH134) is the second part of the RHCSA training track for IT professionals who have already attended Red Hat System Administration I. The course goes deeper into core Linux system administration skills in storage configuration and management, installation and deployment of Red Hat Enterprise Linux, management of security features such as SELinux, control of recurring system tasks, management of the boot process and troubleshooting, basic system tuning, and command-line automation and productivity. This course assumes that students have attended Red Hat System Administration I (RH124).Experienced Linux administrators who seek rapid preparation for the RHCSA certification should instead start with RHCSA Rapid Track (RH199).This course is based on Red Hat Enterprise Linux 9.0.Course summaryInstall Red Hat Enterprise Linux using scalable methodsAccess security files, file systems, and networksExecute shell scripting and automation techniquesManage storage devices, logical volumes, and file systemsManage security and system accessControl the boot process and system servicesRun containersAudience for this courseThis course is geared toward Windows system administrators, network administrators, and other system administrators who are interested in supplementing current skills or backstopping other team members, in addition to Linux system administrators who are responsible for these tasks:Configuring, installing, upgrading, and maintaining Linux systems using established standards and proceduresProviding operational supportManaging systems for monitoring system performance and availabilityWriting and deploying scripts for task automation and system administrationRecommended trainingSuccessful completion of Red Hat System Administration I (RH124) is recommended.Experienced Linux administrators seeking to accelerate their path toward becoming a Red Hat Certified System Administrator should start with the RHCSA Rapid Track course (RH199).Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technology requirements.This course is not designed for bring your own device (BYOD).Internet access is not required, but is recommended to allow students to research and access Red Hat online resources.

Welcome to the Red Hat System Administration II (RH134) group in the Red Hat Learning Community!

Deanna

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat System Administration II! To gain the most value from this group - click the "Join Group" button in the upper right hand corner.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH134.Read more about Red Hat System Administration II here.

417

Revision: rh134-8.2-f0a9756