File Formats volume-config(4)
NAME
volume-config - Solaris Volume Manager volume configuration
information for top down volume creation with metassist
SYNOPSIS
/usr/share/lib/xml/dtd/volume-config.dtd
DESCRIPTION
A volume configuration file, XML-based and compliant with
the volume-config.dtd Document Type Definition, describes
the detailed configuration of the volume or volumes to be
created, including the names, sizes and configurations of
all the components used in the volume or volumes. This con-
figuration file can be automatically generated by running
metassist with the -d option, or can be manually created.
The volume configuration file can then be used to either
generate a command file or to directly create volumes by
running metassist and specifying the volume configuration
file as input to the command.
As a system administrator, you would want to change, manu-
ally create, or edit the volume configuration file only if
there are small details of the configuration that you want
to change. For example, you might want to change names for
volumes or hot spare pools, mirror read option, or stripe
interlace values.
It would be possible to also select different devices or
change slice sizes or make similar changes, but that is gen-
erally not recommended. Substantial changes to the volume-
config file could result in a poor or non-functional confi-
guration.
With a volume-config file, you can run metassist and provide
the file as input to the command to generate either a com-
mand file or to actually set up the configuration.
Defining Volume Configuration
The top level element surrounds the volume
configuration data. This element has no attributes. A volume
configuration requires exactly one element, which
must be the first element of the volume configuration. Addi-
tionally, the volume-config can have zero or more of the
following elements: , , , ,
, as required to define the configuration
of the volume to be created.
SunOS 5.11 Last change: 8 Aug 2003 1
File Formats volume-config(4)
Defining Disk Set
Within the element, a element must
exist. The element, with the name attribute,
specifies the name of the diskset in which to create the
volume or volumes. This element and attribute are required.
If this named disk set does not exist, it is created upon
implementation of this volume configuration.
Defining Slice
The volume configuration format provides for a ele-
ment that defines the name of a slice to use as a component
of a volume. The element requires a name attribute
which specifies a full ctd name. If the is newly
created as part of the volume configuration, the startsector
and sizeinblocks attributes must be specified. If the slice
was previously existing, these attributes need not be speci-
fied.
Defining Hot Spare Pool
The volume configuration format provides for a element
that defines the name of a hot spare pool to use as a com-
ponent of a configuration. The element requires a name
attribute which specifies a hot spare pool name.
Slices defined by elements contained in the
element are included in the hot spare pool when metassist
creates it."
Defining Stripe
The element defines stripes (interlaced RAID 0
volumes) to be used in a volume. The element takes
a required name attribute to specify a name conforming to
Solaris Volume Manager naming requirements. If the name
specifies an existing stripe, no elements are
required. If the name specifies a new stripe, the
elements to construct the slice must be specified within the
element. The elements takes an optional
interlace attribute as value and units (for example, 16KB,
5BLOCKS, 20MB). If this value isn't specified, the Solaris
Volume Manager default value is used.
Defining Concat
The element defines concats (non-interlaced RAID 0
volumes) to be used in a configuration. It is the same as a
element, except that the interlace attribute is not
valid.
Defining Mirror
The element defines mirrors (RAID 1 volumes) to be
used in a volume configuration. It can contain combinations
of and elements (to explicitly determine
SunOS 5.11 Last change: 8 Aug 2003 2
File Formats volume-config(4)
which volumes are used as submirrors).
The element takes a required name attribute to
specify a name conforming to Solaris Volume Manager naming
requirements.
The element takes an optional read attribute to
define the mirror read options (ROUNDROBIN, GEOMETRIC, or
FIRST) for the mirrors. If this attribute is not specified,
the Solaris Volume Manager default value is used.
The element takes an optional write attribute to
define the mirror write options (PARALEL, SERIAL, or FIRST)
for the mirrors. If this attribute is not specified, the
Solaris Volume Manager default value is used. The
element takes an optional passnum attribute (0-9) to define
the mirror passnum that defines the order in which mirrors
are resynced at boot, if required. Smaller numbers are
resynced first. If this attribute is not specified, the
Solaris Volume Manager default value is used.
EXAMPLES
Example 1 Specifying a Volume Configuration
The following is an example volume configuration:
hsp name="hsp0">
SunOS 5.11 Last change: 8 Aug 2003 3
File Formats volume-config(4)
slice name="/dev/dsk/c0t0d3s7"/>
FILES
/usr/share/lib/xml/dtd/volume-config.dtd
SEE ALSO
metassist(1M), metaclear(1M), metadb(1M), metadetach(1M),
metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M),
metaparam(1M), metarecover(1M), metareplace(1M),
metaroot(1M), metaset(1M), metasync(1M), metattach(1M),
mountufs(1M), mddb.cf(4)
SunOS 5.11 Last change: 8 Aug 2003 4
File Formats volume-config(4)
Solaris Volume Manager Administration Guide
SunOS 5.11 Last change: 8 Aug 2003 5
|
