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

*** empty log message ***

This commit is contained in:
gferg 2003-11-27 16:29:09 +00:00
parent 69bae4d6d2
commit b9f6cff124
4 changed files with 2736 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2342
LDP/guide/docbook/EVMSUG/evmsug.html Normal file
View File

File diff suppressed because one or more lines are too long

147
LDP/guide/docbook/EVMSUG/manifesto Normal file
View File

@ -0,0 +1,147 @@
evmsug.html
userguidepref.html
intro.html
cando.html
uis.html
terminology.html
ch01s04.html
LAYERDEF.html
evmscmuse.html
GUI.html
NCURSES.html
COMMANDLINE.html
debuglevels.html
FSIMsupp.html
loglevels.html
specifylevels.html
evmsmigrate.html
guimigrate.html
ncurmigrate.html
climigrate.html
displaydetails.html
displaygui.html
displaydatancurses.html
ch05s03.html
evmsassignseg.html
whenassign.html
smtypes.html
assignsegex.html
assignsegnew.html
assignex.html
removeseg.html
rmvex.html
evmscreateseg.html
whyseg.html
crsegex.html
evmscreatecont.html
whencont.html
contex.html
evmscreatereg.html
ch09s01.html
crregex.html
evmscreatedrivelinking.html
whatisdrivelinking.html
howimp.html
ch10s03.html
drivelinkex.html
expandpartitions.html
shrinkdrivelink.html
deletedrivelink.html
evmscreatesnap.html
whatissnapshotting.html
createactivsnap.html
snapshotex.html
ch11s04.html
ch11s05.html
ch11s06.html
ch11s07.html
evmscreatevol.html
ch12s01.html
crvolexcomp.html
crvolexevms.html
evmsfsimops.html
FSIMsuppevms.html
fsimmkfs.html
fsimmkfsaex.html
clusterops.html
ch14s01.html
ch14s02.html
ch14s03.html
ch14s04.html
ch14s05.html
ch14s06.html
ch14s07.html
ch14s08.html
ch14s09.html
ch14s10.html
evmsconvert.html
ch15s01.html
comptoevms.html
evmstocomp.html
expandshrink.html
whyexpandshrink.html
exshrink.html
mkfs.html
addfeatures.html
whyadd.html
exaddfeature.html
plugintasks.html
aboutplugintasks.html
pluginexample.html
deleterecurs.html
howtodel.html
examdelrecur.html
evmsreplaceobjects.html
whatisobjectreplace.html
replacedlchildobj.html
segstorobjs.html
whatissegmove.html
whymove.html
ch21s03.html
movesegex.html
appxdos.html
DOShow.html
assignDOS.html
creatingDOS.html
expandDOS.html
shrinkDOS.html
deleteDOS.html
appxmdreg.html
createmdreg.html
addremspare.html
rmactiveraid.html
rmfaultyobj.html
markobjfaulty.html
replaceobj.html
characsraid.html
appxsnap.html
lvmimp.html
containerops.html
apcs03.html
appxcsm.html
csmassn.html
unassignCSM.html
apds03.html
jfsfsim.html
createjfsfsim.html
checkjfsfsim.html
removejfsfsim.html
expandjfsfsim.html
shrinkjfsfsim.html
xfsfsim.html
createxfsfsim.html
checkxfsfsim.html
removexfsfsim.html
expandxfsfsim.html
shrinkxfsfsim.html
reiserfsim.html
createreiserfsim.html
checkreiserfsim.html
removexreiserfsim.html
expandreiserFSfsim.html
shrinkreiserfsim.html
ext23fsim.html
createext23fsim.html
checkext23fsim.html
removereiserfsim.html
expandshrinkext23fsim.html

162
LDP/guide/docbook/EVMSUG/move-segmentstorageobjs.xml Normal file
View File

@ -0,0 +1,162 @@
<chapter id="segstorobjs"><title>Moving segment storage objects</title>
<para>This chapter discusses how and why to move segments.
</para>
<sect1 id="whatissegmove"><title>What is segment moving?</title>
<para>A segment move is when a data segment is relocated to another
location on the underlying storage object. The new location of
the segment cannot overlap with the current segment location.
</para>
</sect1>
<sect1 id="whymove"><title>Why move a segment?</title>
<para>
Segments are moved for a variety of reasons. The most compelling among
them is to make better use of disk freespace. Disk freespace is an unused
contiguous extent of sectors on a disk that has been identified by EVMS
as a freespace segment. A data segment can only be expanded by adding
sectors to the end of the segment, moving the end of the data segment
up into the freespace that immediately follows the data segment. However,
what if there is no freespace following the data segment? A segment or
segments could
be be moved around to put freespace after the segment that is to be
expanded. For example:
</para>
<itemizedlist>
<listitem>
<para>The segment following the segment to be expanded can be moved
elsewhere on the disk, thus freeing up space after the segment that
is to be expanded.</para>
</listitem>
<listitem>
<para>The segment to be expanded can be moved into freespace where
there is more room for the segment to be expanded.
</para>
</listitem>
<listitem>
<para>The segment can be moved into freespace that precedes the
segment so that after the move the data segment can be expanded into the freespace
created by the move.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1><title>Which segment manager plug-ins implement the move function?</title>
<para>The following segment manager plug-ins support the move function:
</para>
<itemizedlist>
<listitem>
<para>
DOS
</para>
</listitem>
<listitem>
<para>
s390
</para>
</listitem>
<listitem>
<para>
GPT
</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="movesegex"><title>Example: move a DOS segment</title>
<para> This section shows how to move a DOS segment:</para>
<note><title>Note</title>
<para>
In the following example, the DOS segment manager has a single
primary partition on disk sda that is located at the very end of the disk.
We want to move it to the front of the drive because we want to expand
the segment but there is currently no freespace following the segment.
</para>
</note>
<sect2 id="guimoveseg"><title>Using the EVMS GUI context sensitive menu</title>
<para>To move the DOS segment through the GUI context sensitive menu,
follow these steps:</para>
<orderedlist>
<listitem><para>From the <guimenuitem>Segments</guimenuitem>
tab, right click
<filename>sda1</filename>.
</para></listitem>
<listitem>
<para>Click <guibutton>Move</guibutton>.</para>
</listitem>
<listitem><para>Select <filename>sda_freespace1</filename>.
</para>
</listitem>
<listitem><para>Click <guibutton>Move</guibutton>.</para>
</listitem>
</orderedlist>
</sect2>
<!-- Ncurses-->
<sect2 id="ncursmoveseg"><title>Using Ncurses</title>
<para>To move the DOS segment, follow these steps:</para>
<orderedlist>
<listitem><para>Use <keycap>Tab</keycap>
to select the Disk Segments view.
</para>
</listitem>
<listitem><para>Scroll down with the down arrow and
select <filename>sda1</filename>.</para>
</listitem>
<listitem><para>Press
<keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>Scroll down with the down arrow and
select <guibutton>Move</guibutton> by pressing
<keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>Use the spacebar to select
<filename>sda_freespace1</filename>.</para>
</listitem>
<listitem><para>Use <keycap>Tab</keycap>
to select <guibutton>Move</guibutton> and press
<keycap>Enter</keycap>.
</para>
</listitem>
</orderedlist>
</sect2>
<!-- CLI-->
<sect2 id="clisegmove"><title>Using the CLI</title>
<para>Use the
<command>task</command> command to move a DOS segment with the CLI.
</para>
<programlisting>task:Move,sda1,sda_freespace1</programlisting>
</sect2>
</sect1>
</chapter>

85
LDP/guide/docbook/EVMSUG/replace-objects.xml Normal file
View File

@ -0,0 +1,85 @@
<chapter id="evmsreplaceobjects"><title>Replacing objects</title>
<para>This chapter discusses how to replace objects.</para>
<sect1 id="whatisobjectreplace"><title>What is object-replace?</title>
<para>Occasionally, you might wish to change the configuration of a volume or
storage object. For instance, you might wish to replace one of the disks in a
drive-link or RAID-0 object with a newer, faster disk. As another example, you
might have an EVMS volume created from a simple disk segment, and want to
switch that segment for a RAID-1 region to provide extra data redundancy.
Object-replace accomplishes such tasks.</para>
<para>
Object-replace gives you the ability to swap one object for another object.
The new object is added while the original object is still in place. The data is
then copied from the original object to the new object. When this is complete,
the original object is removed. This process can be performed while the volume is
mounted and in use.
</para>
</sect1>
<sect1 id="replacedlchildobj"><title>Replacing a drive-link child object</title>
<para>For this example, we will start with a drive-link object named <filename>link1</filename>,
which is composed of two disk segments named sda1 and sdb1. The goal is to replace
sdb1 with another segment named sdc1.</para>
<note><title>Note</title>
<para>The drive-linking plug-in allows the target object (sdc1 in this
example) to be the same size or larger than the source object.
If the target is larger, the extra space will be unused. Other plug-ins
have different restrictions and might require that both objects be the
same size.
</para>
</note>
<sect2 id="guiobjectreplace"><title>Using the EVMS GUI or Ncurses</title>
<para>Follow these steps to replace sdb1 with sdc1:
<orderedlist>
<listitem><para>Select
<menuchoice>
<guimenu>Actions</guimenu>
<guimenuitem>Replace.</guimenuitem>
</menuchoice>
</para></listitem>
<listitem><para>In the &quot;Replace Source Object&quot; panel select
<guimenuitem>sdb1</guimenuitem>.
</para></listitem>
<listitem><para>Activate <guibutton>Next</guibutton>.</para></listitem>
<listitem><para>In the &quot;Select Replace Target Object&quot; panel, select
<guimenuitem>sdc1</guimenuitem>. </para></listitem>
<listitem><para>Activate <guibutton>Replace</guibutton>.</para></listitem>
</orderedlist></para>
<para>Alternatively, you can perform these same steps with the
context sensitive menus:</para>
<orderedlist>
<listitem><para>From the &quot;Disk Segments&quot; panel, right click (or Press
<keycap>Enter</keycap> on) the object
<guimenuitem>sdb1</guimenuitem>.</para></listitem>
<listitem><para>Choose <guimenuitem>Replace</guimenuitem> on the popup menu.</para></listitem>
<listitem><para>In the &quot;Select Replace Target Object&quot; panel, select
<guimenuitem>sdc1.</guimenuitem></para></listitem>
<listitem><para>Activate <guibutton>Replace</guibutton>.</para></listitem>
</orderedlist>
<para>When you save changes, EVMS begins to copy the data from sdb1 to sdc1.
The status bar at the bottom of the UI will reflect the percent-complete of the
copy operation. The UI must remain open until the copy is finished. At that time,
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>
</sect2>
</sect1>
</chapter>