1volume-config(4) File Formats volume-config(4)
2
6 volume-config - Solaris Volume Manager volume configuration information
7 for top down volume creation with metassist
8
10 /usr/share/lib/xml/dtd/volume-config.dtd
11
14 A volume configuration file, XML-based and compliant with the volume-
15 config.dtd Document Type Definition, describes the detailed configura‐
16 tion of the volume or volumes to be created, including the names, sizes
17 and configurations of all the components used in the volume or volumes.
18 This configuration file can be automatically generated by running
19 metassist with the -d option, or can be manually created.
20 The volume configuration file can then be used to either generate a
23 command file or to directly create volumes by running metassist and
24 specifying the volume configuration file as input to the command.
25 As a system administrator, you would want to change, manually create,
28 or edit the volume configuration file only if there are small details
29 of the configuration that you want to change. For example, you might
30 want to change names for volumes or hot spare pools, mirror read
31 option, or stripe interlace values.
32 It would be possible to also select different devices or change slice
35 sizes or make similar changes, but that is generally not recommended.
36 Substantial changes to the volume-config file could result in a poor or
37 non-functional configuration.
38 With a volume-config file, you can run metassist and provide the file
41 as input to the command to generate either a command file or to actu‐
42 ally set up the configuration.
43 Defining Volume Configuration
45 The top level element <volume-config> surrounds the volume configura‐
46 tion data. This element has no attributes. A volume configuration
47 requires exactly one <diskset> element, which must be the first element
48 of the volume configuration. Additionally, the volume-config can have
49 zero or more of the following elements: <disk>, <slice>, <hsp>, <con‐
50 cat>, <stripe>, <mirror> as required to define the configuration of
51 the volume to be created.
52 Defining Disk Set
54 Within the <volume-config> element, a <diskset> element must exist. The
55 <diskset> element, with the name attribute, specifies the name of the
56 diskset in which to create the volume or volumes. This element and
57 attribute are required. If this named disk set does not exist, it is
58 created upon implementation of this volume configuration.
59 Defining Slice
61 The volume configuration format provides for a <slice> element that
62 defines the name of a slice to use as a component of a volume. The
63 <slice> element requires a name attribute which specifies a full ctd
64 name. If the <slice> is newly created as part of the volume configura‐
65 tion, the startsector and sizeinblocks attributes must be specified. If
66 the slice was previously existing, these attributes need not be speci‐
67 fied.
68 Defining Hot Spare Pool
70 The volume configuration format provides for a <hsp> element that
71 defines the name of a hot spare pool to use as a component of a config‐
72 uration. The <hsp> element requires a name attribute which specifies a
73 hot spare pool name.
74 Slices defined by <slice> elements contained in the <hsp> element are
77 included in the hot spare pool when metassist creates it."
78 Defining Stripe
80 The <stripe> element defines stripes (interlaced RAID 0 volumes) to be
81 used in a volume. The <stripe> element takes a required name attribute
82 to specify a name conforming to Solaris Volume Manager naming require‐
83 ments. If the name specifies an existing stripe, no <slice> elements
84 are required. If the name specifies a new stripe, the <slice> elements
85 to construct the slice must be specified within the <stripe> element.
86 The <stripe> elements takes an optional interlace attribute as value
87 and units (for example, 16KB, 5BLOCKS, 20MB). If this value isn't spec‐
88 ified, the Solaris Volume Manager default value is used.
89 Defining Concat
91 The <concat> element defines concats (non-interlaced RAID 0 volumes) to
92 be used in a configuration. It is the same as a <stripe> element,
93 except that the interlace attribute is not valid.
94 Defining Mirror
96 The <mirror> element defines mirrors (RAID 1 volumes) to be used in a
97 volume configuration. It can contain combinations of <concat> and
98 <stripe> elements (to explicitly determine which volumes are used as
99 submirrors).
100 The <mirror> element takes a required name attribute to specify a name
103 conforming to Solaris Volume Manager naming requirements.
104 The <mirror> element takes an optional read attribute to define the
107 mirror read options (ROUNDROBIN, GEOMETRIC, or FIRST) for the mirrors.
108 If this attribute is not specified, the Solaris Volume Manager default
109 value is used.
110 The <mirror> element takes an optional write attribute to define the
113 mirror write options (PARALLEL, SERIAL, or FIRST) for the mirrors. If
114 this attribute is not specified, the Solaris Volume Manager default
115 value is used. The <mirror> element takes an optional passnum attribute
116 (0-9) to define the mirror passnum that defines the order in which mir‐
117 rors are resynced at boot, if required. Smaller numbers are resynced
118 first. If this attribute is not specified, the Solaris Volume Manager
119 default value is used.
120
122 Example 1 Specifying a Volume Configuration
123 The following is an example volume configuration:
126 <!-- Example configuration -->
129 <volume-config>
130 <!-- Specify the existing disk set to use -->
131 <diskset name="redundant"/>
132 <!-- Create slices -->
134 <slice name="/dev/dsk/c0t0d1s7" startsector="1444464" \
135 sizeinblocks="205632BLOCKS"/>
136 <slice name="/dev/dsk/c0t0d1s6" startsector="1239840" \
137 sizeinblocks="102816KB"/>
138 <!-- Create a concat -->
140 <concat name="d12">
141 <slice name="/dev/dsk/c0t0d0s7"/>
142 <slice name="/dev/dsk/c0t0d0s6"/>
143 <slice name="/dev/dsk/c0t0d1s7"/>
144 <slice name="/dev/dsk/c0t0d1s6"/>
145 <!-- Create (and use) a HSP -->
147 hsp name="hsp0">
148 <slice name="/dev/dsk/c0t0d4s0"/>
149 <slice name="/dev/dsk/c0t0d4s1"/>
150 <slice name="/dev/dsk/c0t0d4s3"/>
151 <slice name="/dev/dsk/c0t0d4s4"/>
152 </hsp>
153 </concat>
155 <!-- Create a stripe -->
157 <stripe name="d15" interlace="32KB">
158 <slice name="/dev/dsk/c0t0d0s7"/>
159 <slice name="/dev/dsk/c0t0d1s7"/>
160 <!-- Use a previously-defined HSP -->
162 <hsp name="hsp0"/>
163 </stripe>
164 <!-- Create a mirror -->
166 <mirror name="d10">
167 <!-- Submirror 1: An existing stripe -->
169 <stripe name="d11"/>
170 <!-- Submirror 2: The concat defined above -->
172 <concat name="d12"/>
173 <!-- Submirror 3: A stripe defined here -->
175 <stripe name="d13">
176 <slice name="/dev/dsk/c0t0d2s6"/>
177 <slice name="/dev/dsk/c0t0d2s7"/>
178 <slice name="/dev/dsk/c0t0d3s6"/>
179 slice name="/dev/dsk/c0t0d3s7"/>
180 </stripe>
181 </mirror>
183 </volume-config>
185
188 /usr/share/lib/xml/dtd/volume-config.dtd
189
194 metassist(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M),
195 metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metare‐
196 cover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M),
197 metattach(1M), mount_ufs(1M), mddb.cf(4)
198 Solaris Volume Manager Administration Guide
201SunOS 5.11 8 Aug 2003 volume-config(4)