os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Various markup fixes: for example, <programlisting></programlisting>

Browse source 
should be used instead of <para><literal></literal></para>, and
  <screen></screen> instead of <para><command></command></para>
- <screen> tags are not inline elements, so they should not be used
  inside of <para></para>
- s/4.x/4.X and some punctuation fixes
- Some device names fixes I missed in my previous commit
This commit is contained in:
Marc Fonvieille 2004-08-11 17:07:40 +00:00
parent a6d1521834
commit 8af463c4d2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=21932
1 changed files with 19 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

45
en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
View file

@ -1060,9 +1060,9 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<filename>/boot/loader</filename> (<xref <filename>/boot/loader</filename> (<xref
linkend="boot-loader">) load the vinum kernel module linkend="boot-loader">) load the vinum kernel module
early, before starting the kernel. This can be early, before starting the kernel. This can be
accomplished by putting the line</para> accomplished by putting the line:</para>
<para><literal>vinum_load="YES"</literal></para> <programlisting>vinum_load="YES"</programlisting>
<para>into the file <para>into the file
<filename>/boot/loader.conf</filename>.</para> <filename>/boot/loader.conf</filename>.</para>
@ -1083,7 +1083,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<para>By placing the line:</para> <para>By placing the line:</para>
<para><literal>vinum.autostart="YES"</literal></para> <programlisting>vinum.autostart="YES"</programlisting>
<para>into <filename>/boot/loader.conf</filename>, Vinum is <para>into <filename>/boot/loader.conf</filename>, Vinum is
instructed to automatically scan all drives for Vinum instructed to automatically scan all drives for Vinum
@ -1152,9 +1152,9 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<step> <step>
<para>The location (offset from the beginning of the device) <para>The location (offset from the beginning of the device)
and size of this device's subdisk that is part of the root and size of this device's subdisk that is part of the root
volume need to be examined, using the command</para> volume need to be examined, using the command:</para>
<para><command>vinum l -rv root</command></para> <screen>&prompt.root; <userinput>vinum l -rv root</userinput></screen>
<para>Note that Vinum offsets and sizes are measured in <para>Note that Vinum offsets and sizes are measured in
bytes. They must be divided by 512 in order to obtain the bytes. They must be divided by 512 in order to obtain the
@ -1163,10 +1163,9 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
</step> </step>
<step> <step>
<para>Run the command</para> <para>Run the command:</para>
<para><command>disklabel -e <screen>&prompt.root; <userinput>disklabel -e <replaceable>devname</replaceable></userinput></screen>
</command><replaceable>devname</replaceable></para>
<para>for each device that participates in the root volume. <para>for each device that participates in the root volume.
<replaceable>devname</replaceable> must be either the name <replaceable>devname</replaceable> must be either the name
@ -1213,10 +1212,9 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<para>That's all! A faked <literal>"a"</literal> partition <para>That's all! A faked <literal>"a"</literal> partition
does exist now on each device that has one replica of the does exist now on each device that has one replica of the
root volume. It is highly recommendable to verify the root volume. It is highly recommendable to verify the
result again, using a command like</para> result again, using a command like:</para>
<para><command>fsck -n <screen>&prompt.root; <userinput>fsck -n /dev/<replaceable>devname</replaceable>a</userinput></screen>
</command><devicename>/dev/<replaceable>devname</replaceable>a</devicename></para>
</step> </step>
</procedure> </procedure>
@ -1235,7 +1233,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
the prominent notice that shows the success of this setup is a the prominent notice that shows the success of this setup is a
message like:</para> message like:</para>
<para><screen>Mounting root from ufs:/dev/vinum/root</screen></para> <screen>Mounting root from ufs:/dev/vinum/root</screen>
</sect2> </sect2>
<sect2> <sect2>
@ -1244,7 +1242,6 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<para>After the Vinum root volume has been set up, the output of <para>After the Vinum root volume has been set up, the output of
<command>vinum l -rv root</command> could look like:</para> <command>vinum l -rv root</command> could look like:</para>
<para>
<screen> <screen>
... ...
Subdisk root.p0.s0: Subdisk root.p0.s0:
@ -1259,20 +1256,18 @@ Subdisk root.p1.s0:
Plex root.p1 at offset 0 (0 B) Plex root.p1 at offset 0 (0 B)
Drive disk1 (/dev/da1h) at offset 135680 (132 kB) Drive disk1 (/dev/da1h) at offset 135680 (132 kB)
</screen> </screen>
</para>
<para>The values to note are <literal>135680</literal> for the <para>The values to note are <literal>135680</literal> for the
offset (relative to partition offset (relative to partition
<devicename>/dev/da0h</devicename>). This translates to 265 <filename>/dev/da0h</filename>). This translates to 265
512-byte disk blocks in <command>disklabel</command>'s terms. 512-byte disk blocks in <command>disklabel</command>'s terms.
Likewise, the size of this root volume is 245760 512-byte Likewise, the size of this root volume is 245760 512-byte
blocks. <devicename>/dev/da1h</devicename>, containing the blocks. <filename>/dev/da1h</filename>, containing the
second replica of this root volume, has a symmetric second replica of this root volume, has a symmetric
setup.</para> setup.</para>
<para>The disklabel for these devices might look like:</para> <para>The disklabel for these devices might look like:</para>
<para>
<screen> <screen>
... ...
8 partitions: 8 partitions:
@ -1281,7 +1276,6 @@ Subdisk root.p1.s0:
c: 71771688 0 unused 0 0 # (Cyl. 0 - 4467*) c: 71771688 0 unused 0 0 # (Cyl. 0 - 4467*)
h: 71771672 16 vinum # (Cyl. 0*- 4467*) h: 71771672 16 vinum # (Cyl. 0*- 4467*)
</screen> </screen>
</para>
<para>It can be observed that the <literal>"size"</literal> <para>It can be observed that the <literal>"size"</literal>
parameter for the faked <literal>"a"</literal> partition parameter for the faked <literal>"a"</literal> partition
@ -1339,7 +1333,7 @@ Subdisk root.p1.s0:
correctly, the default should be something like correctly, the default should be something like
<literal>ufs:/dev/vinum/root</literal>. A typical alternate <literal>ufs:/dev/vinum/root</literal>. A typical alternate
choice would be something like choice would be something like
<userinput>ufs:da0d</userinput> which could be a <literal>ufs:da0d</literal> which could be a
hypothetical partition that contains the pre-Vinum root hypothetical partition that contains the pre-Vinum root
filesystem. Care should be taken if one of the alias filesystem. Care should be taken if one of the alias
<literal>"a"</literal> partitions are entered here that are <literal>"a"</literal> partitions are entered here that are
@ -1398,9 +1392,9 @@ Subdisk root.p1.s0:
</sect2> </sect2>
<sect2 id="vinum-root-4x"> <sect2 id="vinum-root-4x">
<title>Differences for FreeBSD 4.x</title> <title>Differences for FreeBSD 4.X</title>
<para>Under FreeBSD 4.x, some internal functions required to <para>Under FreeBSD 4.X, some internal functions required to
make Vinum automatically scan all disks are missing, and the make Vinum automatically scan all disks are missing, and the
code that figures out the internal ID of the root device is code that figures out the internal ID of the root device is
not smart enough to handle a name like not smart enough to handle a name like
@ -1411,8 +1405,7 @@ Subdisk root.p1.s0:
line like the following one in line like the following one in
<filename>/boot/loader.conf</filename>:</para> <filename>/boot/loader.conf</filename>:</para>
<para><literal>vinum.drives="/dev/<replaceable>da0</replaceable> <programlisting>vinum.drives="/dev/<replaceable>da0</replaceable> /dev/<replaceable>da1</replaceable>"</programlisting>
/dev/<replaceable>da1</replaceable>"</literal></para>
<para>It is important that all drives are mentioned that could <para>It is important that all drives are mentioned that could
possibly contain Vinum data. It does not harm if possibly contain Vinum data. It does not harm if
@ -1435,7 +1428,7 @@ Subdisk root.p1.s0:
<filename>/boot/loader.conf</filename> to accomplish this <filename>/boot/loader.conf</filename> to accomplish this
looks like:</para> looks like:</para>
<para><literal>vinum.root="root"</literal></para> <programlisting>vinum.root="root"</programlisting>
<para>Now, when the kernel initialization tries to find out the <para>Now, when the kernel initialization tries to find out the
root device to mount, it sees whether some kernel module has root device to mount, it sees whether some kernel module has
@ -1458,9 +1451,9 @@ Subdisk root.p1.s0:
pre-allocated root parameter and the driver as figured out pre-allocated root parameter and the driver as figured out
from the given name will make this routine enter its normal from the given name will make this routine enter its normal
parser, so entering a string like parser, so entering a string like
<userinput>ufs:da0d</userinput> will work as expected. Note <literal>ufs:da0d</literal> will work as expected. Note
that if this fails, it is however no longer possible to that if this fails, it is however no longer possible to
re-enter a string like <userinput>ufs:vinum/root</userinput> re-enter a string like <literal>ufs:vinum/root</literal>
again, since it cannot be parsed. The only way out is to again, since it cannot be parsed. The only way out is to
reboot again, and start over then. (At the reboot again, and start over then. (At the
<quote>askroot</quote> prompt, the initial <quote>askroot</quote> prompt, the initial