LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2004-09-20 13:00:51 +00:00
parent e422050641
commit afa447e3fc
9 changed files with 923 additions and 496 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
LDP/guide/docbook/EVMSUG/EVMSUG.xml
View File

@ -1,32 +1,35 @@
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://docbook.org/xml/4.2/docbookx.dtd"
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "/usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd"
[
<!ENTITY evers "2.3.0">
<!ENTITY evmsugchap1 SYSTEM "over-ug.xml">
<!ENTITY evmsugpref SYSTEM "pref-ug.xml">
<!ENTITY evmscmuse SYSTEM "cmuse-ug.xml">
<!ENTITY evmsdebuglog SYSTEM "debuglog-ug.xml">
<!ENTITY evmsmigrate SYSTEM "migrateto-ug.xml">
<!ENTITY evmsdisplaydetails SYSTEM "displaydetails-ug.xml">
<!ENTITY evmsaddremseg SYSTEM "addremseg-ug.xml">
<!ENTITY evmscreateseg SYSTEM "create-seg.xml">
<!ENTITY evmscreatecont SYSTEM "create-cont.xml">
<!ENTITY evmscreatereg SYSTEM "create-reg-ug.xml">
<!ENTITY evers "2.4.0">
<!ENTITY evmsugpref SYSTEM "preface.xml">
<!ENTITY evmsugchap1 SYSTEM "overview.xml">
<!ENTITY evmscmuse SYSTEM "interfaces.xml">
<!ENTITY evmsdebuglog SYSTEM "logfile.xml">
<!ENTITY evmsmigrate SYSTEM "compatibilityvols.xml">
<!ENTITY evmsdisplaydetails SYSTEM "interfacedisplaydetails.xml">
<!ENTITY evmsaddremseg SYSTEM "addremoveseg.xml">
<!ENTITY evmscreateseg SYSTEM "create-segments.xml">
<!ENTITY evmscreatecont SYSTEM "create-containers.xml">
<!ENTITY evmscreatereg SYSTEM "create-regions.xml">
<!ENTITY evmsdrivelinking SYSTEM "create-drivelinking.xml">
<!ENTITY evmssnapshotting SYSTEM "create-snapshot.xml">
<!ENTITY evmscreatevol SYSTEM "createvol-ug.xml">
<!ENTITY evmsfsimops SYSTEM "fsimops-ug.xml">
<!ENTITY evmsclusterops SYSTEM "clusterops-ug.xml">
<!ENTITY evmsconvert SYSTEM "convertto-ug.xml">
<!ENTITY evmscreatevol SYSTEM "createvolumes.xml">
<!ENTITY evmsfsimops SYSTEM "fsimops.xml">
<!ENTITY evmsclusterops SYSTEM "clusterops.xml">
<!ENTITY evmsconvert SYSTEM "convertvols.xml">
<!ENTITY evmsexpandshrink SYSTEM "expandshrink.xml">
<!ENTITY addfeatures SYSTEM "addfeatures-ug.xml">
<!ENTITY addfeatures SYSTEM "addfeatures.xml">
<!ENTITY selectactivate SYSTEM "selectact.xml">
<!ENTITY mountunmount SYSTEM "mount-unmount.xml">
<!ENTITY evmsplugintasks SYSTEM "plugintasks.xml">
<!ENTITY evmsdeleterecursive SYSTEM "deleterecurs-ug.xml">
<!ENTITY evmsdeleterecursive SYSTEM "deleterecurs.xml">
<!ENTITY evmsreplaceobjects SYSTEM "replace-objects.xml">
<!ENTITY evmsmovesegs SYSTEM "move-segmentstorageobjs.xml">
<!ENTITY evmsmovesegs SYSTEM "move-segstorobjs.xml">
<!ENTITY evmsdos SYSTEM "appx-dos.xml">
<!ENTITY evmsmd SYSTEM "appx-md.xml">
<!ENTITY evmslvm SYSTEM "appx-lvm.xml">
<!ENTITY evmslvm2 SYSTEM "appx-lvm2.xml">
<!ENTITY evmscsm SYSTEM "appx-csm.xml">
<!ENTITY evmssnap SYSTEM "appx-snap.xml">
<!ENTITY evmsdrivelink SYSTEM "appx-drivelink.xml">
@ -35,6 +38,7 @@
<!ENTITY evmsreiserfsim SYSTEM "appx-reiserfs.xml">
<!ENTITY evmsext23fsim SYSTEM "appx-ext23.xml">
<!ENTITY evmsopengfsfsim SYSTEM "appx-opengfs.xml">
<!ENTITY evmsntfsim SYSTEM "appx-ntfs.xml">
]>
<book id="evmsug">
<bookinfo><title>EVMS User Guide</title>
@ -52,7 +56,7 @@
<affiliation><orgname>IBM</orgname></affiliation></author>
</authorgroup>
<pubdate>April 9, 2004</pubdate>
<pubdate>September 16, 2004</pubdate>
<copyright><year>2004</year>
@ -94,6 +98,8 @@
&evmsconvert;
&evmsexpandshrink;
&addfeatures;
&selectactivate;
&mountunmount;
&evmsplugintasks;
&evmsdeleterecursive;
&evmsreplaceobjects;
@ -101,11 +107,13 @@
&evmsdos;
&evmsmd;
&evmslvm;
&evmslvm2;
&evmscsm;
&evmsjfsfsim;
&evmsxfsfsim;
&evmsreiserfsim;
&evmsext23fsim;
&evmsopengfsfsim;
&evmsntfsim;
</book>

100
LDP/guide/docbook/EVMSUG/appx-lvm.xml
View File

@ -63,11 +63,96 @@ shrink regions, or move extents, in order to free the object from use.</para>
</sect2>
<sect2><title>Expanding consumed objects in LVM containers</title>
<para>In addition to adding new objects to an LVM container,
you can also expand
the space in a container by expanding one of the existing consumed
objects (PVs).
For example, if a PV is a disk-segment with freespace immediately
following it on
the disk, you can expand that segment, which will increase the
amount of freespace in the container.
Likewise, if a PV is a RAID-0 or RAID-5 region, you can expand
that region by adding additional objects, which in turn increases the
freespace in the container.</para>
<para>When using the GUI or text-mode UIs, PV-expand is performed by expanding
the container.
If any of the existing PVs are expandable, they will appear in the
expand-points list.
Choose the PV to expand, and then the options for expanding
that object. After the PV has expanded, the container's
freespace will reflect the additional space available on that PV.</para>
<para>When using the CLI, PV-expand is performed by expanding the
appropriate object directly.
The CLI and the EVMS engine will route the necessary commands so the
container is expanded at the same time.</para>
<para>The options for expanding a PV are dependent on the plug-in
that owns that PV object.
Please see the appropriate plug-in's appendix for more details on
options for that object.</para>
</sect2>
<sect2><title>Shrinking consumed objects in LVM containers</title>
<para>
In addition to removing existing objects from an LVM container,
you can
also reduce the size of a container by shrinking one of the existing
consumed objects (PVs).
This is only allowed if the consumed object
has physical extents (PEs) at the end of the object that are not allocated
to any LVM regions.
In this case, LVM2 will allow the object to
shrink by the number of unused PEs at the end of that object.
</para>
<para>
For example, if a PV is a desk-segment, you can shrink that segment,
which will decrease the amount of freespace in the container. Likewise,
if a PV is a RAID-0 or RAID-5 region, you can shrink that region by
removing one of the objects, which in turn decreases the freespace in
the container.
</para>
<para>
When using the GUI or text-mode UIs, PV-shrink is performed by shrinking
the container. If any of the existing PVs are shrinkable, they will
appear in the shrink-points list. Choose the PV to shrink, and then the
options for shrinking that object. After the PV has shrunk, the container's
freespace will reflect the reduced space available on that PV.
</para>
<para>
When using the CLI, PV-shrink is performed by shrinking the appropriate
object directly. The CLI and the EVMS engine will route the necessary
commands so the container is shrunk at the same time.
</para>
<para>
The options for shrinking a PV are dependent on the plug-in that owns
that PV object. Please see the appropriate plug-in's appendix for more
details on options for that object.
</para>
</sect2>
<sect2><title>Deleting LVM containers</title>
<para>You can delete a container as long as the container does not have any produced
regions. The LVM plug-in does not allow containers to be deleted if they have any
regions. No options are available for deleting LVM containers.</para>
</sect2>
<sect2><title>Renaming LVM containers</title>
<para>You can rename an existing LVM container. When renaming an LVM container,
all of the regions produced from that container will automatically have their names changed as
well, because the region names include the container name.
In the EVMS GUI and text-mode UIs, this is done using the
<command>modify properties</command> command,
which is available through the &quot;Actions&quot; menu or the context-sensitive pop-up menus.
In the EVMS CLI, this is done using the <command>set </command>command.</para>
<para>See <xref linkend="renamereg"></xref> for more information about the effects of renaming the regions.</para>
</sect2>
</sect1>
<sect1><title>Region operations</title>
@ -285,6 +370,21 @@ region and container.</para>
</sect2>
<sect2 id="renamereg"><title>Renaming LVM regions</title>
<para>You can rename an existing LVM region. In the EVMS GUI and text-mode UIs, this
is done using the <command>modify properties</command> command, which is available through the &quot;Actions&quot;
menu or the context-sensitive pop-up menus. In the EVMS CLI, this is done using the
<command>set</command> command.</para>
<para>If the renamed LVM region has a compatibility volume on it, then the name of that
compatibility volume will also change. In order for this to work correctly, that volume must
be unmounted before the name is changed. Also, be sure to update your
<filename>/etc/fstab</filename> file if the volume is listed, or the volume won't be mounted properly the next
time the system boots.</para>
<para>If the renamed LVM region has an EVMS volume or another storage object built on it,
then the region's name change will be transparent to the upper layers. In this case, the
rename can be done while the volume is mounted.</para>
</sect2>
</sect1>

1165
LDP/guide/docbook/EVMSUG/appx-md.xml
View File

File diff suppressed because it is too large Load Diff

BIN
LDP/guide/docbook/EVMSUG/cli_active.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 21 KiB

83
LDP/guide/docbook/EVMSUG/create-snapshot.xml
View File

@ -25,16 +25,7 @@ is taken from the snapshot, while the original remains in active use.
</para>
</sect1>
<sect1 id="createactivsnap"><title>Creating and activating snapshot objects</title>
<para>Creating and activating a snapshot is a two-step process.
The first step is to create the snapshot object.
The snapshot object specifies where the saved data will
be stored when changes are made to the original.
The second step is to activate the
object, which is to make an EVMS volume from the object.</para>
<sect2><title>Creating a snapshot</title>
<sect1 id="createactivsnap"><title>Creating snapshot objects</title>
<para>You can create a snapshot object from any unused storage object in EVMS
(disks, segments, regions, or feature objects).
The size of this consumed object is
@ -45,7 +36,6 @@ from the original to the snapshot, given sufficient activity on the original.
In this situation, the snapshot is deactivated and additional
I/O to the snapshot fails.
</para>
<para>Base the size of the snapshot object on the amount of activity that
is likely to take place on the original during the lifetime of the snapshot.
The more changes that occur on the
@ -62,19 +52,22 @@ object is the same size as the original volume, or a little larger,
to account for the snapshot mapping tables, the snapshot is
never deactivated.
</para>
<para>After you've created the snapshot object and saved the changes, the
snapshot will be activated (as long as the snapshot child object is already active).
This is a change from snapshots in EVMS 2.3.x and earlier, where the snapshot
would not be activated until the object was made into an EVMS volume. If you
wish to have an inactive snapshot, please add the name of the snapshot object
to the &quot;activate.exclude&quot; line in the EVMS configuration file (see section about
selective-activation for more details). If at any point you decide to deactivate a
snapshot object while the original volume is still active, the snapshot will be reset.
The next time that the snapshot object is activated, it will reflect the state of the
original volume at that point in time, just as if the snapshot had just been created.</para>
</sect2>
<para>In order to mount the snapshot, the snapshot object must still be made into an
EVMS volume. The name of this volume can be the same as or different than the
name of the snapshot object.</para>
<sect2><title>Activating a snapshot</title>
<para>After you create a snapshot, activate it by making an EVMS volume from the object.
After you create the volume and save the changes, the snapshot is active.
The only option you have to specify for activating snapshots is
the name to give the EVMS volume.
This name can be
the same as or different than the name of the snapshot object.</para>
</sect2>
</sect1>
<sect1 id="snapshotex"><title>Example: create a snapshot</title>
<para> This section shows how to create a snapshot with EVMS:</para>
@ -208,8 +201,8 @@ snapshot.</para>
command on the snapshot object
(not the snapshot volume).
This command reinitializes the snapshot without requiring you to
manually delete and recreate the volume.
The snapshot volume must be unmounted for it to be reinitialized.
manually deactivate and reactivate the volume.
The snapshot must be active but unmounted for it to be reinitialized.
</para>
<para>This section continues the example from the previous section,
@ -228,14 +221,14 @@ is called &quot;/dev/evms/snap.&quot;</para>
</menuchoice>
</para></listitem>
<listitem><para>Select the volume "snap."</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select <guibutton>Reset</guibutton>.</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click <guibutton>Reset</guibutton> on the action panel.
<listitem><para>Click or activate <guibutton>Reset</guibutton> on the action panel.
</para></listitem>
<listitem><para>Click <guibutton>Reset</guibutton> on the warning panel.</para></listitem>
<listitem><para>Click or activate <guibutton>Reset</guibutton> on the warning panel.</para></listitem>
</orderedlist>
@ -247,9 +240,9 @@ is called &quot;/dev/evms/snap.&quot;</para>
the object <guimenuitem>snap</guimenuitem>.
</para>
</listitem>
<listitem><para>Click <guibutton>Reset</guibutton> on the popup menu.</para></listitem>
<listitem><para>Click <guibutton>Reset</guibutton> on the action panel.</para></listitem>
<listitem><para>Click <guibutton>Reset</guibutton> on the warning panel.</para></listitem>
<listitem><para>Click or activate <guibutton>Reset</guibutton> on the popup menu.</para></listitem>
<listitem><para>Click or activate <guibutton>Reset</guibutton> on the action panel.</para></listitem>
<listitem><para>Click or activate <guibutton>Reset</guibutton> on the warning panel.</para></listitem>
</orderedlist>
</sect2>
@ -270,7 +263,7 @@ the object <guimenuitem>snap</guimenuitem>.
<sect1><title>Expanding a snapshot</title>
<para>
As mentioned in the <xref linkend="createactivsnap"></xref>, as data is
As mentioned in <xref linkend="createactivsnap"></xref>, as data is
copied from the original volume to the snapshot, the space available
for the snapshot might fill up, causing the snapshot to be invalidated.
This situation might cause your data backup to end prematurely, as the
@ -324,17 +317,17 @@ and comparing the percent-full field before and after the expand operation.
to see a list of EVMS feature objects.
</para></listitem>
<listitem><para>Select the volume <guimenuitem>/dev/evms/snap</guimenuitem>.</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select <guimenuitem>lvm/Sample Container/Sample Region</guimenuitem>.
This object is the object that will actually be expanded. </para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select the options for expanding the LVM region,
including the amount of extra space to add to the region.
</para></listitem>
<listitem><para>Click <guibutton>Expand</guibutton>.
<listitem><para>Click or activate <guibutton>Expand</guibutton>.
</para></listitem>
</orderedlist></para>
@ -347,14 +340,14 @@ and comparing the percent-full field before and after the expand operation.
</para>
</listitem>
<listitem><para>Select <guibutton>Expand</guibutton> from the popup menu.</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select the region <guimenuitem>lvm/Sample Container/Sample Region</guimenuitem>. This is the object that will
actually be expanded.</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select the options for expanding the LVM region, including the
amount of extra space to add to the region.</para></listitem>
<listitem><para>Click <guibutton>Expand</guibutton>.</para>
<listitem><para>Click or activate <guibutton>Expand</guibutton>.</para>
</listitem>
</orderedlist>
</sect2>
@ -429,25 +422,25 @@ all but the desired snapshot must be deleted before rollback can take place.
<guimenuitem>Storage Object Tasks</guimenuitem>.
</menuchoice> </para></listitem>
<listitem><para>Select the object "snap."</para></listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Select <guibutton>Rollback</guibutton></para>.</listitem>
<listitem><para>Click <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click <guibutton>Rollback</guibutton> on the action panel.
<listitem><para>Click or activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>Click or activate <guibutton>Rollback</guibutton> on the action panel.
</para></listitem>
<listitem><para>Click <guibutton>Rollback</guibutton> on the warning panel.
<listitem><para>Click or activate <guibutton>Rollback</guibutton> on the warning panel.
</para></listitem>
</orderedlist>
<para>Alternatively, you can perform these same steps with the context sensitive menus:</para>
<para>Alternatively, you can perform these same steps with the context-sensitive menus:</para>
<orderedlist>
<listitem><para>From the Feature Objects panel, right click (or press
<keycap>Enter</keycap> on) the object &quot;snap.&quot;</para>
</listitem>
<listitem><para>Click <guibutton>Rollback</guibutton> on the popup menu.</para>
<listitem><para>Click or activate <guibutton>Rollback</guibutton> on the popup menu.</para>
</listitem>
<listitem><para>Click <guibutton>Rollback</guibutton> on the action panel.</para>
<listitem><para>Click or activate <guibutton>Rollback</guibutton> on the action panel.</para>
</listitem>
<listitem><para>Click <guibutton>Rollback</guibutton> on the warning panel.</para>
<listitem><para>Click or activate <guibutton>Rollback</guibutton> on the warning panel.</para>
</listitem>
</orderedlist>

6
LDP/guide/docbook/EVMSUG/expandshrink.xml
View File

@ -65,6 +65,12 @@ shrink and expand options available for each type of FSIM.
<entry>Online only</entry>
</row>
<row>
<entry>NTFS</entry>
<entry>Offline only</entry>
<entry>Offline only</entry>
</row>
</tbody>
</tgroup>
</table>

BIN
LDP/guide/docbook/EVMSUG/gui_active.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 23 KiB

2
LDP/guide/docbook/EVMSUG/install-ug.xml
View File

@ -414,7 +414,7 @@ activates all of the volumes and fills in each of the checkboxes.</para>
<para>In addition to manually starting one of the EVMS user interfaces, there is a new
utility called <command>evms_activate</command>.
The <command>evms_activate</command> utility simply opens the EVMS Engine
and issues a <command>commit</command> command.
and tells the Engine to save the changes.
You might want to add a call to <command>evms_activate</command> to your
boot scripts in order to automatically activate your volumes at boot time. If
you have volumes listed in your <filename>/etc/fstab</filename> file,

15
LDP/guide/docbook/EVMSUG/replace-objects.xml
View File

@ -75,8 +75,19 @@ the object sdb1 will be moved to the &quot;Available Objects&quot; panel.</para>
</sect2>
<sect2 id="clireplace"><title>Using the CLI</title>
<para>The replace command has not yet been implemented in the EVMS CLI.
It will be available in a future release.</para>
<para>Use the <command>Replace</command> to replace objects with
the CLI:</para>
<programlisting>
Replace:source_object_name, target_object_name
</programlisting>
<para>
"source_object_name" is the name of the object you wish to replace with
"target_object_name." In the following example, sdb1 is replaced with
sdc1.
</para>
<programlisting>
Replace:sdb1,sdc1
</programlisting>
</sect2>
</sect1>