Installation guide

3. fs: 1 — This is a File System resource. If there were other File System resources in Service
foo, they would stop in the reverse order listed in the Service foo portion of
/etc/cl uster/cl uster.co nf.
4. lvm: 2 — This is an LVM resource. All LVM resources are stopped last. l vm: 2 (<lvm
name= "2" . . . />) is stopped before lvm: 1; resources within a group of a resource type
are stopped in the reverse order listed in the Service foo portion of
/etc/cl uster/cl uster.co nf.
5. l vm: 1 — This is an LVM resource. All LVM resources are stopped last. l vm: 1 (<l vm
name= "1" . . . />) is stopped after l vm: 2; resources within a group of a resource type are
stopped in the reverse order listed in the Service foo portion of
/etc/cl uster/cl uster.co nf.
C.2.2. Non-t yped Child Resource St art and St op Ordering
Additional considerations are required for non-typed child resources. For a non-typed child
resource, starting order and stopping order are not explicitly specified by the Service resource.
Instead, starting order and stopping order are determined according to the order of the child
resource in /etc/cl uster/cl uster.co nf. Additionally, non-typed child resources are started
after all typed child resources and stopped before any typed child resources.
For example, consider the starting order and stopping order of the non-typed child resources in
Example C.4, “ Non-typed and Typed Child Resource in a Service” .
Examp le C.4 . No n - t yp ed an d T yp ed C h ild Reso u rce in a Service
<service name="foo">
<script name="1" .../>
<nontypedresource name="foo"/>
<lvm name="1" .../>
<nontypedresourcetwo name="bar"/>
<ip address="10.1.1.1" .../>
<fs name="1" .../>
<lvm name="2" .../>
</service>
Non-typed Child Resource Starting Order
In Example C.4, “Non-typed and Typed Child Resource in a Service” , the child resources are started
in the following order:
1. lvm: 1 — This is an LVM resource. All LVM resources are started first. lvm: 1 (<lvm
name= "1" . . . />) is the first LVM resource started among LVM resources because it is the
first LVM resource listed in the Service foo portion of /etc/cluster/cluster. co nf.
2. l vm: 2 — This is an LVM resource. All LVM resources are started first. lvm: 2 (<lvm
name= "2" . . . />) is started after lvm: 1 because it is listed after l vm: 1 in the Service foo
portion of /etc/cluster/cluster. co nf.
3. fs: 1 — This is a File System resource. If there were other File System resources in Service
foo, they would start in the order listed in the Service foo portion of
/etc/cl uster/cl uster.co nf.
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
210