<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
  <!ENTITY kappname "&kvpm;">
  <!ENTITY kvpm "<application>kvpm</application>">
  <!ENTITY Benjamin.Scott "<personname><firstname>Benjamin</firstname><surname>Scott</surname></personname>">
  <!ENTITY benscott.email "<email>benscott@nwlink.com</email>">
  <!ENTITY % English "INCLUDE">
  <!ENTITY % addindex "IGNORE">
]>

<book lang="&language;">

<bookinfo>
<title>The &kvpm; Handbook</title>

<authorgroup>
<author>
<firstname>Benjamin</firstname>
<othername></othername>
<surname>Scott</surname>
<affiliation>
<address>&benscott.email;</address>
</affiliation>
</author>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
</authorgroup>

<legalnotice>&FDLNotice;</legalnotice>

<date>2011-12-13</date>
<releaseinfo>0.02.00</releaseinfo>

<abstract>
<para>
&kvpm; is an application for the &kde; environment that lets a system
administrator modify partitions on disk drives or logical volumes
created by lvm2.
</para>
</abstract>


<keywordset>
<keyword>KDE</keyword>
<keyword>kvpm</keyword>
<keyword>lvm2</keyword>
</keywordset>

</bookinfo>

<chapter id="introduction">
<title>Introduction</title>

<para>The KDE Logical Volume and Partition Manager can manipulate logical
volumes, physical volumes and volume groups as defined by the Linux Logical
Volume Manager, LVM2. It can also write a partition table or modify an existing
one to add, delete or resize partitions. This guide assumes a basic knowledge of
LVM2 operation and disk partitioning. The following is a good starting point for
learning the basics of LVM2: <ulink url="http://tldp.org/HOWTO/LVM-HOWTO">http://tldp.org/HOWTO/LVM-HOWTO/</ulink></para>

<para>Currently most LVM functions are implemented by the standard lvm command
line programs. KDE dialog boxes are used to determine the parameters to pass the
program. If you are already using lvm on the command line the dialogues will
probably seem familiar. For example this is the dialog to change a logical
volume's attributes:

<screenshot>
<screeninfo>Logical volume change attributes dialog</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="lvchange.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>&kvpm; change attributes dialog</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

</para>
</chapter>

<chapter id="getting-started-kvpm">
<title>Getting Started</title>

<sect1 id="getting-started-kvpm-device">
<title>The <guilabel>Storage Devices</guilabel> Tab</title>

<para>When first started on a system with no volume groups the screen
will look something like this:</para>

<screenshot>
<screeninfo>This is a screenshot of &kvpm; when first started</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="main.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>&kvpm; main window</phrase>
	  </textobject>
	</mediaobject>
</screenshot>


<sect2 id="storage-device-tree">
<title>Storage Device Tree</title>

<para>The devices found are listed in the large tree list to the left. Clicking
  the &LMB; to select a device brings up additional information on the
  properties pane to the right. The colored bar across the top of the tab also
  gives a visual of the partitioning of the highlighted device. Clicking the
  &RMB; over the name of a device calls
  the <link linkend="storage-device-menu">context menu</link> of actions that
  can be taken on that device. Any action that can be called from the context
  menu can also be called from the toolbar by selecting the device desired with
  the &LMB; and then pressing a button on the toolbar</para>
</sect2>

<sect2 id="storage-device-bar">
<title>Storage Device Bar</title>
<para>The device represented by the colored bar across the top is the one
  currently selected in the device tree, as described above. Each partition is
  represented by a segment of the bar. Right-clicking on a segment or free space
  on the device will call a context menu of partitioning operations. The colors
  indicate either the filesystem type in use on the partition or the type of
  partition. By default the partition type determines color but it is a user
  configuration option. Clicking the &RMB; over a device or partition calls
  the <link linkend="storage-device-menu">context menu</link> of actions that
  can be taken on it.
</para>
</sect2>
</sect1>

<sect1 id="getting-started-kvpm-group">
<title>A Volume Group Tab</title>

<para>Below in an example of a volume group called  <quote>vg1.</quote>
If more than one group exists, additional tabs are used, one for each
group, with the group name on the tab.</para>

<screenshot>
<screeninfo>This is a screenshot of a typical volume group.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="typicalvg.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>a typical group</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<sect2 id="typical-volume-group-info">
<title>Volume Group Information Panel</title>

<para>Across the top of the window, below the toolbar, is an information panel
about the volume group as a whole.  It shows the size of the group, the amount
of space used up and how much is still left.  There are also entries for the
uuid, clustering status, default allocation policy, metadata areas, whether
resizing is allowed and the extent size.</para>
</sect2>

<sect2 id="typical-volume-group-colors">
<title>The Logical Volume Bar</title>

<para>Below the volume group information panel is a graphical representation of
the group in the form of a bar divided into segments. There are three logical
volumes in this group. Each volume is represented by a bar segment according to
its relative size and has a color representing the filesystem, if it has
one, or the type of logical volume, depending on the user's configuration
preference. The last segment of the bar is green and depicts the free space
remaining. Clicking the &RMB; on a segment of the bar calls the <link
linkend="logical-volume-menu">context menu</link> of actions that can be taken
on the logical volume that was clicked. The menu also has an entry for creating
new volumes.</para>
</sect2>

<sect2 id="typical-volume-group-vgtree">
<title>Logical Volume Tree</title>

<para>The large tree list at center left shows the logical volumes by name, along
with some information about them. Selecting a name in the list window shows
additional information about that volume in the pane on the right right. Here, the
volume lvol1 is selected. Clicking the &RMB; over the name of a volume calls the
<link linkend="logical-volume-menu">context menu</link> of actions that can be
taken on that logical volume. There is also an entry in the menu for creating
new volumes. Any action that can be called from the context menu can also be
called from the toolbar by selecting the volume desired with the &LMB; and then
pressing a button on the toolbar</para>

<para>Because volumes often have an underlying structure, such as segments or
mirror legs, the logical volumes are listed in tree form. Snapshots are also
grouped under their origin volume. Clicking on an item in the tree will expand
or collapse the branch if the item has more items under it.</para>
</sect2>

<sect2 id="typical-volume-group-pvtree">
<title>Physical Volume Information</title> <para>The last two panels at the
bottom deal with physical volumes. The left tree list shows the physical volumes
by name with basic information, while the right panel gives more detailed
information. Clicking the &RMB; on the name list brings up a context menu of
actions that can be taken on the physical volume.</para>
</sect2>
</sect1>

</chapter>

<chapter id="storage-devices">
<title>Storage Devices</title>

<sect1 id="storage-devices-intro">
<title>Working With Storage Devices</title>
<para>Nearly any action that can be taken on a device is done from the device
context menu, discussed next, or the equivalent tool bar. It has menu entries for
the creation, deletion, extension and reduction of partitions and a variety of
other changes that can be made to a device. There is also a sub-menu for
working with or writing filesystems on the device.</para>
</sect1>

<sect1 id="storage-device-menu">
<title>The Storage Device Context Menu</title>

<para>This is a pop-up menu activated with the &RMB;. See <link
linkend="storage-device-bar">The Storage Device Bar</link> and <link
linkend="storage-device-tree">The Storage Device Tree</link> for
information on calling this context menu.</para>

<caution><para>Partitioning is inherently dangerous. It is highly recommended
    that all data be backed up before making any changes to a device or its
    partitions.</para></caution>

<variablelist>
<varlistentry>
<term><menuchoice>
<guimenuitem>Create or remove a partition table</guimenuitem>
</menuchoice></term>
<listitem><para>Writes a new partition table to the device or erases an existing
    table. Both GUID (GPT) and traditional MS-DOS type tables are supported. Any
    partitions or data on the device will be permanently lost.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Delete disk partition</guimenuitem>
</menuchoice></term>
<listitem><para>Deletes a partition on the device. Any data on it will be
    lost permanently.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Add disk partition</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a new partition on the device.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Move or resize disk partition</guimenuitem>
</menuchoice></term>
<listitem><para>Move, grow or shrink an existing partition.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Change partition flags</guimenuitem>
</menuchoice></term>
<listitem><para>Changes flags, such as the boot flag.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Extend physical volume to fill device</guimenuitem>
</menuchoice></term>
<listitem><para>If the device or partition is larger than the physical volume
    thinks it is, this will extend the volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Create volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Create a new volume group using the selected device or
    partition.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Remove from volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Remove the device or partition from the its volume
    group.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Extend volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Add the device or partition to an existing volume
    group.</para></listitem>
</varlistentry>
</variablelist>

<sect2 id="storage-device-filesystems-menu">
<title>Filesystem Operations On Devices</title>

<para>The Filesystem operations sub-menu provides five common menu selections
    for working with a filesystem. Details are provided
    under <link linkend="filesystems-menu">Filesystem Operations</link>.</para>

</sect2>
</sect1>

<sect1 id="adding-partition">
<title>Adding a new partition</title>

<para>To add a new partition select <guimenuitem>Add disk
    partition</guimenuitem> from the <link linkend="storage-device-menu">storage
    device context menu</link> or the tool bar on the devices tab.</para>

<screenshot>
<screeninfo>This is a screenshot of a dialog for creating a new volume partition.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="addpart.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>add a disk partition</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<para>At the top is a graphic that represents the size and position of the new
    partition relative to the free space it is going into. The blue bar is the
    partition and the green is the left over space around it.</para>

<para>The combo box labeled <quote>Select type</quote> can be set to Primary,
    Logical or Extended if the partition table is MS-DOS. If it is a GUID
    partition table (GPT) only Primary is allowed and the combo box is
    disabled. The usual limits to MS-DOS partitions, such as only four primary
    partitions or three primary and one extended partition, also apply.</para>

<para>The size of the partition can be set with the upper slider or can be typed
    directly into the text box above it. A combo box next to the text box
    changes the input numerical value between megabytes, gigabytes and
    terabytes. Once the size is set it can be locked before setting the
    partition's starting position. By default the partition will be as large as
    the available free space.</para>

<para>By default the partition will start at the beginning of available free
    space on the device. By unchecking <guibutton>Lock partition
    start</guibutton> the partition can be placed anywhere in the free
    space. If the partition size is not locked changing the start may make the
    partition smaller. Conversely, making the partition larger after setting
    the start may move the start towards zero if the start is not locked. </para>

<para>Clicking <guibutton>Reset</guibutton> will make the partition as large as
    possible.</para>

</sect1>





<sect1 id="changing-partition">
<title>Changing an existing partition</title>

<para>To change a partition select <guimenuitem>Move or resize disk
    partition</guimenuitem> from the <link linkend="storage-device-menu">storage
    device context menu</link> or the tool bar on the devices tab.</para>

<screenshot>
<screeninfo>This is a screenshot of a dialog for creating a new volume partition.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="changepart.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>add a disk partition</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<para>At the top is a graphic that represents the size and position of the
    partition relative to any free space around it. The blue bar is the
    partition and the green is the available free space. The text below
    indicates the partition is going to be moved 512 megabytes towards the
    start of the disk and will be 512 megabytes larger.</para>

<para>The size of the partition can be set with the upper slider or can be typed
    directly into the text box above it. A combo box next to the text box
    changes the input numerical value between megabytes, gigabytes and
    terabytes. Once the size is set it can be locked before setting the
    partition's starting position.</para>

<para>By unchecking <guibutton>Lock partition start</guibutton> the partition
    can be placed anywhere in the free space. If the partition size is not
    locked changing the start may make the partition smaller. Conversely, making
    the partition larger after setting the start may move the start towards zero
    if the start is not locked. </para>

<para>Clicking <guibutton>Reset</guibutton> will reset the partition to its
    original size and starting point.</para>

<note><para>Not all filesystem types can grow or shrink so some operations may
    not be available.</para></note>

</sect1>
</chapter>

<chapter id="volume-group">
<title>Volume Groups</title>

<sect1 id="volume-group-intro">
<title>Working With Volume Groups</title>

<para>Most actions that can be taken on a Volume Group are done from the
<guimenu>Volume Groups</guimenu> menu discussed next. It has menu entries for
the creation, deletion, extension and reduction of Volume Groups and a variety
of other changes that can be made.</para>

<para>The <guimenu>Volume Groups</guimenu> Menu is located at the top of the
main program window.  Except for <guimenu>Create volume group</guimenu> all of
the menu choices act on the currently selected volume group tab. If the <guilabel>Storage
devices</guilabel> tab is selected, or there are no existing volume groups, 
only the <guimenu>Create volume group</guimenu> choice will be available.</para>

</sect1>

<sect1 id="menu-vgchange">
<title>The <guimenu>Volume Groups</guimenu> Menu</title>

<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Create volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Create a new volume group.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Delete volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Delete the volume group. A group must be empty before it may be deleted.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Rename volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Rename the volume group.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Remove missing physical volumes</guimenuitem>
</menuchoice></term>
<listitem><para>Remove any missing physical volumes. This may cause data loss, use with caution</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Extend volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Extend the volume group by adding new physical volumes.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Reduce volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Reduce the volume group by removing physical volumes.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Split volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Split the volume group into two groups.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Merge volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Merge the volume group with another.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Export volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Export the volume group.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Import volume group</guimenuitem>
</menuchoice></term>
<listitem><para>Import the volume group.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Volume Groups</guimenu>
<guimenuitem>Change volume group attributes</guimenuitem>
</menuchoice></term>
<listitem><para>Call a dialog that allows many group attributes to be modified.</para></listitem>
</varlistentry>
</variablelist>
</sect1>

<sect1 id="creating-group">
<title>Creating a Volume Group</title>

<para>To create a new volume group select <menuchoice><guimenu>Volume
Groups</guimenu><guimenuitem>Create Volume Group</guimenuitem></menuchoice>. A
dialog box will ask which devices to use, its name and other pertinent questions
about the new group. I have checked several devices and entered the name
MyVolumeGroup. After the dialog's <guibutton>OK</guibutton> button has been
pressed notice the new tab titled <guilabel>MyVolumeGroup</guilabel> is now
present on the main window.</para>

<screenshot>
<screeninfo>This is a screenshot of &kvpm; creating a new volume group.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="vg1.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>create a volume group</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<note><para>Because &kvpm; uses the lvm2app library to create volume groups, not
all options of the command <quote>lvcreate</quote> are available here yet. Some, such a
clustering, need to be selected from the <menuchoice><guimenu>Volume
Groups</guimenu><guimenuitem>Change volume group
attributes</guimenuitem></menuchoice> dialog discussed later.</para></note>
</sect1>

<sect1 id="volume-group-split">
<title>Splitting A Volume Group</title> <para> By selecting <menuchoice><guimenu>Volume
Groups</guimenu><guimenuitem>Split Volume Group</guimenuitem></menuchoice> a
volume group can be split into two groups.</para>

<screenshot>
<screeninfo>This is a screenshot of the volume group split dialog.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="vgsplit.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>split a volume group</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<para>The dialog has two views. One view shows which logical volumes will remain
  in the original group and those being moved to the new group. The other view
  shows the physical volumes that will be in each group. All volumes will start
  in the original group. By selecting a volume with the &LMB; and then
  pressing <guibutton>Add</guibutton> or <guibutton>Remove</guibutton> they may
  be moved as needed. The new group must be given a name, which can be entered
  at the top. Any physical volume that has a busy or mounted logical volume on
  it will be greyed out and moving it will be disabled.</para>

<note><para>Moving a volume between groups may cause other volumes to move as
  well. When a logical volume is moved it takes all of its physical volumes with
  it because they cannot be split across groups. That, in turn, may pull other
  volumes. In the same fashion, one volume that is mounted and can't be moved may
  cause others to become impossible to move.</para></note>
</sect1>

<sect1 id="volume-group-remove-missing">
<title>Remove Missing Physical Volumes</title>
<para> By selecting <menuchoice><guimenu>Volume
  Groups</guimenu><guimenuitem>Remove missing volumes</guimenuitem></menuchoice>
  a volume group with missing physical volumes, a failed disk drive for example,
  can have them permanently removed. This dialog has only two options, either
  all missing volumes will be removed or only those that were empty and
  unused. If removing all missing volumes is chosen and some of the missing
  volumes had logical volumes or thin pools on them then any unmirrored data
  they held will be permanently deleted.</para>

<warning><para>Removing missing volumes can result in data loss</para></warning>
</sect1>

<sect1 id="volume-group-changes">
<title>Changing a Volume Group</title> <para> By
selecting <menuchoice><guimenu>Volume Groups</guimenu><guimenuitem>Change Volume
Group Attributes</guimenuitem></menuchoice> a wide variety of changes can be
made to the group.</para>

<screenshot>
<screeninfo>This is a screenshot of the volume group change dialog.</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="vgchange.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>change a volume group</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<note><para>Most Volume group attributes may be changed here with some
    restrictions. For example: changes in the extent size depend on the
    alignment of allocated extents, so some sizes my not be possible. Also, a
    volume group can not be made unavailable if it contains mounted or otherwise
    busy volumes.</para></note>

<caution><para>Do not enable cluster support unless there is a working cluster
    running. Switching off cluster support or using the volume group with it
    enabled is difficult without a cluster.</para></caution>

</sect1>
</chapter>

<chapter id="logical-volumes-kvpm">
<title>Logical Volumes</title>

<sect1 id="logical-volume-intro">
<title>Working With Logical Volumes</title>

<para>Nearly any action that can be taken on a logical volume is done from the
logical volume context menu discussed next or the equivalent tool bar. It
has menu entries for the creation, deletion, extension and reduction of logical
volumes and a variety of other changes that can be made to a volume. There are
also two sub menus, one for changes in mirroring and another for handling or
writing filesystems on the volume.</para>
</sect1>

<sect1 id="logical-volume-menu">
<title>The Logical Volume Context Menu</title>

<note><para>This is a pop-up menu activated with the &RMB;. See <link
linkend="typical-volume-group-colors">The Logical Volume Bar</link> and <link
linkend="typical-volume-group-vgtree">The Logical Volume Tree</link> for
information on calling this context menu</para></note>

<variablelist>
<varlistentry>
<term><menuchoice>
<guimenuitem>Create logical volume</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a new logical volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Create thin pool</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a new pool for thin provisioned logical volumes.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Create thin volume</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a new thin provisioned logical volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Delete logical volume</guimenuitem>
</menuchoice></term>
<listitem><para>Deletes the selected logical volume, thin pool or thin volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Rename logical volume</guimenuitem>
</menuchoice></term>
<listitem><para>Renames the logical volume, thin pool or thin volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Create snapshot</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a snapshot volume based on the selected volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Create thin snapshot</guimenuitem>
</menuchoice></term>
<listitem><para>Creates a thin provisioned snapshot volume based on the selected volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Merge snapshot</guimenuitem>
</menuchoice></term>
<listitem><para>Merges the snapshot with it logical volume origin.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Reduce logical volume</guimenuitem>
</menuchoice></term>
<listitem><para>Reduces the size of the logical volume.</para></listitem>
</varlistentry>


<varlistentry>
<term><menuchoice>
<guimenuitem>Extends logical volume</guimenuitem>
</menuchoice></term>
<listitem><para>Enlarges the size of the logical volume.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Move physical extents</guimenuitem>
</menuchoice></term>
<listitem><para>Move the logical volume's extents to other physical volumes.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Change attributes or tags</guimenuitem>
</menuchoice></term>
<listitem><para>Changes the logical volume's attributes, such as allocation policy, or tags.</para></listitem>
</varlistentry>
</variablelist>

<sect2 id="logical-volume-mirror-menu">
<title>Mirror Operations on Volumes</title>

<para>The following five menu choices allow converting an existing volume into
a mirror, changing a mirror or converting a mirror back into a linear
volume.</para>

<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Mirror operations</guimenu>
<guimenuitem>Add mirror legs to volume</guimenuitem>
</menuchoice></term>
<listitem><para>Add one or more mirror legs to the volume, convert it to a
    mirror if it isn't already.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Mirror operations</guimenu>
<guimenuitem>Change mirror log</guimenuitem>
</menuchoice></term>
<listitem><para>Change the log type for a non-RAID mirror.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Mirror operations</guimenu>
<guimenuitem>Remove mirror legs</guimenuitem>
</menuchoice></term>
<listitem><para>Remove one or more mirror legs.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Mirror operations</guimenu>
<guimenuitem>Repair RAID or mirror</guimenuitem>
</menuchoice></term>
<listitem><para>Remove or replace missing physical volumes under mirror or RAID.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Mirror operations</guimenu>
<guimenuitem>Re-sync RAID or mirror</guimenuitem>
</menuchoice></term>
<listitem><para>Re-synchronize a RAID or mirror volume's underlying elements.</para></listitem>
</varlistentry>
</variablelist>
</sect2>

<sect2 id="logical-volume-filesystems-menu">
<title>Filesystem Operations on Volumes</title>

<para>The Filesystem operations sub-menu provides five common menu selections
for working with a filesystem.</para>
<para>Details are provided under <link linkend="filesystems-menu">Filesystem Operations</link>.</para>

</sect2>
</sect1>

<sect1 id="logical-volume-creation">
<title>Creating a Logical Volume</title>

<para>If a volume group exists and has free space, a logical volume can be
created in it. Select the tab titled with the name of the volume group you wish
to work with first. Then a dialog can be called up by right clicking on the long
green bar or the (still empty) table below it and selecting <guibutton>Create
logical volume</guibutton>. The toolbar also has an equivalent button. I have
called the volume <quote>VolumeOne</quote> and it will take 20 GiB of the available space. </para>

<screenshot>
<screeninfo>This is the volume group</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="vg2.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>A dialog for creating logical volumes</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</sect1>

<sect1 id="converting-mirrors">
<title>Converting Mirrors</title>

<para>To create a mirror from a linear volume, bring up
    the <link linkend="logical-volume-menu">logical volume context menu</link>
    and select <menuchoice><guimenu>Mirror operations</guimenu><guimenuitem>Add
    mirror legs to volume</guimenuitem></menuchoice>.  Then select the physical
    volumes and other options from the dialog. Mirrors may be the original LVM2
    mirrors or RAID. A mirror may be created with multiple legs or as few as two
    and non-RAID mirror legs can be striped. When the dialog is finished the
    data on the original linear volume will be copied to the new mirror leg or
    legs and synchronized.</para>

<note><para>If creating a non-RAID mirror remember to account for the space the
    mirror log takes when selecting physical volumes. Depending on configuration
    LVM may require separate physical volumes for logs.</para></note>

<tip><para>A mirror can be returned to a linear volume by removing all but one of its
    mirror legs. This can be a convenient way to move data on a mounted
    volume. Simply create a new mirror leg on the destination physical volume
    and wait for the mirror to sync. When finished, remove the source mirror leg
    and the remaining leg will have all the original data.</para></tip>
</sect1>
</chapter>

<chapter id="filesystems-kvpm">
<title>Filesystem Operations</title>
<sect1 id="filesystems-menu">
<title>Working With Filesystems</title>

<para>The Filesystem Operations menu is available under the <link
linkend="logical-volume-menu">Logical Volume</link> context menu and the <link linkend="storage-device-menu">Storage Device</link>
context menu.</para>

<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Filesystem operations</guimenu>
<guimenuitem>Mount</guimenuitem>
</menuchoice></term>
<listitem><para>Mount the filesystem under a directory.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Filesystem operations</guimenu>
<guimenuitem>Unmount</guimenuitem>
</menuchoice></term>
<listitem><para>Unmount the filesystem.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Filesystem operations</guimenu>
<guimenuitem>Extend filesystem to fill volume</guimenuitem>
</menuchoice></term>
<listitem><para>If the filesystem is smaller than the volume that contains it, extend it.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Filesystem operations</guimenu>
<guimenuitem>Run fsck -fp on filesystem</guimenuitem>
</menuchoice></term>
<listitem><para>Force fsck to preen a filesystem, use with caution.</para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Filesystem operations</guimenu>
<guimenuitem>Make or remove filesystem</guimenuitem>
</menuchoice></term>
<listitem><para>Write a filesystem on the volume or write zeros at the beginning to remove
    the filesystem.</para></listitem>
</varlistentry>

</variablelist>
</sect1>

<sect1 id="filesystems-mount">
<title>Mounting a Filesystem</title>

<sect2 id="filesystems-mount-type">
<title>Filesystem Type</title>

<para>The main tab of the filesystem mount dialog provides a list of the most
common filesystem types that may be selected. The dialog attempts to identify
the type and check the correct radio button in advance. If needed the user may
select <guimenuitem>Specify other</guimenuitem> and write the correct type into
the dialog.  There is also a place to enter the desired mount point and a
<guimenuitem>Browse</guimenuitem> button for convenience. It is possible to
mount a filesystem at multiple locations.</para>

<screenshot>
<screeninfo>Mounting a filesystem</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="mount_main.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>Mounting a filesystem</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</sect2>

<sect2 id="filesystems-mount-options">
<title>Mount Options</title>

<para>The options tab of the filesystem mount dialog provides a list of the most
common mount options and a place to write in a comma separated list of any
additional options required. If unsure, it is generally safe to leave these at
the default.</para>
<screenshot>
<screeninfo>Mounting a filesystem</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="mount_options.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>Mounting a filesystem</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</sect2>
</sect1>

<sect1 id="filesystems-mkfs">
<title>Writing a Filesystem</title>

<para>In the following dialog the device <quote>/dev/MyVolumeGroup/MyVolume</quote> has been
selected to write a new filesystem on. The type <quote>ext4</quote> has been
chosen and the beginning of the volume will be zeroed out to erase the old
filesystem.</para>

<screenshot>
<screeninfo>Writing a filesystem</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="mkfs_main.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>Writing a filesystem</phrase>
	  </textobject>
	</mediaobject>
</screenshot>

<para>If ext2, ext3 or ex4 are selected the <guilabel>Standard Ext
Options</guilabel> tab will be enabled. Selecting ext4 also enables the tab
labeled <guilabel>Additional Ext4 Options.</guilabel> This dialog may also be
used to create Linux swap space. Most filesystem types also allow an optional
short text label which can be supplied here.</para>

<note><para>It is not necessary to erase the old filesystem but doing so
is recommended. If the old filesystem is of a different type, the remaining traces
of it can fool &kvpm; and other programs into misidentifying the new filesystem.</para></note>

<note><para>&kvpm; uses the standard system programs to write filesystems. If a
filesystem type is chosen for which the needed program is missing, &kvpm; will
generate an error message and otherwise do nothing. See also, <link
linkend="programs">Programs</link>. </para></note>


<sect2 id="filesystems-mkfs-ext">
<title>Standard Options For Ext2, Ext3 and Ext4</title>

<screenshot>
<screeninfo>Writing an ext filesystem</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="mkfs_ext.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>Writing a filesystem</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</sect2>

<sect2 id="filesystems-mkfs-ext4">
<title>Ext4 Only Options</title>
<screenshot>
<screeninfo>Writing an ext4 filesystem</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="mkfs_ext4.png" format="PNG"/>
	  </imageobject>
	    <textobject>
	    <phrase>Writing a filesystem</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</sect2>

</sect1>


</chapter>

<chapter id="config-options-kvpm">
<title>Configuring &kvpm;</title>
<sect1>
<title>The Configuration Dialog</title>
<para>There are many aspects of &kvpm; that may be configured or customized. To access the configuration dialog select 

<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kvpm;</guimenuitem></menuchoice></para>
<para>The dialog has three pages:</para>


<variablelist>  
  <varlistentry>
    <term><guimenu>General</guimenu></term>
    <listitem><para>Configures the data to display or hide.</para></listitem>
  </varlistentry>
  <varlistentry>
    <term><guimenu>Colors</guimenu></term>
    <listitem><para>Configures the colors used to represent different types of
    filesystem or types of partitions and volumes.</para></listitem>
  </varlistentry>
  <varlistentry>
    <term><guimenu>Programs</guimenu></term>
    <listitem><para>Configures the places to look for support programs.</para></listitem>
  </varlistentry>
</variablelist>
</sect1>

<sect1 id="general">
<title>General</title>

<para>The <guimenuitem>General</guimenuitem> page is the largest of the three
pages and has two tabs. The first tab <guimenuitem>Tree Views</guimenuitem> is
for configuring the tree and table views. The second tab <guimenuitem>Property
Panels</guimenuitem> deals with the property panel that each tree or table has
associated with it. See <link linkend="getting-started-kvpm-group">here</link>
for more detail on the layout of the trees and panels. Any changes made to the
configuration may be reverted to the default simply by pressing the
<guimenuitem>Defaults</guimenuitem> button at the bottom of the dialog.</para>

<sect2 id="general-trees">
<title>Tree Views</title>

<para>The columns of each tree my be hidden or shown as desired by clicking on
the appropriate check box. For example, to hide the mount point column in the
device tree, find the section titled <guimenuitem>Device Tree</guimenuitem> and
uncheck the check box labeled <guimenuitem>Mount point</guimenuitem>. Some
information, such as stripe size, is duplicated in the property panel and may be
hidden by default in the tree view. The amount of space left on a device or
volume may be set to show as a percentage of the the total space, in
Mega/Giga/Tera bytes or both. There is also an option to enable a warning icon
in the <guilabel>remaining</guilabel> column when the amount of space left drops
below a user set level. </para>
</sect2>

<sect2 id="general-panels">
<title>Property Panels</title>

<para>The panels are divided into sections which may be, optionally, shown or
hidden. Checking a box enables showing the section while unchecking it will hide
the section.</para>
</sect2>
</sect1>

<sect1 id="colors">
<title>Colors</title>

<para>The <guimenuitem>Colors</guimenuitem> page is for customizing the colors
  used where devices or volumes are shown graphically. For devices the color can
  be configured to represent the device, such as one color for logical
  partitions and another for primary partitions. For volumes the color would be
  different between RAID and linear for example. The other option is to have the
  color represent the filesystem type on the device, if there is one. Colors can
  be changed by clicking on the color picker buttons.</para>
</sect1>

<sect1 id="programs">
<title>Programs</title>

<para>The <guimenuitem>Programs</guimenuitem> page has two tabs. The first tab
sets the search path for needed support programs. The second tab contains a list
of the programs that are needed and where, or if, they were found.</para>
<sect2 id="programs-search">
<title>Search Path</title>

<para>Most of the functionality of &kvpm; comes from standard LVM and system
programs such as lvcreate and mkfs. The search path is a list of locations in
the system where &kvpm; should look to find the needed programs. The standard
locations in the list are: </para>

<simplelist>
<member>/sbin</member>
<member>/usr/sbin</member>
<member>/bin</member>
<member>/usr/bin</member>
<member>/usr/local/sbin</member>
<member>/usr/local/bin</member>
</simplelist>

<para>Using the provided list box it is possible to add new locations or to
remove unwanted ones. The search is done from top to bottom so moving items up
or down in the list will change their search order. The
<guimenuitem>Defaults</guimenuitem> button will restore the standard
list.</para>
</sect2>

<sect2 id="programs-found">
<title>Program List</title> <para>The second tab has a list of all the needed
executables and the location where they were found. If a program could not be
found an error message will be displayed.</para>
</sect2>
</sect1>
</chapter>

<chapter id="credits">

<title>Credits and License</title>

<para>
&kvpm;
</para>


<!--List all the copyright holders here-->
<para>Program Copyright 2008, 2009, 2010, 2011 &Benjamin.Scott; &benscott.email;</para>

<para>Documentation Copyright 2011 &Benjamin.Scott; &benscott.email;</para>

<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
&underFDL;               <!-- FDL: do not remove -->
&underGPL;        	 <!-- GPL License -->

</chapter>

<!-- !!!!do not change ANYTHING after this line!!!! (?) -->

</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes: nil
sgml-general-insert-case: lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

