From 2c9b02f0b24507013be2b0741527a6bcf088a53c Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Wed, 2 Aug 2006 18:49:40 +0000 Subject: Update section on partitioning using LVM to reflect recent changes --- en/using-d-i/components.xml | 2 +- en/using-d-i/modules/lvmcfg.xml | 58 ------------------- en/using-d-i/modules/partman-lvm.xml | 104 +++++++++++++++++++++++++++++++++++ 3 files changed, 105 insertions(+), 59 deletions(-) delete mode 100644 en/using-d-i/modules/lvmcfg.xml create mode 100644 en/using-d-i/modules/partman-lvm.xml (limited to 'en') diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml index 453bb9388..0d0570fd2 100644 --- a/en/using-d-i/components.xml +++ b/en/using-d-i/components.xml @@ -72,8 +72,8 @@ like LVM or RAID devices. &module-autopartkit.xml; &module-partitioner.xml; &module-partconf.xml; -&module-lvmcfg.xml; &module-mdcfg.xml; +&module-partman-lvm.xml; &module-partman-crypto.xml; diff --git a/en/using-d-i/modules/lvmcfg.xml b/en/using-d-i/modules/lvmcfg.xml deleted file mode 100644 index 6d7fae931..000000000 --- a/en/using-d-i/modules/lvmcfg.xml +++ /dev/null @@ -1,58 +0,0 @@ - - - - - Configuring Logical Volume Manager (LVM) - - -If you are working with computers at the level of system administrator -or advanced user, you have surely seen the situation -where some disk partition (usually the most important one) was short on -space, while some other partition was grossly underused and you had to -manage this situation with moving stuff around, symlinking, etc. - - - -To avoid the described situation you can use Logical Volume Manager -(LVM). Simply said, with LVM you can combine your partitions -(physical volumes in LVM lingo) to form -a virtual disc (so called volume group), which -can then be divided into virtual partitions (logical -volumes). The point is that logical volumes (and of course -underlying volume groups) can span across several physical discs. - - - -Now when you realize you need more space for your old 160GB -/home partition, you can simply add a new 300GB -disc to the computer, join it with your existing volume group and then -resize the logical volume which holds your /home -filesystem and voila — your users have some room again on their -renewed 460GB partition. This example is of course a bit -oversimplified. If you haven't read it yet, you should consult the -LVM HOWTO. - - - -LVM setup in &d-i; is quite simple. At first, you have to mark your -partitions to be used as physical volumes for LVM. (This is done in -partman in the Partition -settings menu where you should select -Use as: physical volume for -LVM .) Then start the -lvmcfg module (either directly from -partman or from the &d-i;'s main menu) and combine -physical volumes to volume group(s) under the Modify -volume groups (VG) menu. After that, you should create -logical volumes on the top of volume groups from the menu -Modify logical volumes (LV). - - - -After returning from lvmcfg back to -partman, you will see any created logical volumes -in the same way as ordinary partitions (and you should treat them like -that). - - - diff --git a/en/using-d-i/modules/partman-lvm.xml b/en/using-d-i/modules/partman-lvm.xml new file mode 100644 index 000000000..4feadedc1 --- /dev/null +++ b/en/using-d-i/modules/partman-lvm.xml @@ -0,0 +1,104 @@ + + + + + Configuring the Logical Volume Manager (LVM) + + +If you are working with computers at the level of system administrator +or advanced user, you have surely seen the situation +where some disk partition (usually the most important one) was short on +space, while some other partition was grossly underused and you had to +manage this situation with moving stuff around, symlinking, etc. + + + +To avoid the described situation you can use Logical Volume Manager +(LVM). Simply said, with LVM you can combine your partitions +(physical volumes in LVM lingo) to form +a virtual disk (so called volume group), which +can then be divided into virtual partitions (logical +volumes). The point is that logical volumes (and of course +underlying volume groups) can span across several physical disks. + + + +Now when you realize you need more space for your old 160GB +/home partition, you can simply add a new 300GB +disk to the computer, join it with your existing volume group and then +resize the logical volume which holds your /home +filesystem and voila — your users have some room again on their +renewed 460GB partition. This example is of course a bit +oversimplified. If you haven't read it yet, you should consult the +LVM HOWTO. + + + +LVM setup in &d-i; is quite simple and completely supported inside +partman. First, you have to mark the partition(s) +to be used as physical volumes for LVM. This is done in the +Partition settings menu where you should select + Use as: physical volume +for LVM . + + + +When you return to the main partman screen, you will see +a new option Configure the Logical Volume Manager. +When you select that, you will first be asked to confirm pending changes to +the partition table (if any) and after that the LVM configuration menu will +be shown. Above the menu a summary of the LVM configuration is shown. The +menu itself is context sensitive and only shows valid actions. The possible +actions are: + + + + Display configuration details: + shows LVM device structure, names and sizes of logical volumes and more + + + Create volume group + + + Create logical volume + + + Delete volume group + + + Delete logical volume + + + Extend volume group + + + Reduce volume group + + + Finish: + return to the main partman screen + + + + + +Use the options in that menu to first create a volume group and then create +your logical volumes inside it. + + + + +You can also use this menu to delete an existing LVM configuration from +your hard disk before choosing Guided partitioning using LVM. +Guided partitioning using LVM is not possible if there already are volume +groups defined, but by removing them you can get a clean start. + + + + +After you return to the main partman screen, any created +logical volumes will be displayed in the same way as ordinary partitions +(and you should treat them as such). + + + -- cgit v1.2.3