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

updated

This commit is contained in:
gferg 2004-04-13 13:23:01 +00:00
parent 710bdc5ec6
commit fb8b98e57b
12 changed files with 159 additions and 105 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,14 +1,14 @@
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://docbook.org/xml/4.2/docbookx.dtd"
[
<!ENTITY evers "2.2.0">
<!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 evmsassignseg SYSTEM "assignseg-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">
@ -34,6 +34,7 @@
<!ENTITY evmsxfsfsim SYSTEM "appx-xfs.xml">
<!ENTITY evmsreiserfsim SYSTEM "appx-reiserfs.xml">
<!ENTITY evmsext23fsim SYSTEM "appx-ext23.xml">
<!ENTITY evmsopengfsfsim SYSTEM "appx-opengfs.xml">
]>
<book id="evmsug">
<bookinfo><title>EVMS User Guide</title>
@ -51,10 +52,10 @@
<affiliation><orgname>IBM</orgname></affiliation></author>
</authorgroup>
<pubdate>November 25, 2003</pubdate>
<pubdate>April 9, 2004</pubdate>
<copyright><year>2003</year>
<copyright><year>2004</year>
<holder>IBM</holder></copyright>
@ -81,7 +82,7 @@
&evmsdebuglog;
&evmsmigrate;
&evmsdisplaydetails;
&evmsassignseg;
&evmsaddremseg;
&evmscreateseg;
&evmscreatecont;
&evmscreatereg;
@ -105,5 +106,6 @@
&evmsxfsfsim;
&evmsreiserfsim;
&evmsext23fsim;
&evmsopengfsfsim;
</book>

7
LDP/guide/docbook/EVMSUG/appx-csm.xml
View File

@ -86,10 +86,11 @@ node from which you are running the EVMS user interface.</para></listitem>
</varlistentry>
<varlistentry><term>Container Name</term>
<listitem><para>The name for the container. Currently, you need to keep this name unique
<listitem><para>The name for the container. You need to keep this name unique
across the cluster to prevent name-in-conflict errors should the container fail over to
another node that has a container with the same name. Later releases of EVMS will assist
you with this. </para></listitem>
another node that has a container with the same name.
</para>
</listitem>
</varlistentry>
<varlistentry><term>Storage Type</term>

2
LDP/guide/docbook/EVMSUG/appx-ext23.xml
View File

@ -97,7 +97,7 @@ them as busy. The default is false.</para>
</sect1>
<sect1 id="removereiserfsim"><title>Removing Ext-2/3 file systems</title>
<sect1 id="removeext23fsim"><title>Removing Ext-2/3 file systems</title>
<para>
An Ext-2/3 file system can be removed from its volume if the file system is

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

@ -1,4 +1,4 @@
<appendix id="appxsnap"><title>The LVM plug-in</title>
<appendix id="appxlvm"><title>The LVM plug-in</title>
<para>The LVM plug-in combines storage objects into groups called containers.
From these containers, new storage objects can be created, with a variety of

125
LDP/guide/docbook/EVMSUG/clusterops-ug.xml
View File

@ -17,20 +17,29 @@ a shared container to a private container. EVMS also provides the flexibility t
change the ownership of a private container from one cluster node to another
cluster node.</para>
<sect1><title>Rules and restrictions for creating cluster containers</title>
<para>Note the following rules and limitations for creating cluster containers:</para>
<para>Note the following rules and limitations for creating cluster containers:
</para>
<itemizedlist>
<listitem><para>Do not assign non-shared disks to a cluster container.</para>
<listitem>
<para>Do not assign non-shared disks to a cluster container.
</para>
</listitem>
<listitem><para>Storage objects created on a cluster container must not span across
multiple cluster containers. Currently, the EVMS Engine cannot enforce this rule, so
you must ensure that objects and volumes created from cluster storage manager
segments do not span multiple containers.</para>
<listitem>
<para>Storage objects and volumes created on a cluster container must not
span across multiple cluster containers.
The EVMS Engine enforces this rule by disallowing such configurations.
</para>
</listitem>
<listitem><para>A disk should not span cluster containers.</para>
</listitem>
<listitem><para>Do not assign RAID, snapshot, and BBR features to storage
objects on a cluster container.</para>
<listitem>
<para>Do not assign RAID-1, RAID-5, BBR, or snapshotting
to storage objects on a shared cluster container. These plug-ins
can be used on private cluster containers.
</para>
</listitem>
</itemizedlist>
</sect1>
@ -194,9 +203,6 @@ Storage Type as
</listitem>
<listitem><para>Commit the changes.</para>
</listitem>
<listitem><para>Quit the GUI and run <command>evms_activate</command> on each of the cluster
nodes so that the nodes discover the volume.
This process will be automated in future releases of EVMS.</para></listitem>
</orderedlist>
</sect2>
@ -255,7 +261,6 @@ the name of the container and the type of the container.</para>
<para>On the CLI, type the following command to create shared container <filename>Shar1</filename>:</para>
<programlisting>create: container,CSM={name=&quot;Shar1&quot;,type=&quot;shared&quot;},sdd,sde,sdf</programlisting>
<para>Run <command>evms_activate</command> on each node of the cluster. This process will be automated in future releases of EVMS.</para>
</sect2>
</sect1>
@ -282,17 +287,14 @@ container with the EVMS GUI:</para>
<orderedlist>
<listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para>
</listitem>
<listitem><para>Select the container <guimenuitem>csm/Priv1</guimenuitem> and press <keycap>Next</keycap>.</para>
<listitem><para>Select the container <guimenuitem>Priv1</guimenuitem> and press <keycap>Next</keycap>.</para>
<para>A Modify Properties dialog box opens.</para>
</listitem>
<listitem><para>Change &quot;Type Field&quot; to &quot;shared&quot; and click <keycap>Modify</keycap>.</para>
<listitem><para>Change &quot;Type&quot; to &quot;shared&quot; and click <keycap>Modify</keycap>.</para>
<para>A window opens that displays the outcome.</para>
</listitem>
<listitem><para>Commit the changes.</para>
</listitem>
<listitem><para>Quit the GUI and run <command>evms_activate</command> on all the cluster nodes so that the nodes discover
all the volumes on the <filename>csm/Priv1</filename> container. This process will be
automated in a future release of EVMS.</para></listitem>
</orderedlist>
</sect2>
@ -304,7 +306,7 @@ container with the Ncurses interface:</para>
</listitem>
<listitem><para>The Modify Container Properties dialog opens. Select the container
<filename>csm/Priv1</filename> by
<filename>Priv1</filename> by
pressing <keycap>spacebar</keycap>. The container you selected is marked with an &quot;x.&quot;</para>
<para>Press <keycap>Enter</keycap>.</para>
</listitem>
@ -314,13 +316,13 @@ and <filename>sdf</filename> from the list. The disks you select are marked wit
</listitem>
<listitem><para>Press <keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>The Modify Container Properties - Configuration Options&quot; dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the &quot;Type field&quot;.</para>
<listitem><para>The Modify Container Properties - Configuration Options&quot; dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on &quot;Type&quot;.</para>
</listitem>
<listitem><para>Press <keycap>spacebar</keycap>.</para>
</listitem>
<listitem><para>The Change Option Value dialog opens. Type <userinput>shared</userinput> and press <keycap>Enter</keycap>.</para>
<para>The changed value is now displays in the Modify Container Properties -
<para>The changed value now displays in the Modify Container Properties -
Configuration Options dialog.</para>
</listitem>
@ -329,10 +331,6 @@ Configuration Options dialog.</para>
</listitem>
<listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown menu.</para>
</listitem>
<listitem><para>Quit Ncurses and run <command>evms_activate</command> on all the cluster nodes so that the nodes discover
all the volumes on the <filename>csm/Priv1</filename> container. This process will be
automated in a future release of EVMS.</para></listitem>
</orderedlist>
</sect2>
@ -341,10 +339,8 @@ automated in a future release of EVMS.</para></listitem>
<para>The <command>modify</command> command modifies the properties of a container. The first argument
of the command is the object to modify, followed by its new properties. The command
to convert the private container to a shared container in the example is:</para>
<programlisting>modify: csm/Priv1,type=shared</programlisting>
<para>Run <command>evms_activate</command> on all the cluster nodes so that the nodes discover
all the volumes on the <filename>csm/Priv1</filename> container. This process will be
automated in a future release of EVMS.</para>
<programlisting>modify: Priv1,type=shared</programlisting>
</sect2>
</sect1>
@ -371,17 +367,14 @@ container with the EVMS GUI:</para>
<orderedlist>
<listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para>
</listitem>
<listitem><para>Select the container <guimenuitem>csm/Shar1</guimenuitem> and press <keycap>Next</keycap>.</para>
<listitem><para>Select the container <guimenuitem>Shar1</guimenuitem> and press <keycap>Next</keycap>.</para>
<para>A Modify Properties dialog opens.</para>
</listitem>
<listitem><para>Change &quot;Type Field&quot; to &quot;private&quot; and the &quot;NodeID&quot; field to <filename>node1</filename>. Click <keycap>Modify</keycap>.</para>
<listitem><para>Change &quot;Type&quot; to &quot;private&quot; and the &quot;Node&quot; field to <filename>node1</filename>. Click <keycap>Modify</keycap>.</para>
<para>A window opens that displays the outcome.</para>
</listitem>
<listitem><para>Commit the changes.</para>
</listitem>
<listitem><para>Quit the GUI and run <command>evms_activate</command> on the other nodes to deactivate
the volumes of the shared container on the other nodes. This process will be
automated in a future release of EVMS.</para></listitem>
</orderedlist>
</sect2>
@ -396,7 +389,7 @@ container with the Ncurses interface:</para>
<listitem>
<para>The Modify Container Properties dialog opens. Select the container
<filename>csm/Shar1</filename> by
<filename>Shar1</filename> by
pressing <keycap>spacebar</keycap>. The container you selected is marked with an &quot;x.&quot;</para>
<para>Press <keycap>Enter</keycap>.</para>
</listitem>
@ -407,7 +400,7 @@ pressing <keycap>spacebar</keycap>. The container you selected is marked with a
<listitem><para>Press <keycap>spacebar</keycap>.</para>
</listitem>
<listitem><para>The Change Option Value dialog opens. Type <userinput>private</userinput> and press <keycap>Enter</keycap>.</para>
<listitem><para>The Change Option Value dialog opens. Select <userinput>private</userinput> and press <keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>The Modify Container Properties -
@ -415,7 +408,7 @@ Configuration Options dialog opens. Scroll down the list to <guimenuitem>NodeId
with the <keycap>down</keycap> arrow
and press <keycap>spacebar</keycap>.</para></listitem>
<listitem><para>The Change Option Value dialog opens. Enter <userinput>node1</userinput> and press <keycap>Enter</keycap>.</para></listitem>
<listitem><para>The Change Option Value dialog opens. Select <userinput>node1</userinput> and press <keycap>Enter</keycap>.</para></listitem>
<listitem><para>The changed values now display in the Modify Container Properties -
Configuration Options dialog. Press <keycap>Enter</keycap>. </para>
@ -423,8 +416,6 @@ Configuration Options dialog. Press <keycap>Enter</keycap>. </para>
</listitem>
<listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown.</para></listitem>
<listitem><para>Quit Ncurses and run <command>evms_activate</command> on all the cluster nodes to deactivate the volumes of the shared container on all the other nodes. This process will be
automated in a future release of EVMS.</para></listitem>
</orderedlist>
</sect2>
@ -434,10 +425,7 @@ automated in a future release of EVMS.</para></listitem>
<para>The <command>modify</command> command modifies the properties of a container. The first argument
of the command is the object to modify, followed by its new properties. The command
to convert the shared container to a private container in the example is:</para>
<programlisting>modify: csm/Shar1,type=private,nodeid=node1</programlisting>
<para>Run <command>evms_activate</command> on all the cluster nodes to deactivate the volumes
of the shared container on all the other nodes. This process will be
automated in a future release of EVMS.</para>
<programlisting>modify: Shar1,type=private,node=node1</programlisting>
</sect2>
</sect1>
@ -471,7 +459,7 @@ To deport a container with the EVMS GUI, follow these steps:
</para>
</listitem>
<listitem>
<para>Select the container <filename>csm/c1</filename> and press
<para>Select the container <filename>c1</filename> and press
<keycap>Next</keycap>.
</para>
<para>
@ -479,7 +467,7 @@ A Modify Properties dialog opens.
</para>
</listitem>
<listitem>
<para>Change "Type Field" to "deported." Click <keycap>Modify</keycap>.
<para>Change "Type" to "deported." Click <keycap>Modify</keycap>.
</para>
<para>
A window opens that displays the outcome.
@ -490,13 +478,6 @@ A window opens that displays the outcome.
</para>
</listitem>
</orderedlist>
<note><title>NOTE</title>
<para>
If the deported container was a shared container, quit the GUI and then
run <command>evms_activate</command> on each cluster node. This operation
will be automated in a future release of EVMS.
</para>
</note>
</sect2>
@ -568,14 +549,6 @@ The outcome of the command is displayed at the bottom of the screen.
</orderedlist>
<note><title>NOTE</title>
<para>
If the deported container was a shared container, quit Ncurses and then
run <command>evms_activate</command> on each cluster node. This operation
will be automated in a future release of EVMS.
</para>
</note>
</sect2>
<sect2><title>Using the CLI</title>
@ -584,17 +557,9 @@ To deport a container from the CLI, execute the following command
at the CLI prompt:
</para>
<programlisting>
modify: csm/c1,type="deported"
modify: c1,type=deported
</programlisting>
<note><title>NOTE</title>
<para>
If the deported container was a shared container,
run <command>evms_activate</command> on each cluster node. This operation
will be automated in a future release of EVMS.
</para>
</note>
</sect2>
</sect1>
<sect1><title>Deleting a cluster container</title>
@ -633,8 +598,9 @@ to the other node when <filename>node1</filename> dies.</para>
node with <filename>node2</filename> as the owning node, then add the following entry to
<filename>/etc/ha.d/haresources</filename>:</para>
<programlisting>node2 evms_failover::container3 evms_failover::container4</programlisting>
<para>Refer to the following source for more details on the semantics of resource groups:
<ulink url="http://www.linux-ha.org/download/GettingStarted.html">http://www.linux-ha.org/download/GettingStarted.html</ulink>.</para>
<para>Refer to
<ulink url="http://www.linux-ha.org/download/GettingStarted.html">http://www.linux-ha.org/download/GettingStarted.html</ulink> for more details on the
semantics of resource groups.</para>
</listitem>
<listitem><para>Validate that the <filename>/etc/ha.d</filename>, <filename>/etc/ha.cf</filename> and <filename>/etc/ha.d/haresources</filename> files are the same
on all the nodes of the cluster.</para>
@ -671,7 +637,8 @@ through the various EVMS user interfaces.</para>
</listitem>
</orderedlist>
<para>
The discovery of the remote configuration is initiated and the status
The GUI gathers information about the objects, containers, and volumes on
the other node. The status
bar displays the message "Now administering node node2," which indicates
that the GUI is switched over to node node2.
</para>
@ -694,8 +661,8 @@ press <keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>Press <keycap>Enter</keycap>.</para>
</listitem>
<listitem><para>The &quot;EVMS is examining your system. Please wait&quot; dialog opens. After a
while you will be switched over to the node <filename>node2</filename>.</para></listitem>
<listitem><para>After a while, you will be switched over to
the node <filename>node2</filename>.</para></listitem>
</orderedlist>
</sect2>
@ -731,8 +698,7 @@ the node currently has quorum
<para>
Similarly, a shared container and its objects are made active on a node if
the node currently has quorum. However, the administrator can force the
importation of private and shared containers by overriding these rules, as
follows:
importation of private and shared containers by overriding these rules.
</para>
<note><title>NOTE</title>
@ -747,8 +713,9 @@ on the node can get corrupted.
<orderedlist>
<listitem>
<para>
Enabling the maintenance mode in the <command>evms.conf</command> file.
The option to modify in the <command>evms.conf</command> file is the following:
Enabling maintenance mode in the <filename>/etc/evms.conf</filename> file.
The option to modify in the <filename>/etc/evms.conf</filename> file is the
following:
</para>
<programlisting>
# cluster segment manager section

19
LDP/guide/docbook/EVMSUG/convertto-ug.xml
View File

@ -5,10 +5,21 @@ of the differences between compatibility and EVMS volumes, see <xref linkend="ev
<sect1><title>When to convert volumes</title>
<para>There are several different scenarios that might help you determine what type of volumes you need. For example, if you wanted persistent names or to make full use of EVMS features, such as BBR, Drive Linking, or Snapshotting, you would convert your compatibility volumes to EVMS volumes. In another situation, you might decide that a volume needs to be read by a system that understands the underlying volume management scheme. In this case, you would convert your EVMS volume to a compatibility volume.</para>
<para>A volume can only be converted when it is offline. This means the volume must
be unmounted and otherwise not in use. The volume must be unmounted because the conversion operation changes both the name and the device number of the volume. Once the volume
is converted, you can remount it using its new name.</para>
<para>There are several different scenarios that might help you determine
what type of volumes you need.
For example, if you wanted persistent names or to make full use of
EVMS features, such as Drive Linking or Snapshotting, you would convert
your compatibility volumes to EVMS volumes.
In another situation, you might decide that a volume needs to be
read by a system that understands the underlying volume management scheme.
In this case, you would convert your EVMS volume to a
compatibility volume.</para>
<para>A volume can only be converted when it is offline.
This means the volume must be unmounted and otherwise not in use.
The volume must be unmounted because the conversion operation changes both
the name and the device number of the volume.
Once the volume is converted, you can remount it using its new name.</para>
</sect1>

4
LDP/guide/docbook/EVMSUG/createvol-ug.xml
View File

@ -15,8 +15,8 @@ become a volume; it must be made into a volume.</para>
EVMS equipped system. Volumes are mountable and can contain file systems.</para>
<para>EVMS native volumes contain EVMS-specific information
to identify the name and minor number. After this volume information is
<para>EVMS native volumes contain EVMS-specific information to identify
the volume name. After this volume information is
applied, the volume is no longer fully backward compatible
with existing volume types.</para>

14
LDP/guide/docbook/EVMSUG/debuglog-ug.xml
View File

@ -23,9 +23,9 @@
<row><entry>Warning</entry><entry>An error has occurred that the system might or might not be able to work around.</entry></row>
<row><entry>Default</entry><entry>An error has occurred that the system has already worked around.</entry></row>
<row><entry>Details</entry><entry>Detailed information about the system.</entry></row>
<row><entry>Entry_Exit</entry><entry>Traces the entries and exits of functions.</entry></row>
<row><entry>Debug</entry><entry>Information that helps the user debug a problem.</entry></row>
<row><entry>Extra</entry><entry>More information that helps the user debug a problem than the &quot;Debug&quot; level provides.</entry></row>
<row><entry>Entry_Exit</entry><entry>Traces the entries and exits of functions.</entry></row>
<row><entry>Everything</entry><entry>Verbose output.</entry></row>
</tbody></tgroup></table></para>
@ -58,6 +58,18 @@ in the previous commands) makes it easier for us to help you.
<para>The CLI command, <command>probe</command>, opens and closes the Engine, which causes a new log to start. The log that existed before the <command>probe</command> command was issued is renamed <filename>/var/log/evmsEngine.1.log</filename> and the new log is named <filename>/var/log/evmsEngine.log</filename>.</para>
<para>
If you will be frequently using a different log level than the default,
you can specify the default logging level in
<filename>/etc/evms.conf</filename> rather than
having to use the <command>-d</command> option when starting the user interface.
The "debug_level" option in the "engine" section sets the default
logging level for when the Engine is opened.
Using the <command>-d</command> option
during the command invocation overrides the setting in
<filename>/etc/evms.conf</filename>.
</para>
</sect1>
</chapter>

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

@ -28,7 +28,49 @@ shrink and expand options available for each type of FSIM.
<entry>Expands</entry>
</row>
</thead>
<tbody><row><entry>JFS</entry><entry>No</entry><entry>Online only</entry></row><row><entry>XFS</entry><entry>No</entry><entry>Online only</entry></row><row><entry>ReiserFS</entry><entry>Offline only</entry><entry>Offline and online</entry></row><row><entry>ext2/3</entry><entry>Offline only</entry><entry>Offline only</entry></row><row><entry>SWAPFS</entry><entry>Offline only</entry><entry>Offline only</entry></row></tbody></tgroup></table></para>
<tbody>
<row>
<entry>JFS</entry>
<entry>No</entry>
<entry>Online only</entry>
</row>
<row>
<entry>XFS</entry>
<entry>No</entry>
<entry>Online only</entry>
</row>
<row>
<entry>ReiserFS</entry>
<entry>Offline only</entry>
<entry>Offline and online</entry>
</row>
<row>
<entry>ext2/3</entry>
<entry>Offline only</entry>
<entry>Offline only</entry>
</row>
<row>
<entry>SWAPFS</entry>
<entry>Offline only</entry>
<entry>Offline only</entry>
</row>
<row>
<entry>OpenGFS</entry>
<entry>No</entry>
<entry>Online only</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
<para>You can perform all of the supported shrink and expand operations with each of the EVMS user interfaces.</para></sect1>
<sect1 id="exshrink"><title>Example: shrink a volume</title>
@ -289,4 +331,4 @@ value pair and an expandable object. To find the expand point, use the <command
</sect2>
</sect1>
</chapter>
</chapter>

21
LDP/guide/docbook/EVMSUG/fsimops-ug.xml
View File

@ -1,10 +1,10 @@
<chapter id="evmsfsimops"><title>FSIMs and file system operations</title>
<para>This chapter discusses the five File System Interface Modules (FSIMs) shipped with EVMS, and then provides examples of adding file systems and coordinating file system checks with the FSIMs.</para>
<para>This chapter discusses the six File System Interface Modules (FSIMs) shipped with EVMS, and then provides examples of adding file systems and coordinating file system checks with the FSIMs.</para>
<sect1 id="FSIMsuppevms"><title>The FSIMs supported by EVMS</title>
<para>EVMS currently ships with five FSIMs. These file system modules allow EVMS to interact with file system utilities such as <command>mkfs</command> and <command>fsck</command>. Additionally, the FSIMs ensure that EVMS safely performs operations, such as expanding and shrinking file systems, by coordinating these actions with the file system. </para>
<para>EVMS currently ships with six FSIMs. These file system modules allow EVMS to interact with file system utilities such as <command>mkfs</command> and <command>fsck</command>. Additionally, the FSIMs ensure that EVMS safely performs operations, such as expanding and shrinking file systems, by coordinating these actions with the file system. </para>
<para>You can invoke operations such as <command>mkfs</command> and <command>fsck</command> through the various EVMS user interfaces. Any actions you initiate through an FSIM are not committed to disk until the changes are saved in the user interface. Later in this chapter we provide examples of creating a new file system and coordinating file system checks through the EVMS GUI, Ncurses, and command-line interfaces.</para>
<para>The FSIMs supported by EVMS are:</para>
@ -14,6 +14,7 @@
<listitem><para>ReiserFS</para></listitem>
<listitem><para>Ext2/3</para></listitem>
<listitem><para>SWAPFS</para></listitem>
<listitem><para>OpenGFS</para></listitem>
</itemizedlist>
<sect2 id="fsimjfs"><title>JFS</title>
@ -53,7 +54,7 @@ This module supports <command>mkfs</command>, <command>unmkfs</command>, <comman
expansion and offline shrinkage. You need version 3.x.1a or higher
of the ReiserFS utilities for use with the EVMS FSIM modules. You can download
the ReiserFS utilities from <ulink url="http://www.namesys.com">The Naming
System Venture (Namesys) </ulink> web site.
System Venture (Namesys) </ulink> Web site.
</para>
<para>
@ -86,6 +87,20 @@ not in use.
</para>
</sect2>
<sect2 id="fsimopengfs"><title>OpenGFS</title>
<para>
The OpenGFS module supports the OpenGFS clustered journaling file system.
This module supports <command>mkfs</command>, <command>unmkfs</command>,
<command>fsck</command>, and online expansion.
You need the OpenGFS utilities for use with the EVMS FSIM module.
You can download the OpenGFS utilities from the
<ulink url="http://sourceforge.net/projects/opengfs">OpenGFS project on SourceForge</ulink>.
</para>
<para>
For more information on the OpenGFS FSIM, refer to <xref linkend="gfsfsim"></xref>.
</para>
</sect2>
</sect1>
<sect1 id="fsimmkfs"><title>Example: add a file system to a volume</title>

6
LDP/guide/docbook/EVMSUG/over-ug.xml
View File

@ -3,7 +3,8 @@
<para>EVMS brings a new model of volume management to Linux&reg;.
EVMS integrates all aspects of volume management,
such as disk partitioning, Linux logical volume manager (LVM) and
multi-disk (MD) management, OS2 and AIX volume managers, and file system operations into a single
multi-disk (MD) management, OS2 and AIX volume managers, and
file system operations into a single
cohesive package.
With EVMS, various volume management technologies are accessible through
one interface, and new technologies can be added as plug-ins as they are developed.</para>
@ -23,7 +24,8 @@ With EVMS, you can use multiple volume management technologies under one
framework while ensuring your system still interacts correctly with
stored data.
With EVMS, you are can use bad block relocation, shrink and expand volumes,
create snapshots of your volumes, and set up RAID (redundant array of independent devices) features for your system.
create snapshots of your volumes, and set up RAID
(redundant array of independent devices) features for your system.
You can also use many types of file systems and manipulate these storage pieces
in ways that best meet the needs of your particular work environment.</para>

6
LDP/guide/docbook/EVMSUG/pref-ug.xml
View File

@ -57,8 +57,8 @@ web site</ulink>.</para>
configuration of a volume or storage object.</entry></row>
<row><entry>21. Moving segment storage objects</entry><entry>Discusses how to use
the move function for moving segments.</entry></row>
<row><entry>A. The DOS link plug-in</entry>
<entry>Provides details about the DOS link plug-in, which is a segment manager plug-in.</entry></row>
<row><entry>A. The DOS plug-in</entry>
<entry>Provides details about the DOS plug-in, which is a segment manager plug-in.</entry></row>
<row><entry>B. The MD region manager</entry>
<entry>Explains the Multiple Disks (MD) support in Linux that is a software implementation of RAID.</entry></row>
<row><entry>C. The LVM plug-in</entry>
@ -73,6 +73,8 @@ the move function for moving segments.</entry></row>
<entry>Provides information about the ReiserFS FSIM.</entry></row>
<row><entry>H. Ext-2/3 file system interface module</entry>
<entry>Provides information about the Ext-2/3 FSIM.</entry></row>
<row><entry>I. OpenGFS file system interface module</entry>
<entry>Provides information about the OpenGFS FSIM.</entry></row>
</tbody></tgroup>
</table>
</preface>