Lab 1 - Red Hat Summit
Lab 1 - Red Hat Summit Lab 1 - Red Hat Summit
Lab 1 : Part 2 – Analyzing lvresize[root]# lvresize -L 20M /dev/vg_summit/lab1Extending logical volume lab1 to 20.00 MiBLogical volume lab1 successfully resizedSpecify absolute new size as 20MB
Lab 1 : Part 2 – Analyzing resize2fs[root]# resize2fs /dev/vg_summit/lab1resize2fs 1.41.12 (17-May-2010)Filesystem at /dev/vg_summit/lab1 is mounted on /mnt/lab1; on-line resizingrequiredold desc_blocks = 1, new_desc_blocks = 1Performing an on-line resize of /dev/vg_summit/lab1 to 20480 (1k) blocks.The filesystem on /dev/vg_summit/lab1 is now 20480 blocks long.[root]# df -h /mnt/lab1FilesystemSize Used Avail Use% Mounted on/dev/mapper/vg_summit-lab120M 1.2M 18M 6% /mnt/lab1Size is now 20MB[root]# lvs -o lv_name,lv_size,lv_attr,segtype,devices vg_summit/lab1LV LSize Attr Type Deviceslab1 20.00m -wi-ao linear /dev/vdb1(0)vdb1 still had space, soresize did not use vdc1
- Page 2 and 3: Fundamentals of LVM (LAB)Christoph
- Page 4 and 5: Quick SurveyAudience ProfileSystem
- Page 6 and 7: Quick SurveyBASH Skills Testls /dev
- Page 8 and 9: Why use Logical Volume Management?
- Page 10 and 11: The LVM CLI ToolboxPhysical Volumes
- Page 12 and 13: Mapping Linear Logical Extents (LE)
- Page 14 and 15: Lab 1 : Part 1 - Analyzing pvcreate
- Page 16 and 17: Lab 1 : Part 1 - Analyzing lvcreate
- Page 18 and 19: Lab 1 : Part 1 - Analyzing mount[ro
- Page 20 and 21: Lab 1 : Part 2 - Resize a Filesyste
- Page 24 and 25: Lab 1 : Part 3 - Resize a Filesyste
- Page 26 and 27: Lab 1 : Part 3 - Analyzing resize2f
- Page 28 and 29: Logical Volume ManagementStriping a
- Page 30 and 31: Lab 2 : Part 1 - Create a Striped L
- Page 32 and 33: Lab 2 : Part 1 - Analyzing lvcreate
- Page 34 and 35: Lab 2 : Part 2 - Resize a Striped L
- Page 36 and 37: Lab 2 : Part 2 - Analyzing lvresize
- Page 38 and 39: LVM Mirrors●●●Summary:●LVM
- Page 40 and 41: Lab 3 : Part 1 - Analyzing lvcreate
- Page 42 and 43: Lab 3 : Part 3 - Upconvert a Mirror
- Page 44 and 45: LVM Procedure - Mirror Split●●
- Page 46 and 47: Lab 3 : Part 3 - Analyzing lvconver
- Page 48 and 49: Logical Volume ManagementRAID
- Page 50 and 51: Architectural Overview (Current)Use
- Page 52 and 53: Lab 4 - Create a RAID5 LVlvcreate
- Page 54 and 55: LVM RAID 1 - Converting a Mirror to
- Page 56 and 57: Lab 5 - Analyzing lvconvert[root@bp
- Page 58 and 59: Lab 5 - BONUS * Analyzing the renam
- Page 60 and 61: LVM Snapshot●●●Summary:●Qui
- Page 62 and 63: Lab 6 - Analyzing lvcreate[root]# l
- Page 64 and 65: Lab 6 - Analyzing the filesystems[r
- Page 66 and 67: Lab 7 : Merge LV to Previous Stateu
- Page 68 and 69: Lab 7 - Analyzing the filesystems[r
- Page 70 and 71: Lab 8 - Create a sparse logical vol
<strong>Lab</strong> 1 : Part 2 – Analyzing resize2fs[root]# resize2fs /dev/vg_summit/lab1resize2fs 1.41.12 (17-May-2010)Filesystem at /dev/vg_summit/lab1 is mounted on /mnt/lab1; on-line resizingrequiredold desc_blocks = 1, new_desc_blocks = 1Performing an on-line resize of /dev/vg_summit/lab1 to 20480 (1k) blocks.The filesystem on /dev/vg_summit/lab1 is now 20480 blocks long.[root]# df -h /mnt/lab1FilesystemSize Used Avail Use% Mounted on/dev/mapper/vg_summit-lab120M 1.2M 18M 6% /mnt/lab1Size is now 20MB[root]# lvs -o lv_name,lv_size,lv_attr,segtype,devices vg_summit/lab1LV LSize Attr Type Deviceslab1 20.00m -wi-ao linear /dev/vdb1(0)vdb1 still had space, soresize did not use vdc1