- Use manual page entities for ccd(4).
- Some little "rewordings" and tags fixes.
This commit is contained in:
Marc Fonvieille
parent
fbb1f0eda5
commit
b55c832494
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=16869
1 changed files with 26 additions and 26 deletions
|
|
@ -420,11 +420,11 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33</programlist
|
|||
<sect4 id="ccd-setup">
|
||||
<title>Setting up the CCD</title>
|
||||
|
||||
<para><application>CCD</application> allows you to take
|
||||
<para>The driver &man.ccd.4; allows you to take
|
||||
several identical disks and concatenate them into one
|
||||
logical file system. In order to use
|
||||
<application>ccd</application>, you need a kernel with
|
||||
<application>ccd</application> support built in.
|
||||
&man.ccd.4;, you need a kernel with
|
||||
&man.ccd.4; support built in.
|
||||
Add this line to your kernel configuration file, rebuild, and
|
||||
reinstall the kernel:</para>
|
||||
|
||||
|
|
@ -436,47 +436,47 @@ ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33</programlist
|
|||
<programlisting>device ccd</programlisting>
|
||||
|
||||
<note><para>In FreeBSD 5.X, it is not necessary to specify
|
||||
a number of ccd devices, as the ccd device driver is now
|
||||
a number of &man.ccd.4; devices, as the &man.ccd.4; device driver is now
|
||||
self-cloning — new device instances will automatically be
|
||||
created on demand.</para></note>
|
||||
|
||||
<para><application>ccd</application> support can also be
|
||||
<para>The &man.ccd.4; support can also be
|
||||
loaded as a kernel loadable module in FreeBSD 3.0 or
|
||||
later.</para>
|
||||
|
||||
<para>To set up <application>ccd</application>, you must first use
|
||||
<para>To set up &man.ccd.4;, you must first use
|
||||
&man.disklabel.8; to label the disks:</para>
|
||||
|
||||
<programlisting>disklabel -r -w ad1 auto
|
||||
disklabel -r -w ad2 auto
|
||||
disklabel -r -w ad3 auto</programlisting>
|
||||
|
||||
<para>This creates a disklabel for ad1c, ad2c and ad3c that
|
||||
<para>This creates a disklabel for <devicename>ad1c</devicename>, <devicename>ad2c</devicename> and <devicename>ad3c</devicename> that
|
||||
spans the entire disk.</para>
|
||||
|
||||
<para>The next step is to change the disklabel type. You
|
||||
can use <application>disklabel</application> to edit the
|
||||
<para>The next step is to change the disk label type. You
|
||||
can use &man.disklabel.8; to edit the
|
||||
disks:</para>
|
||||
|
||||
<programlisting>disklabel -e ad1
|
||||
disklabel -e ad2
|
||||
disklabel -e ad3</programlisting>
|
||||
|
||||
<para>This opens up the current disklabel on each disk with
|
||||
<para>This opens up the current disk label on each disk with
|
||||
the editor specified by the <envar>EDITOR</envar>
|
||||
environment variable, typically &man.vi.1;.</para>
|
||||
|
||||
<para>An unmodified disklabel will look something like
|
||||
<para>An unmodified disk label will look something like
|
||||
this:</para>
|
||||
|
||||
<programlisting>8 partitions:
|
||||
# size offset fstype [fsize bsize bps/cpg]
|
||||
c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597)</programlisting>
|
||||
|
||||
<para>Add a new "e" partition for &man.ccd.4; to use. This
|
||||
can usually be copied from the <quote>c</quote> partition,
|
||||
<para>Add a new <literal>e</literal> partition for &man.ccd.4; to use. This
|
||||
can usually be copied from the <literal>c</literal> partition,
|
||||
but the <option>fstype</option> <emphasis>must</emphasis>
|
||||
be <userinput>4.2BSD</userinput>. The disklabel should
|
||||
be <userinput>4.2BSD</userinput>. The disk label should
|
||||
now look something like this:</para>
|
||||
|
||||
<programlisting>8 partitions:
|
||||
|
|
@ -501,12 +501,12 @@ sh MAKEDEV ccd0</programlisting>
|
|||
<command>MAKEDEV</command> is not necessary.</para></note>
|
||||
|
||||
<para>Now that you have all of the disks labeled, you must
|
||||
build the <application>ccd</application>. To do that,
|
||||
use &man.ccdconfig.8;, with options similar to the following:
|
||||
build the &man.ccd.4;. To do that,
|
||||
use &man.ccdconfig.8;, with options similar to the following:</para>
|
||||
|
||||
<programlisting>ccdconfig ccd0<co id="co-ccd-dev"> 32<co id="co-ccd-interleave"> 0<co id="co-ccd-flags"> /dev/ad1e<co id="co-ccd-devs"> /dev/ad2e /dev/ad3e</programlisting>
|
||||
|
||||
The use and meaning of each option is shown below:</para>
|
||||
<para>The use and meaning of each option is shown below:</para>
|
||||
|
||||
<calloutlist>
|
||||
<callout arearefs="co-ccd-dev">
|
||||
|
|
@ -523,21 +523,21 @@ sh MAKEDEV ccd0</programlisting>
|
|||
</callout>
|
||||
|
||||
<callout arearefs="co-ccd-flags">
|
||||
<para>Flags for <command>ccdconfig</command>. If you want to enable drive
|
||||
<para>Flags for &man.ccdconfig.8;. If you want to enable drive
|
||||
mirroring, you can specify a flag here. This
|
||||
configuration does not provide mirroring for
|
||||
<application>ccd</application>, so it is set at 0 (zero).</para>
|
||||
&man.ccd.4;, so it is set at 0 (zero).</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="co-ccd-devs">
|
||||
<para>The final arguments to <command>ccdconfig</command>
|
||||
<para>The final arguments to &man.ccdconfig.8;
|
||||
are the devices to place into the array. Use the complete pathname
|
||||
for each device.</para>
|
||||
</callout>
|
||||
</calloutlist>
|
||||
|
||||
|
||||
<para>After running <command>ccdconfig</command> the <application>ccd</application>
|
||||
<para>After running &man.ccdconfig.8; the &man.ccd.4;
|
||||
is configured. A file system can be installed. Refer to &man.newfs.8;
|
||||
for options, or simply run: </para>
|
||||
|
||||
|
|
@ -550,7 +550,7 @@ sh MAKEDEV ccd0</programlisting>
|
|||
<title>Making it all Automatic</title>
|
||||
|
||||
<para>Generally, you will want to mount the
|
||||
<application>ccd</application> upon each reboot. To do this, you must
|
||||
&man.ccd.4; upon each reboot. To do this, you must
|
||||
configure it first. Write out your current configuration to
|
||||
<filename>/etc/ccd.conf</filename> using the following command:</para>
|
||||
|
||||
|
|
@ -559,18 +559,18 @@ sh MAKEDEV ccd0</programlisting>
|
|||
<para>During reboot, the script <command>/etc/rc</command>
|
||||
runs <command>ccdconfig -C</command> if <filename>/etc/ccd.conf</filename>
|
||||
exists. This automatically configures the
|
||||
<application>ccd</application> so it can be mounted.</para>
|
||||
&man.ccd.4; so it can be mounted.</para>
|
||||
|
||||
<note><para>If you are booting into single user mode, before you can
|
||||
<command>mount</command> the <application>ccd</application>, you
|
||||
&man.mount.8; the &man.ccd.4;, you
|
||||
need to issue the following command to configure the
|
||||
array:</para>
|
||||
|
||||
<programlisting>ccdconfig -C</programlisting>
|
||||
</note>
|
||||
|
||||
<para>To automatically mount the <application>ccd</application>,
|
||||
place an entry for the <application>ccd</application> in
|
||||
<para>To automatically mount the &man.ccd.4;,
|
||||
place an entry for the &man.ccd.4; in
|
||||
<filename>/etc/fstab</filename> so it will be mounted at
|
||||
boot time:</para>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue