Open main menu

CDOT Wiki β

Changes

OPS235 Lab 3 - Fedora17

3,811 bytes removed, 11:46, 27 January 2012
no edit summary
'''Answer the Investigation 3 observations / questions in your lab log book.'''
 
== Investigation 4: How to Add a PV 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:'''
 
# Start <code>'''virt-manager'''</code>.
# Shutdown ''fedora1'' if it is running.
# Open the console window for ''fedora1''.
# Select the menu option '''View'''>'''Details'''.
# Click '''''Add Hardware''''' button at the bottom left-hand corner.
# In the ''Adding new virtual hardware'' window that appears, select a Hardware Type of ''"'''storage'''"'' and click ''"'''Forward'''"''.
# Make certain option "Managed or other existing storage" is selected. Click on the '''''Browse''''' button, 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'''''.
# Select a device type of '''''Virtio Disk'''''.
# Finish creating the new virtual disk by clicking '''''Forward''''' and then '''''Finish'''''.
# Boot the system. You should now have both <code>/dev/vda</code> and <code>/dev/vdb</code>.
# Record the size of the volume group and the amount of free space <span class="plainlinks">[http://www.inleds.com/products/?cid=2<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> led downlight singapore</span>](Hint: use a command that you learned in a previous lab).
# Partition /dev/vdb with a single partition that fills the whole disk.
# Check the messages printed when <code>fdisk</code> exits -- you may need to reboot the system in order for the new partition table to take effect.
# Run this command to format the physical volume: <code>pvcreate /dev/''vdb1''</code>
# Add the new physical volume to the existing volume group: <code>vgextend ''nameOfVolumeGroup'' /dev/vdb1</code>
# Verify that the volume group is larger and has more free space.
 
{{Admon/note|Think!|The next part of this investigation is designed to encourage the student to research, think, and use some creativity in working around obstacles in order to solve a task. Research methods can include the Internet searches, etc...}}
'''Using that additional space, create a separate filesystem for <code>/home</code>:'''
# Create the logical volume <code>lv_home</code> (1G ext4)
# Find a way to move the contents of <code>/home</code> onto it.
# Change your system configuration so that the new filesystem is mounted on <code>/home</code> from now on.
 
{{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>}}
 
'''Answer the Investigation 4 observations / questions in your lab log book.'''
 
 
== Investigation 5: How can I use LVM to manage storage on my f16host disk pack? ==
'''On your <u>f16host</u> (i.e. "disk pack"), using your choice of the GUI and/or command-line tools:'''
# Create a new logical partition ('''NOT a logical volume!''') - minimum 5G, leaving at least 10G free space in the extended partition.
# Add that partition as a PV into the existing VG (using the commands you used in the previous investigation).
# Grow the root filesystem to fill the available space.
 
'''Answer the Investigation 5 observations / questions in your lab log book.'''
= Software Package Management =
13,420
edits