#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2018-12-08 14:45-0200\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""

#. (itstool) path: info/title
#: article.translate.xml:16
msgid "The <filename>vinum</filename> Volume Manager"
msgstr ""

#. (itstool) path: authorgroup/author
#: article.translate.xml:19
msgid ""
"<personname> <firstname>Greg</firstname> <surname>Lehey</surname> </"
"personname> <contrib>Originally written by </contrib>"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:30
msgid "Synopsis"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:32
msgid ""
"No matter the type of disks, there are always potential problems. The disks "
"can be too small, too slow, or too unreliable to meet the system's "
"requirements. While disks are getting bigger, so are data storage "
"requirements. Often a file system is needed that is bigger than a disk's "
"capacity. Various solutions to these problems have been proposed and "
"implemented."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:40
msgid ""
"One method is through the use of multiple, and sometimes redundant, disks. "
"In addition to supporting various cards and controllers for hardware "
"Redundant Array of Independent Disks <acronym>RAID</acronym> systems, the "
"base FreeBSD system includes the <filename>vinum</filename> volume manager, "
"a block device driver that implements virtual disk drives and addresses "
"these three problems. <filename>vinum</filename> provides more flexibility, "
"performance, and reliability than traditional disk storage and implements "
"<acronym>RAID</acronym>-0, <acronym>RAID</acronym>-1, and <acronym>RAID</"
"acronym>-5 models, both individually and in combination."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:53
msgid ""
"This chapter provides an overview of potential problems with traditional "
"disk storage, and an introduction to the <filename>vinum</filename> volume "
"manager."
msgstr ""

#. (itstool) path: note/para
#: article.translate.xml:58
msgid ""
"Starting with FreeBSD 5, <filename>vinum</filename> has been rewritten in "
"order to fit into the <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-"
"1/books/handbook/geom.html\">GEOM architecture</link>, while retaining the "
"original ideas, terminology, and on-disk metadata. This rewrite is called "
"<emphasis>gvinum</emphasis> (for <emphasis> GEOM vinum</emphasis>). While "
"this chapter uses the term <filename>vinum</filename>, any command "
"invocations should be performed with <command>gvinum</command>. The name of "
"the kernel module has changed from the original <filename>vinum.ko</"
"filename> to <filename>geom_vinum.ko</filename>, and all device nodes reside "
"under <filename class=\"directory\">/dev/gvinum</filename> instead of "
"<filename class=\"directory\">/dev/vinum</filename>. As of FreeBSD 6, the "
"original <filename>vinum</filename> implementation is no longer available in "
"the code base."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:76
msgid "Access Bottlenecks"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:78
msgid ""
"Modern systems frequently need to access data in a highly concurrent manner. "
"For example, large FTP or HTTP servers can maintain thousands of concurrent "
"sessions and have multiple 100 Mbit/s connections to the outside world, well "
"beyond the sustained transfer rate of most disks."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:84
msgid ""
"Current disk drives can transfer data sequentially at up to 70 MB/s, but "
"this value is of little importance in an environment where many independent "
"processes access a drive, and where they may achieve only a fraction of "
"these values. In such cases, it is more interesting to view the problem from "
"the viewpoint of the disk subsystem. The important parameter is the load "
"that a transfer places on the subsystem, or the time for which a transfer "
"occupies the drives involved in the transfer."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:94
msgid ""
"In any disk transfer, the drive must first position the heads, wait for the "
"first sector to pass under the read head, and then perform the transfer. "
"These actions can be considered to be atomic as it does not make any sense "
"to interrupt them."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:100
msgid ""
"<anchor xml:id=\"vinum-latency\"/> Consider a typical transfer of about "
"10 kB: the current generation of high-performance disks can position the "
"heads in an average of 3.5 ms. The fastest drives spin at 15,000 rpm, so the "
"average rotational latency (half a revolution) is 2 ms. At 70 MB/s, the "
"transfer itself takes about 150 μs, almost nothing compared to the "
"positioning time. In such a case, the effective transfer rate drops to a "
"little over 1 MB/s and is clearly highly dependent on the transfer size."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:111
msgid ""
"The traditional and obvious solution to this bottleneck is <quote>more "
"spindles</quote>: rather than using one large disk, use several smaller "
"disks with the same aggregate storage space. Each disk is capable of "
"positioning and transferring independently, so the effective throughput "
"increases by a factor close to the number of disks used."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:118
msgid ""
"The actual throughput improvement is smaller than the number of disks "
"involved. Although each drive is capable of transferring in parallel, there "
"is no way to ensure that the requests are evenly distributed across the "
"drives. Inevitably the load on one drive will be higher than on another."
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:124
msgid "<primary>disk concatenation</primary>"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:127
msgid "<primary>Vinum</primary> <secondary>concatenation</secondary>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:132
msgid ""
"The evenness of the load on the disks is strongly dependent on the way the "
"data is shared across the drives. In the following discussion, it is "
"convenient to think of the disk storage as a large number of data sectors "
"which are addressable by number, rather like the pages in a book. The most "
"obvious method is to divide the virtual disk into groups of consecutive "
"sectors the size of the individual physical disks and store them in this "
"manner, rather like taking a large book and tearing it into smaller sections."
" This method is called <emphasis>concatenation</emphasis> and has the "
"advantage that the disks are not required to have any specific size "
"relationships. It works well when the access to the virtual disk is spread "
"evenly about its address space. When access is concentrated on a smaller "
"area, the improvement is less marked. <xref linkend=\"vinum-concat\"/> "
"illustrates the sequence in which storage units are allocated in a "
"concatenated organization."
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:152
msgid "Concatenated Organization"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:156
msgctxt "_"
msgid "external ref='vinum-concat' md5='__failed__'"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:161
msgid "<primary>disk striping</primary>"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:164
msgid "<primary>Vinum</primary> <secondary>striping</secondary>"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:168
msgid "<primary><acronym>RAID</acronym></primary>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:172
msgid ""
"An alternative mapping is to divide the address space into smaller, equal-"
"sized components and store them sequentially on different devices. For "
"example, the first 256 sectors may be stored on the first disk, the next 256 "
"sectors on the next disk and so on. After filling the last disk, the process "
"repeats until the disks are full. This mapping is called <emphasis>striping</"
"emphasis> or <acronym>RAID-0</acronym>."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:181
msgid ""
"<acronym>RAID</acronym> offers various forms of fault tolerance, though "
"<acronym>RAID-0</acronym> is somewhat misleading as it provides no "
"redundancy. Striping requires somewhat more effort to locate the data, and "
"it can cause additional I/O load where a transfer is spread over multiple "
"disks, but it can also provide a more constant load across the disks. <xref "
"linkend=\"vinum-striped\"/> illustrates the sequence in which storage units "
"are allocated in a striped organization."
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:193
msgid "Striped Organization"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:197
msgctxt "_"
msgid "external ref='vinum-striped' md5='__failed__'"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:204
msgid "Data Integrity"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:206
msgid ""
"The final problem with disks is that they are unreliable. Although "
"reliability has increased tremendously over the last few years, disk drives "
"are still the most likely core component of a server to fail. When they do, "
"the results can be catastrophic and replacing a failed disk drive and "
"restoring data can result in server downtime."
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:213
msgid "<primary>disk mirroring</primary>"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:216
msgid "<primary>vinum</primary> <secondary>mirroring</secondary>"
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:219
msgid "<primary><acronym>RAID</acronym>-1</primary>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:222
msgid ""
"One approach to this problem is <emphasis>mirroring</emphasis>, or "
"<acronym>RAID-1</acronym>, which keeps two copies of the data on different "
"physical hardware. Any write to the volume writes to both disks; a read can "
"be satisfied from either, so if one drive fails, the data is still available "
"on the other drive."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:230
msgid "Mirroring has two problems:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:234
msgid "It requires twice as much disk storage as a non-redundant solution."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:239
msgid ""
"Writes must be performed to both drives, so they take up twice the bandwidth "
"of a non-mirrored volume. Reads do not suffer from a performance penalty and "
"can even be faster."
msgstr ""

#. (itstool) path: sect1/indexterm
#: article.translate.xml:246
msgid "<primary><acronym>RAID</acronym>-5</primary>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:248
msgid ""
"An alternative solution is <emphasis>parity</emphasis>, implemented in "
"<acronym>RAID</acronym> levels 2, 3, 4 and 5. Of these, <acronym>RAID-5</"
"acronym> is the most interesting. As implemented in <filename>vinum</"
"filename>, it is a variant on a striped organization which dedicates one "
"block of each stripe to parity one of the other blocks. As implemented by "
"<filename>vinum</filename>, a <acronym>RAID-5</acronym> plex is similar to a "
"striped plex, except that it implements <acronym>RAID-5</acronym> by "
"including a parity block in each stripe. As required by <acronym>RAID-5</"
"acronym>, the location of this parity block changes from one stripe to the "
"next. The numbers in the data blocks indicate the relative block numbers."
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:264
msgid "<acronym>RAID</acronym>-5 Organization"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:268
msgctxt "_"
msgid "external ref='vinum-raid5-org' md5='__failed__'"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:273
msgid ""
"Compared to mirroring, <acronym>RAID-5</acronym> has the advantage of "
"requiring significantly less storage space. Read access is similar to that "
"of striped organizations, but write access is significantly slower, "
"approximately 25% of the read performance. If one drive fails, the array can "
"continue to operate in degraded mode where a read from one of the remaining "
"accessible drives continues normally, but a read from the failed drive is "
"recalculated from the corresponding block from all the remaining drives."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:285
msgid "<filename>vinum</filename> Objects"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:287
msgid ""
"In order to address these problems, <filename>vinum</filename> implements a "
"four-level hierarchy of objects:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:293
msgid ""
"The most visible object is the virtual disk, called a <emphasis>volume</"
"emphasis>. Volumes have essentially the same properties as a <trademark "
"class=\"registered\">UNIX</trademark> disk drive, though there are some "
"minor differences. For one, they have no size limitations."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:301
msgid ""
"Volumes are composed of <emphasis>plexes</emphasis>, each of which represent "
"the total address space of a volume. This level in the hierarchy provides "
"redundancy. Think of plexes as individual disks in a mirrored array, each "
"containing the same data."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:309
msgid ""
"Since <filename>vinum</filename> exists within the <trademark class="
"\"registered\">UNIX</trademark> disk storage framework, it would be possible "
"to use <trademark class=\"registered\">UNIX</trademark> partitions as the "
"building block for multi-disk plexes. In fact, this turns out to be too "
"inflexible as <trademark class=\"registered\">UNIX</trademark> disks can "
"have only a limited number of partitions. Instead, <filename>vinum</"
"filename> subdivides a single <trademark class=\"registered\">UNIX</"
"trademark> partition, the <emphasis>drive</emphasis>, into contiguous areas "
"called <emphasis>subdisks</emphasis>, which are used as building blocks for "
"plexes."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:321
msgid ""
"Subdisks reside on <filename>vinum</filename> <emphasis>drives</emphasis>, "
"currently <trademark class=\"registered\">UNIX</trademark> partitions. "
"<filename>vinum</filename> drives can contain any number of subdisks. With "
"the exception of a small area at the beginning of the drive, which is used "
"for storing configuration and state information, the entire drive is "
"available for data storage."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:331
msgid ""
"The following sections describe the way these objects provide the "
"functionality required of <filename>vinum</filename>."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:336
msgid "Volume Size Considerations"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:338
msgid ""
"Plexes can include multiple subdisks spread over all drives in the "
"<filename>vinum</filename> configuration. As a result, the size of an "
"individual drive does not limit the size of a plex or a volume."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:345
msgid "Redundant Data Storage"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:347
msgid ""
"<filename>vinum</filename> implements mirroring by attaching multiple plexes "
"to a volume. Each plex is a representation of the data in a volume. A volume "
"may contain between one and eight plexes."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:352
msgid ""
"Although a plex represents the complete data of a volume, it is possible for "
"parts of the representation to be physically missing, either by design (by "
"not defining a subdisk for parts of the plex) or by accident (as a result of "
"the failure of a drive). As long as at least one plex can provide the data "
"for the complete address range of the volume, the volume is fully functional."
""
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:362
msgid "Which Plex Organization?"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:364
msgid ""
"<filename>vinum</filename> implements both concatenation and striping at the "
"plex level:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:369
msgid ""
"A <emphasis>concatenated plex</emphasis> uses the address space of each "
"subdisk in turn. Concatenated plexes are the most flexible as they can "
"contain any number of subdisks, and the subdisks may be of different length. "
"The plex may be extended by adding additional subdisks. They require less "
"<acronym>CPU</acronym> time than striped plexes, though the difference in "
"<acronym>CPU</acronym> overhead is not measurable. On the other hand, they "
"are most susceptible to hot spots, where one disk is very active and others "
"are idle."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:382
msgid ""
"A <emphasis>striped plex</emphasis> stripes the data across each subdisk. "
"The subdisks must all be the same size and there must be at least two "
"subdisks in order to distinguish it from a concatenated plex. The greatest "
"advantage of striped plexes is that they reduce hot spots. By choosing an "
"optimum sized stripe, about 256 kB, the load can be evened out on the "
"component drives. Extending a plex by adding new subdisks is so complicated "
"that <filename>vinum</filename> does not implement it."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:395
msgid ""
"<xref linkend=\"vinum-comparison\"/> summarizes the advantages and "
"disadvantages of each plex organization."
msgstr ""

#. (itstool) path: table/title
#: article.translate.xml:399
msgid "<filename>vinum</filename> Plex Organizations"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:405
msgid "Plex type"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:406
msgid "Minimum subdisks"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:407
msgid "Can add subdisks"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:408
msgid "Must be equal size"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:409
msgid "Application"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:415
msgid "concatenated"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:416
msgid "1"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:417 article.translate.xml:427
msgid "yes"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:418 article.translate.xml:426
msgid "no"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:419
msgid ""
"Large data storage with maximum placement flexibility and moderate "
"performance"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:424
msgid "striped"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:425
msgid "2"
msgstr ""

#. (itstool) path: row/entry
#: article.translate.xml:428
msgid "High performance in combination with highly concurrent access"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:438
msgid "Some Examples"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:440
msgid ""
"<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."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:453
msgid "The Configuration File"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:455
msgid ""
"The configuration file describes individual <filename>vinum</filename> "
"objects. The definition of a simple volume might be:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:459
#, no-wrap
msgid ""
"    drive a device /dev/da3h\n"
"    volume myvol\n"
"      plex org concat\n"
"        sd length 512m drive a"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:464
msgid "This file describes four <filename>vinum</filename> objects:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:469
msgid ""
"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."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:478
msgid ""
"The <emphasis>volume</emphasis> line describes a volume. The only required "
"attribute is the name, in this case <emphasis>myvol</emphasis>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:484
msgid ""
"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>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:496
msgid ""
"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>."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:508
msgid ""
"After processing this file, <citerefentry><refentrytitle>gvinum</"
"refentrytitle><manvolnum>8</manvolnum></citerefentry> produces the following "
"output:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:511
#, no-wrap
msgid ""
"\n"
"<prompt>#</prompt> gvinum -&gt; <userinput>create config1</userinput>\n"
"Configuration summary\n"
"Drives:         1 (4 configured)\n"
"Volumes:        1 (4 configured)\n"
"Plexes:         1 (8 configured)\n"
"Subdisks:       1 (16 configured)\n"
"\n"
"  D a                     State: up       Device /dev/da3h      Avail: 2061/"
"2573 MB (80%)\n"
"\n"
"  V myvol                 State: up       Plexes:       1 Size:      512 MB\n"
"\n"
"  P myvol.p0            C State: up       Subdisks:     1 Size:      512 MB\n"
"\n"
"  S myvol.p0.s0           State: up       PO:        0  B Size:      512 MB"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:527
msgid ""
"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\"/>."
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:532
msgid "A Simple <filename>vinum</filename> Volume"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:537
msgctxt "_"
msgid "external ref='vinum-simple-vol' md5='__failed__'"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:542
msgid ""
"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."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:547
msgid ""
"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."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:557
msgid "Increased Resilience: Mirroring"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:559
msgid ""
"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:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:565
#, no-wrap
msgid ""
"	drive b device /dev/da4h\n"
"	volume mirror\n"
"      plex org concat\n"
"        sd length 512m drive a\n"
"	  plex org concat\n"
"	    sd length 512m drive b"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:572
msgid ""
"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:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:578
#, no-wrap
msgid ""
"\n"
"	Drives:         2 (4 configured)\n"
"	Volumes:        2 (4 configured)\n"
"	Plexes:         3 (8 configured)\n"
"	Subdisks:       3 (16 configured)\n"
"\n"
"	D a                     State: up       Device /dev/da3h       Avail: 1549/"
"2573 MB (60%)\n"
"	D b                     State: up       Device /dev/da4h       Avail: 2061/"
"2573 MB (80%)\n"
"\n"
"    V myvol                 State: up       Plexes:       1 Size:        512 "
"MB\n"
"    V mirror                State: up       Plexes:       2 Size:        512 "
"MB\n"
"\n"
"    P myvol.p0            C State: up       Subdisks:     1 Size:        512 "
"MB\n"
"    P mirror.p0           C State: up       Subdisks:     1 Size:        512 "
"MB\n"
"    P mirror.p1           C State: initializing     Subdisks:     1 Size:    "
"    512 MB\n"
"\n"
"    S myvol.p0.s0           State: up       PO:        0  B Size:        512 "
"MB\n"
"	S mirror.p0.s0          State: up       PO:        0  B Size:        512 MB\n"
"	S mirror.p1.s0          State: empty    PO:        0  B Size:        512 MB"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:598
msgid "<xref linkend=\"vinum-mirrored-vol\"/> shows the structure graphically."
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:603
msgid "A Mirrored <filename>vinum</filename> Volume"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:608
msgctxt "_"
msgid "external ref='vinum-mirrored-vol' md5='__failed__'"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:613
msgid ""
"In this example, each plex contains the full 512 MB of address space. As in "
"the previous example, each plex contains only a single subdisk."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:619
msgid "Optimizing Performance"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:621
msgid ""
"The mirrored volume in the previous example is more resistant to failure "
"than an unmirrored volume, but its performance is less as each write to the "
"volume requires a write to both drives, using up a greater proportion of the "
"total disk bandwidth. Performance considerations demand a different approach:"
" instead of mirroring, the data is striped across as many disk drives as "
"possible. The following configuration shows a volume with a plex striped "
"across four disk drives:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:631
#, no-wrap
msgid ""
"        drive c device /dev/da5h\n"
"	drive d device /dev/da6h\n"
"	volume stripe\n"
"	plex org striped 512k\n"
"	  sd length 128m drive a\n"
"	  sd length 128m drive b\n"
"	  sd length 128m drive c\n"
"	  sd length 128m drive d"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:640
msgid ""
"As before, it is not necessary to define the drives which are already known "
"to <filename>vinum</filename>. After processing this definition, the "
"configuration looks like:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:645
#, no-wrap
msgid ""
"\n"
"	Drives:         4 (4 configured)\n"
"	Volumes:        3 (4 configured)\n"
"	Plexes:         4 (8 configured)\n"
"	Subdisks:       7 (16 configured)\n"
"\n"
"    D a                     State: up       Device /dev/da3h        Avail: "
"1421/2573 MB (55%)\n"
"    D b                     State: up       Device /dev/da4h        Avail: "
"1933/2573 MB (75%)\n"
"    D c                     State: up       Device /dev/da5h        Avail: "
"2445/2573 MB (95%)\n"
"    D d                     State: up       Device /dev/da6h        Avail: "
"2445/2573 MB (95%)\n"
"\n"
"    V myvol                 State: up       Plexes:       1 Size:        512 "
"MB\n"
"    V mirror                State: up       Plexes:       2 Size:        512 "
"MB\n"
"    V striped               State: up       Plexes:       1 Size:        512 "
"MB\n"
"\n"
"    P myvol.p0            C State: up       Subdisks:     1 Size:        512 "
"MB\n"
"    P mirror.p0           C State: up       Subdisks:     1 Size:        512 "
"MB\n"
"    P mirror.p1           C State: initializing     Subdisks:     1 Size:    "
"    512 MB\n"
"    P striped.p1            State: up       Subdisks:     1 Size:        512 "
"MB\n"
"\n"
"    S myvol.p0.s0           State: up       PO:        0  B Size:        512 "
"MB\n"
"    S mirror.p0.s0          State: up       PO:        0  B Size:        512 "
"MB\n"
"    S mirror.p1.s0          State: empty    PO:        0  B Size:        512 "
"MB\n"
"    S striped.p0.s0         State: up       PO:        0  B Size:        128 "
"MB\n"
"    S striped.p0.s1         State: up       PO:      512 kB Size:        128 "
"MB\n"
"    S striped.p0.s2         State: up       PO:     1024 kB Size:        128 "
"MB\n"
"    S striped.p0.s3         State: up       PO:     1536 kB Size:        128 "
"MB"
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:675
msgid "A Striped <filename>vinum</filename> Volume"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:680
msgctxt "_"
msgid "external ref='vinum-striped-vol' md5='__failed__'"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:685
msgid ""
"This volume is represented in <xref linkend=\"vinum-striped-vol\"/>. The "
"darkness of the stripes indicates the position within the plex address "
"space, where the lightest stripes come first and the darkest last."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:692
msgid "Resilience and Performance"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:694
msgid ""
"<anchor xml:id=\"vinum-resilience\"/>With sufficient hardware, it is "
"possible to build volumes which show both increased resilience and increased "
"performance compared to standard <trademark class=\"registered\">UNIX</"
"trademark> partitions. A typical configuration file might be:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:700
#, no-wrap
msgid ""
"	volume raid10\n"
"      plex org striped 512k\n"
"        sd length 102480k drive a\n"
"        sd length 102480k drive b\n"
"        sd length 102480k drive c\n"
"        sd length 102480k drive d\n"
"        sd length 102480k drive e\n"
"      plex org striped 512k\n"
"        sd length 102480k drive c\n"
"        sd length 102480k drive d\n"
"        sd length 102480k drive e\n"
"        sd length 102480k drive a\n"
"        sd length 102480k drive b"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:714
msgid ""
"The subdisks of the second plex are offset by two drives from those of the "
"first plex. This helps to ensure that writes do not go to the same subdisks "
"even if a transfer goes over two drives."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:719
msgid ""
"<xref linkend=\"vinum-raid10-vol\"/> represents the structure of this volume."
""
msgstr ""

#. (itstool) path: figure/title
#: article.translate.xml:724
msgid "A Mirrored, Striped <filename>vinum</filename> Volume"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: article.translate.xml:729
msgctxt "_"
msgid "external ref='vinum-raid10-vol' md5='__failed__'"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:737
msgid "Object Naming"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:739
msgid ""
"<filename>vinum</filename> assigns default names to plexes and subdisks, "
"although they may be overridden. Overriding the default names is not "
"recommended as it does not bring a significant advantage and it can cause "
"confusion."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:745
msgid ""
"Names may contain any non-blank character, but it is recommended to restrict "
"them to letters, digits and the underscore characters. The names of volumes, "
"plexes, and subdisks may be up to 64 characters long, and the names of "
"drives may be up to 32 characters long."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:751
msgid ""
"<filename>vinum</filename> objects are assigned device nodes in the "
"hierarchy <filename class=\"directory\">/dev/gvinum</filename>. The "
"configuration shown above would cause <filename>vinum</filename> to create "
"the following device nodes:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:758
msgid ""
"Device entries for each volume. These are the main devices used by "
"<filename>vinum</filename>. The configuration above would include the "
"devices <filename class=\"devicefile\">/dev/gvinum/myvol</filename>, "
"<filename class=\"devicefile\">/dev/gvinum/mirror</filename>, <filename "
"class=\"devicefile\">/dev/gvinum/striped</filename>, <filename class="
"\"devicefile\">/dev/gvinum/raid5</filename> and <filename class="
"\"devicefile\">/dev/gvinum/raid10</filename>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:769
msgid ""
"All volumes get direct entries under <filename class=\"directory\">/dev/"
"gvinum/</filename>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:774
msgid ""
"The directories <filename class=\"directory\">/dev/gvinum/plex</filename>, "
"and <filename class=\"directory\">/dev/gvinum/sd</filename>, which contain "
"device nodes for each plex and for each subdisk, respectively."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:782
msgid "For example, consider the following configuration file:"
msgstr ""

#. (itstool) path: sect1/programlisting
#: article.translate.xml:785
#, no-wrap
msgid ""
"	drive drive1 device /dev/sd1h\n"
"	drive drive2 device /dev/sd2h\n"
"	drive drive3 device /dev/sd3h\n"
"	drive drive4 device /dev/sd4h\n"
"    volume s64 setupstate\n"
"      plex org striped 64k\n"
"        sd length 100m drive drive1\n"
"        sd length 100m drive drive2\n"
"        sd length 100m drive drive3\n"
"        sd length 100m drive drive4"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:796
msgid ""
"After processing this file, <citerefentry><refentrytitle>gvinum</"
"refentrytitle><manvolnum>8</manvolnum></citerefentry> creates the following "
"structure in <filename class=\"directory\">/dev/gvinum</filename>:"
msgstr ""

#. (itstool) path: sect1/programlisting
#: article.translate.xml:799
#, no-wrap
msgid ""
"	drwxr-xr-x  2 root  wheel       512 Apr 13\n"
"16:46 plex\n"
"	crwxr-xr--  1 root  wheel   91,   2 Apr 13 16:46 s64\n"
"	drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 sd\n"
"\n"
"    /dev/vinum/plex:\n"
"    total 0\n"
"    crwxr-xr--  1 root  wheel   25, 0x10000002 Apr 13 16:46 s64.p0\n"
"\n"
"    /dev/vinum/sd:\n"
"    total 0\n"
"    crwxr-xr--  1 root  wheel   91, 0x20000002 Apr 13 16:46 s64.p0.s0\n"
"    crwxr-xr--  1 root  wheel   91, 0x20100002 Apr 13 16:46 s64.p0.s1\n"
"    crwxr-xr--  1 root  wheel   91, 0x20200002 Apr 13 16:46 s64.p0.s2\n"
"    crwxr-xr--  1 root  wheel   91, 0x20300002 Apr 13 16:46 s64.p0.s3"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:815
msgid ""
"Although it is recommended that plexes and subdisks should not be allocated "
"specific names, <filename>vinum</filename> drives must be named. This makes "
"it possible to move a drive to a different location and still recognize it "
"automatically. Drive names may be up to 32 characters long."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:823
msgid "Creating File Systems"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:825
msgid ""
"Volumes appear to the system to be identical to disks, with one exception. "
"Unlike <trademark class=\"registered\">UNIX</trademark> drives, "
"<filename>vinum</filename> does not partition volumes, which thus do not "
"contain a partition table. This has required modification to some disk "
"utilities, notably <citerefentry><refentrytitle>newfs</"
"refentrytitle><manvolnum>8</manvolnum></citerefentry>, so that it does not "
"try to interpret the last letter of a <filename>vinum</filename> volume name "
"as a partition identifier. For example, a disk drive may have a name like "
"<filename class=\"devicefile\">/dev/ad0a</filename> or <filename class="
"\"devicefile\">/dev/da2h</filename>. These names represent the first "
"partition (<filename>a</filename>) on the first (0) IDE disk (<filename>ad</"
"filename>) and the eighth partition (<filename>h</filename>) on the third "
"(2) SCSI disk (<filename>da</filename>) respectively. By contrast, a "
"<filename>vinum</filename> volume might be called <filename class="
"\"devicefile\">/dev/gvinum/concat</filename>, which has no relationship with "
"a partition name."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:844
msgid ""
"In order to create a file system on this volume, use "
"<citerefentry><refentrytitle>newfs</refentrytitle><manvolnum>8</manvolnum></"
"citerefentry>:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:847
#, no-wrap
msgid "<prompt>#</prompt> <userinput>newfs /dev/gvinum/concat</userinput>"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:852
msgid "Configuring <filename>vinum</filename>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:854
msgid ""
"The <filename>GENERIC</filename> kernel does not contain <filename>vinum</"
"filename>. It is possible to build a custom kernel which includes "
"<filename>vinum</filename>, but this is not recommended. The standard way to "
"start <filename>vinum</filename> is as a kernel module. "
"<citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</"
"manvolnum></citerefentry> is not needed because when "
"<citerefentry><refentrytitle>gvinum</refentrytitle><manvolnum>8</manvolnum></"
"citerefentry> starts, it checks whether the module has been loaded, and if "
"it is not, it loads it automatically."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:865
msgid "Startup"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:867
msgid ""
"<filename>vinum</filename> stores configuration information on the disk "
"slices in essentially the same form as in the configuration files. When "
"reading from the configuration database, <filename>vinum</filename> "
"recognizes a number of keywords which are not allowed in the configuration "
"files. For example, a disk configuration might contain the following text:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:875
#, no-wrap
msgid ""
"volume myvol state up\n"
"volume bigraid state down\n"
"plex name myvol.p0 state up org concat vol myvol\n"
"plex name myvol.p1 state up org concat vol myvol\n"
"plex name myvol.p2 state init org striped 512b vol myvol\n"
"plex name bigraid.p0 state initializing org raid5 512b vol bigraid\n"
"sd name myvol.p0.s0 drive a plex myvol.p0 state up len 1048576b driveoffset "
"265b plexoffset 0b\n"
"sd name myvol.p0.s1 drive b plex myvol.p0 state up len 1048576b driveoffset "
"265b plexoffset 1048576b\n"
"sd name myvol.p1.s0 drive c plex myvol.p1 state up len 1048576b driveoffset "
"265b plexoffset 0b\n"
"sd name myvol.p1.s1 drive d plex myvol.p1 state up len 1048576b driveoffset "
"265b plexoffset 1048576b\n"
"sd name myvol.p2.s0 drive a plex myvol.p2 state init len 524288b driveoffset "
"1048841b plexoffset 0b\n"
"sd name myvol.p2.s1 drive b plex myvol.p2 state init len 524288b driveoffset "
"1048841b plexoffset 524288b\n"
"sd name myvol.p2.s2 drive c plex myvol.p2 state init len 524288b driveoffset "
"1048841b plexoffset 1048576b\n"
"sd name myvol.p2.s3 drive d plex myvol.p2 state init len 524288b driveoffset "
"1048841b plexoffset 1572864b\n"
"sd name bigraid.p0.s0 drive a plex bigraid.p0 state initializing len "
"4194304b driveoff set 1573129b plexoffset 0b\n"
"sd name bigraid.p0.s1 drive b plex bigraid.p0 state initializing len "
"4194304b driveoff set 1573129b plexoffset 4194304b\n"
"sd name bigraid.p0.s2 drive c plex bigraid.p0 state initializing len "
"4194304b driveoff set 1573129b plexoffset 8388608b\n"
"sd name bigraid.p0.s3 drive d plex bigraid.p0 state initializing len "
"4194304b driveoff set 1573129b plexoffset 12582912b\n"
"sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len "
"4194304b driveoff set 1573129b plexoffset 16777216b"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:895
msgid ""
"The obvious differences here are the presence of explicit location "
"information and naming, both of which are allowed but discouraged, and the "
"information on the states. <filename>vinum</filename> does not store "
"information about drives in the configuration information. It finds the "
"drives by scanning the configured disk drives for partitions with a "
"<filename>vinum</filename> label. This enables <filename>vinum</filename> to "
"identify drives correctly even if they have been assigned different "
"<trademark class=\"registered\">UNIX</trademark> drive IDs."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:907
msgid "Automatic Startup"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:909
msgid ""
"<emphasis>Gvinum</emphasis> always features an automatic startup once the "
"kernel module is loaded, via <citerefentry><refentrytitle>loader.conf</"
"refentrytitle><manvolnum>5</manvolnum></citerefentry>. To load the "
"<emphasis>Gvinum</emphasis> module at boot time, add "
"<literal>geom_vinum_load=\"YES\"</literal> to <filename>/boot/loader.conf</"
"filename>."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:916
msgid ""
"When <filename>vinum</filename> is started with <command>gvinum start</"
"command>, <filename>vinum</filename> reads the configuration database from "
"one of the <filename>vinum</filename> drives. Under normal circumstances, "
"each drive contains an identical copy of the configuration database, so it "
"does not matter which drive is read. After a crash, however, "
"<filename>vinum</filename> must determine which drive was updated most "
"recently and read the configuration from this drive. It then updates the "
"configuration, if necessary, from progressively older drives."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:933
msgid "Using <filename>vinum</filename> for the Root File System"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:936
msgid ""
"For a machine that has fully-mirrored file systems using <filename>vinum</"
"filename>, it is desirable to also mirror the root file system. Setting up "
"such a configuration is less trivial than mirroring an arbitrary file system "
"because:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:944
msgid ""
"The root file system must be available very early during the boot process, "
"so the <filename>vinum</filename> infrastructure must already be available "
"at this time."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:950
msgid ""
"The volume containing the root file system also contains the system "
"bootstrap and the kernel. These must be read using the host system's native "
"utilities, such as the BIOS, which often cannot be taught about the details "
"of <filename>vinum</filename>."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:958
msgid ""
"In the following sections, the term <quote>root volume</quote> is generally "
"used to describe the <filename>vinum</filename> volume that contains the "
"root file system."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:964
msgid ""
"Starting up <filename>vinum</filename> Early Enough for the Root File System"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:967
msgid ""
"<filename>vinum</filename> must be available early in the system boot as "
"<citerefentry><refentrytitle>loader</refentrytitle><manvolnum>8</manvolnum></"
"citerefentry> must be able to load the vinum kernel module before starting "
"the kernel. This can be accomplished by putting this line in <filename>/boot/"
"loader.conf</filename>:"
msgstr ""

#. (itstool) path: sect2/programlisting
#: article.translate.xml:973
#, no-wrap
msgid "geom_vinum_load=\"YES\""
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:978
msgid ""
"Making a <filename>vinum</filename>-based Root Volume Accessible to the "
"Bootstrap"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:981
msgid ""
"The current FreeBSD bootstrap is only 7.5 KB of code and does not understand "
"the internal <filename>vinum</filename> structures. This means that it "
"cannot parse the <filename>vinum</filename> configuration data or figure out "
"the elements of a boot volume. Thus, some workarounds are necessary to "
"provide the bootstrap code with the illusion of a standard <literal>a</"
"literal> partition that contains the root file system."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:990
msgid ""
"For this to be possible, the following requirements must be met for the root "
"volume:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:995
msgid "The root volume must not be a stripe or <acronym>RAID</acronym>-5."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1000
msgid ""
"The root volume must not contain more than one concatenated subdisk per plex."
""
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1005
msgid ""
"Note that it is desirable and possible to use multiple plexes, each "
"containing one replica of the root file system. The bootstrap process will "
"only use one replica for finding the bootstrap and all boot files, until the "
"kernel mounts the root file system. Each single subdisk within these plexes "
"needs its own <literal>a</literal> partition illusion, for the respective "
"device to be bootable. It is not strictly needed that each of these faked "
"<literal>a</literal> partitions is located at the same offset within its "
"device, compared with other devices containing plexes of the root volume. "
"However, it is probably a good idea to create the <filename>vinum</filename> "
"volumes that way so the resulting mirrored devices are symmetric, to avoid "
"confusion."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1020
msgid ""
"In order to set up these <literal>a</literal> partitions for each device "
"containing part of the root volume, the following is required:"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1026
msgid ""
"The location, offset from the beginning of the device, and size of this "
"device's subdisk that is part of the root volume needs to be examined, using "
"the command:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:1030
#, no-wrap
msgid "<prompt>#</prompt> <userinput>gvinum l -rv root</userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1032
msgid ""
"<filename>vinum</filename> offsets and sizes are measured in bytes. They "
"must be divided by 512 in order to obtain the block numbers that are to be "
"used by <command>bsdlabel</command>."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1039
msgid "Run this command for each device that participates in the root volume:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:1042
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>bsdlabel -e <replaceable>devname</"
"replaceable></userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1044
msgid ""
"<replaceable>devname</replaceable> must be either the name of the disk, like "
"<filename>da0</filename> for disks without a slice table, or the name of the "
"slice, like <filename>ad0s1</filename>."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1049
msgid ""
"If there is already an <literal>a</literal> partition on the device from a "
"pre-<filename>vinum</filename> root file system, it should be renamed to "
"something else so that it remains accessible (just in case), but will no "
"longer be used by default to bootstrap the system. A currently mounted root "
"file system cannot be renamed, so this must be executed either when being "
"booted from a <quote>Fixit</quote> media, or in a two-step process where, in "
"a mirror, the disk that is not been currently booted is manipulated first."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1061
msgid ""
"The offset of the <filename>vinum</filename> partition on this device (if "
"any) must be added to the offset of the respective root volume subdisk on "
"this device. The resulting value will become the <literal>offset</literal> "
"value for the new <literal>a</literal> partition. The <literal>size</"
"literal> value for this partition can be taken verbatim from the calculation "
"above. The <literal>fstype</literal> should be <literal>4.2BSD</literal>. "
"The <literal>fsize</literal>, <literal>bsize</literal>, and <literal>cpg</"
"literal> values should be chosen to match the actual file system, though "
"they are fairly unimportant within this context."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1076
msgid ""
"That way, a new <literal>a</literal> partition will be established that "
"overlaps the <filename>vinum</filename> partition on this device. "
"<command>bsdlabel</command> will only allow for this overlap if the "
"<filename>vinum</filename> partition has properly been marked using the "
"<literal>vinum</literal> fstype."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1086
msgid ""
"A faked <literal>a</literal> partition now exists on each device that has "
"one replica of the root volume. It is highly recommendable to verify the "
"result using a command like:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:1091
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>fsck -n /dev/<replaceable>devname</"
"replaceable>a</userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1095
msgid ""
"It should be remembered that all files containing control information must "
"be relative to the root file system in the <filename>vinum</filename> volume "
"which, when setting up a new <filename>vinum</filename> root volume, might "
"not match the root file system that is currently active. So in particular, "
"<filename>/etc/fstab</filename> and <filename>/boot/loader.conf</filename> "
"need to be taken care of."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1104
msgid ""
"At next reboot, the bootstrap should figure out the appropriate control "
"information from the new <filename>vinum</filename>-based root file system, "
"and act accordingly. At the end of the kernel initialization process, after "
"all devices have been announced, the prominent notice that shows the success "
"of this setup is a message like:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:1111
#, no-wrap
msgid "Mounting root from ufs:/dev/gvinum/root"
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:1115
msgid "Example of a <filename>vinum</filename>-based Root Setup"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1118
msgid ""
"After the <filename>vinum</filename> root volume has been set up, the output "
"of <command>gvinum l -rv root</command> could look like:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:1122
#, no-wrap
msgid ""
"...\n"
"Subdisk root.p0.s0:\n"
"		Size:        125829120 bytes (120 MB)\n"
"		State: up\n"
"		Plex root.p0 at offset 0 (0  B)\n"
"		Drive disk0 (/dev/da0h) at offset 135680 (132 kB)\n"
"\n"
"Subdisk root.p1.s0:\n"
"		Size:        125829120 bytes (120 MB)\n"
"		State: up\n"
"		Plex root.p1 at offset 0 (0  B)\n"
"		Drive disk1 (/dev/da1h) at offset 135680 (132 kB)"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1135
msgid ""
"The values to note are <literal>135680</literal> for the offset, relative to "
"partition <filename class=\"devicefile\">/dev/da0h</filename>. This "
"translates to 265 512-byte disk blocks in <command>bsdlabel</command>'s "
"terms. Likewise, the size of this root volume is 245760 512-byte blocks. "
"<filename class=\"devicefile\">/dev/da1h</filename>, containing the second "
"replica of this root volume, has a symmetric setup."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1144
msgid "The bsdlabel for these devices might look like:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:1146
#, no-wrap
msgid ""
"...\n"
"8 partitions:\n"
"#        size   offset    fstype   [fsize bsize bps/cpg]\n"
"  a:   245760      281    4.2BSD     2048 16384     0   # (Cyl.    0*- 15*)\n"
"  c: 71771688        0    unused        0     0         # (Cyl.    0 - "
"4467*)\n"
"  h: 71771672       16     vinum                        # (Cyl.    0*- "
"4467*)"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1153
msgid ""
"It can be observed that the <literal>size</literal> parameter for the faked "
"<literal>a</literal> partition matches the value outlined above, while the "
"<literal>offset</literal> parameter is the sum of the offset within the "
"<filename>vinum</filename> partition <literal>h</literal>, and the offset of "
"this partition within the device or slice. This is a typical setup that is "
"necessary to avoid the problem described in <xref linkend=\"vinum-root-"
"panic\"/>. The entire <literal>a</literal> partition is completely within "
"the <literal>h</literal> partition containing all the <filename>vinum</"
"filename> data for this device."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1165
msgid ""
"In the above example, the entire device is dedicated to <filename>vinum</"
"filename> and there is no leftover pre-<filename>vinum</filename> root "
"partition."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:1171
msgid "Troubleshooting"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1173
msgid "The following list contains a few known pitfalls and solutions."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:1177
msgid "System Bootstrap Loads, but System Does Not Boot"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1180
msgid ""
"If for any reason the system does not continue to boot, the bootstrap can be "
"interrupted by pressing <keycap>space</keycap> at the 10-seconds warning. "
"The loader variable <literal>vinum.autostart</literal> can be examined by "
"typing <command>show</command> and manipulated using <command>set</command> "
"or <command>unset</command>."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1188
msgid ""
"If the <filename>vinum</filename> kernel module was not yet in the list of "
"modules to load automatically, type <command>load geom_vinum</command>."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1192
msgid ""
"When ready, the boot process can be continued by typing <command>boot -as</"
"command> which <option>-as</option> requests the kernel to ask for the root "
"file system to mount (<option>-a</option>) and make the boot process stop in "
"single-user mode (<option>-s</option>), where the root file system is "
"mounted read-only. That way, even if only one plex of a multi-plex volume "
"has been mounted, no data inconsistency between plexes is being risked."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1202
msgid ""
"At the prompt asking for a root file system to mount, any device that "
"contains a valid root file system can be entered. If <filename>/etc/fstab</"
"filename> is set up correctly, the default should be something like "
"<literal>ufs:/dev/gvinum/root</literal>. A typical alternate choice would be "
"something like <literal>ufs:da0d</literal> which could be a hypothetical "
"partition containing the pre-<filename>vinum</filename> root file system. "
"Care should be taken if one of the alias <literal>a</literal> partitions is "
"entered here, that it actually references the subdisks of the "
"<filename>vinum</filename> root device, because in a mirrored setup, this "
"would only mount one piece of a mirrored root device. If this file system is "
"to be mounted read-write later on, it is necessary to remove the other "
"plex(es) of the <filename>vinum</filename> root volume since these plexes "
"would otherwise carry inconsistent data."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:1224
msgid "Only Primary Bootstrap Loads"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1226
msgid ""
"If <filename>/boot/loader</filename> fails to load, but the primary "
"bootstrap still loads (visible by a single dash in the left column of the "
"screen right after the boot process starts), an attempt can be made to "
"interrupt the primary bootstrap by pressing <keycap>space</keycap>. This "
"will make the bootstrap stop in <link xlink:href=\"@@URL_RELPREFIX@@/doc/"
"en_US.ISO8859-1/books/handbook/boot.html#boot-boot1\">stage two</link>. An "
"attempt can be made here to boot off an alternate partition, like the "
"partition containing the previous root file system that has been moved away "
"from <literal>a</literal>."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:1239
msgid "Nothing Boots, the Bootstrap Panics"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1242
msgid ""
"This situation will happen if the bootstrap had been destroyed by the "
"<filename>vinum</filename> installation. Unfortunately, <filename>vinum</"
"filename> accidentally leaves only 4 KB at the beginning of its partition "
"free before starting to write its <filename>vinum</filename> header "
"information. However, the stage one and two bootstraps plus the bsdlabel "
"require 8 KB. So if a <filename>vinum</filename> partition was started at "
"offset 0 within a slice or disk that was meant to be bootable, the "
"<filename>vinum</filename> setup will trash the bootstrap."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:1254
msgid ""
"Similarly, if the above situation has been recovered, by booting from a "
"<quote>Fixit</quote> media, and the bootstrap has been re-installed using "
"<command>bsdlabel -B</command> as described in <link xlink:href="
"\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/boot.html#boot-"
"boot1\"/>, the bootstrap will trash the <filename>vinum</filename> header, "
"and <filename>vinum</filename> will no longer find its disk(s). Though no "
"actual <filename>vinum</filename> configuration data or data in "
"<filename>vinum</filename> volumes will be trashed, and it would be possible "
"to recover all the data by entering exactly the same <filename>vinum</"
"filename> configuration data again, the situation is hard to fix. It is "
"necessary to move the entire <filename>vinum</filename> partition by at "
"least 4 KB, in order to have the <filename>vinum</filename> header and the "
"system bootstrap no longer collide."
msgstr ""