The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: sect2/para
Context English State
Must be equal size
Large data storage with maximum placement flexibility and moderate performance
High performance in combination with highly concurrent access
Some Examples
<filename>vinum</filename> maintains a <emphasis>configuration database</emphasis> which describes the objects known to an individual system. Initially, the user creates the configuration database from one or more configuration files using <citerefentry><refentrytitle>gvinum</refentrytitle><manvolnum>8</manvolnum></citerefentry>. <filename>vinum</filename> stores a copy of its configuration database on each disk <emphasis>device</emphasis> under its control. This database is updated on each state change, so that a restart accurately restores the state of each <filename>vinum</filename> object.
The Configuration File
The configuration file describes individual <filename>vinum</filename> objects. The definition of a simple volume might be:
drive a device /dev/da3h
volume myvol
plex org concat
sd length 512m drive a
This file describes four <filename>vinum</filename> objects:
The <emphasis>drive</emphasis> line describes a disk partition (<emphasis>drive</emphasis>) and its location relative to the underlying hardware. It is given the symbolic name <emphasis>a</emphasis>. This separation of symbolic names from device names allows disks to be moved from one location to another without confusion.
The <emphasis>volume</emphasis> line describes a volume. The only required attribute is the name, in this case <emphasis>myvol</emphasis>.
The <emphasis>plex</emphasis> line defines a plex. The only required parameter is the organization, in this case <emphasis>concat</emphasis>. No name is necessary as the system automatically generates a name from the volume name by adding the suffix <emphasis>.p</emphasis><emphasis>x</emphasis>, where <emphasis>x</emphasis> is the number of the plex in the volume. Thus this plex will be called <emphasis>myvol.p0</emphasis>.
The <emphasis>sd</emphasis> line describes a subdisk. The minimum specifications are the name of a drive on which to store it, and the length of the subdisk. No name is necessary as the system automatically assigns names derived from the plex name by adding the suffix <emphasis>.s</emphasis><emphasis>x</emphasis>, where <emphasis>x</emphasis> is the number of the subdisk in the plex. Thus <filename>vinum</filename> gives this subdisk the name <emphasis>myvol.p0.s0</emphasis>.
After processing this file, <citerefentry><refentrytitle>gvinum</refentrytitle><manvolnum>8</manvolnum></citerefentry> produces the following output:

<prompt>#</prompt> gvinum -&gt; <userinput>create config1</userinput>
Configuration summary
Drives: 1 (4 configured)
Volumes: 1 (4 configured)
Plexes: 1 (8 configured)
Subdisks: 1 (16 configured)

D a State: up Device /dev/da3h Avail: 2061/2573 MB (80%)

V myvol State: up Plexes: 1 Size: 512 MB

P myvol.p0 C State: up Subdisks: 1 Size: 512 MB

S myvol.p0.s0 State: up PO: 0 B Size: 512 MB
This output shows the brief listing format of <citerefentry><refentrytitle>gvinum</refentrytitle><manvolnum>8</manvolnum></citerefentry>. It is represented graphically in <xref linkend="vinum-simple-vol"/>.
A Simple <filename>vinum</filename> Volume
_ external ref='vinum-simple-vol' md5='__failed__'
This figure, and the ones which follow, represent a volume, which contains the plexes, which in turn contains the subdisks. In this example, the volume contains one plex, and the plex contains one subdisk.
This particular volume has no specific advantage over a conventional disk partition. It contains a single plex, so it is not redundant. The plex contains a single subdisk, so there is no difference in storage allocation from a conventional disk partition. The following sections illustrate various more interesting configuration methods.
Increased Resilience: Mirroring
The resilience of a volume can be increased by mirroring. When laying out a mirrored volume, it is important to ensure that the subdisks of each plex are on different drives, so that a drive failure will not take down both plexes. The following configuration mirrors a volume:
drive b device /dev/da4h
volume mirror
plex org concat
sd length 512m drive a
plex org concat
sd length 512m drive b
In this example, it was not necessary to specify a definition of drive <emphasis>a</emphasis> again, since <filename>vinum</filename> keeps track of all objects in its configuration database. After processing this definition, the configuration looks like:


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: sect2/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/vinum.pot, string 78