{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}= State when Storage Setup (prior to starting Lab 4 ) =

At this point, having completed [[OPS235 Lab 3|Lab 3]] you should have <u>roughly</u> the following disk storage setup:<br />('''Note:''' These results are output from the '''vgs''', '''lvs''', and '''pvs''' commands within each virtual machine. You will be using these commands in the following lab investigations)<br /><br />

* '''fedora1'''

* '''fedora2'''

vg_fedora2 1 3 0 wz--n- 914.80G 34.95G07G

lv_home vg_fedora2 -wi-ao 1000 1.00M 95G lv_root vg_fedora2 -wi-ao 37.91G 81G

/dev/vda2 vg_fedora2 lvm2 a- 914.80G 34.95G07G

* '''fedora3'''

* host '''f17host (i.e. "disk pack")'''

= Logical Volume Management (Continued) =

{{Admon/note|Recovering VMs|'''Most of these investigations will take place in you virtual machines. ''' If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your virtual machines in Lab 3, and you can '''restore them if something goes wrong'''.}}

'''Please read this page to get an overview of LVM:'''<br /><br />('''Note:''' It is recommended to return to this guide as a reference when performing the next several investigations).<br /><br />

== Investigation 21: How are LVMs are managed from the command line? using Command-Line Tools ==# You are going to repeat the same LVM management operations (as your did with the ''fedora2'Repeat the operations from Investigation 1' VM in '''lab3'''), but you will using command-line tools in the virtual machine ''fedora3'fedora 3''' (VM. Since the fedora3 VM only operates in command-line tools only)mode, you will need to refer to the '''"Logical Volume Management"''' link above. # Write down the exact commands used at each step, and record appropriate command output:'''## Determine the current LVM configuration using the <code>pvs</code>, <code>vgs</code>, and <code>lvs</code> command.## Grow the home filesystem to 2G using the command <code>lvextend</code> and <code>resize2fs</code>.## Create a new 2G LV containing an ext4 filesystem and mount it at /archive (use <code>lvcreate</code>, <code>mkfs</code>, <code>mount</code>, edit the file <code>/etc/fstab</code>, and then reboot to confirm automatic mount).## Copy the contents of <code>/etc</code> into <code>/archive</code>.## Shrink <code>lv_archive</code> to 1G (use <code>umount</code>, <code>resize2fs</code>, <code>lvreduce</code>, <code>resize2fs</code>, and <code>mount</code>)

== Investigation 32: How can a PV be added to an existing VG? =='''Add an additional 2 GB virtual disk to your ''<u>fedora1</u>'' system, and use it as an additional physical volume:'''

# Click ''+ Add Hardware''button at the bottom left-hand corner.# In the ''Adding Virtual Hardwarenew virtual hardware'' window that appears, select a Hardware Type of ''"storage"'' and click ''"Forward"''.# Select ''File (Disk Image)'' for the Make certain option "Managed or other existing storage space" is selected. Click on the ''Browse'' button near the ''Location'' field, add a new volume (which creates a new file in <code>/var/libvirt/images</code>), then click on ''New Volume''.# Give the new virtual disk file a name of <code>fedora1b</code>, a format of ''raw'', with a ''Max Capacity'' and ''Allocation'' of 2000 MB. Click ''Finish''.# Select the new virtual disk file ''fedora1b.img'' and click ''Choose Volume''.

# Finish creating the new virtual diskby clicking ''Forward'' and then ''Finish''.

# Record the size of the volume group and the amount of free space(Hint: use a command that you learned in a previous lab).# Partition /dev/vdb with a single partion partition that fills the whole disk.

{{Admon/tip|SELinux relabelling may be required|Your system may report that the files are not present in the new /home filesystem when they are clearly there. This is due to the Security-Enhanced Linux system (SELinux) preventing access to the files, because the files were tampered with (moved) and are no longer recognized as home directory content. You can fix this problem by restoring the file context labels so that SELinux accepts the files as valid home directory content: <code>restorecon -r /home</code>}} == Investigation 43: How can I use LVM to manage storage on my disk pack? =='''On your host <u>f17host</u> (i.e. "disk pack"), using your choice of the GUI and/or command-line tools:'''

== Investigation 84: The /etc/passwd file ==

== Investigation 95: Adding users ==

{{Admon/note|Use fedora1f17host|Perform these steps in the '''fedora1f17host''' system. Due to a configuration issue, these steps may not work normally in the fedora1 virtual machinehost (previous versions of this lab used fedora1 for this investigation).}}

== Investigation 106: Managing Groups ==

== Investigation 117: Deleting users ==

# Check the contents of the /etc/group directoryfile. What do you notice?

 == Investigation 128: Modifying users ==

<!-- == Investigation 13: Security Tip: Removing Unnecessary Users and Groups ==

#* uucp -->

{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines. Remember to also make a backup of the new second virtual disk drive on ''fedora1''-- you now have two virtual disks on ''fedora1'', and therefore two image files, and therefore will need two backup files.}}

# Larger <code>/home</code> on '''fedora2''' and '''fedora3'''.!-- # Unnecessary accounts and groups have been removed on '''fedora1'''.-->

# List contents of '''nled/etc/group''' installed on the host file (disk pack - main systemops235 group).# Answer to this question: #* What is the license List contents of the '''nautilus/etc/passwd''' package?file (created accounts).

# What did you have to do in order to move is the home directories onto a new filesystem? Whypurpose of <code>/etc/shadow</code>?