summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--sbin/vinum/vinum.8101
-rw-r--r--share/man/man4/vinum.4106
2 files changed, 76 insertions, 131 deletions
diff --git a/sbin/vinum/vinum.8 b/sbin/vinum/vinum.8
index 1637559..4763396 100644
--- a/sbin/vinum/vinum.8
+++ b/sbin/vinum/vinum.8
@@ -34,7 +34,7 @@
.\" otherwise) arising in any way out of the use of this software, even if
.\" advised of the possibility of such damage.
.\"
-.\" $Id: vinum.4,v 1.9 1999/03/23 04:57:24 grog Exp grog $
+.\" $Id: vinum.8,v 1.10 1999/07/02 07:46:13 grog Exp grog $
.\"
.Dd 28 March 1999
.Dt vinum 8
@@ -283,10 +283,9 @@ manager. See
.Xr vinum 4
for more information about the volume manager.
.Xr vinum 8
-is designed either for interactive use, when started without a command, or to
-execute a single command if the command is supplied as arguments to
-.Nm vinum .
-In interactive mode,
+is designed either for interactive use, when started without command line
+arguments, or to execute a single command if the command is supplied on the
+command line. In interactive mode,
.Nm
maintains a command line history.
.Ss OPTIONS
@@ -614,16 +613,16 @@ Maximum allocs: 56, malloc table at 0xf0f72dbc
Time Event Buf Dev Offset Bytes SD SDoff Doffset Goffset
-14:40:00.637758 1VS Write 0xf2361f40 0x5b03 0x10 16384
-14:40:00.639280 2LR Write 0xf2361f40 0x5b03 0x10 16384
-14:40:00.639294 3RQ Read 0xf2361f40 0x427 0x104109 8192 19 0 0 0
-14:40:00.639455 3RQ Read 0xf2361f40 0x417 0xd2109 8192 17 0 0 0
-14:40:00.639529 3RQ Read 0xf2361f40 0x40f 0x6e109 8192 16 0 0 0
-14:40:00.652978 4DN Read 0xf2361f40 0x427 0x104109 8192 19 0 0 0
-14:40:00.667040 4DN Read 0xf2361f40 0x40f 0x6e109 8192 16 0 0 0
-14:40:00.668556 4DN Read 0xf2361f40 0x417 0xd2109 8192 17 0 0 0
-14:40:00.669777 6RP Write 0xf2361f40 0x427 0x104109 8192 19 0 0 0
-14:40:00.685547 4DN Write 0xf2361f40 0x427 0x104109 8192 19 0 0 0
+14:40:00.637758 1VS Write 0xf2361f40 91.3 0x10 16384
+14:40:00.639280 2LR Write 0xf2361f40 91.3 0x10 16384
+14:40:00.639294 3RQ Read 0xf2361f40 4.39 0x104109 8192 19 0 0 0
+14:40:00.639455 3RQ Read 0xf2361f40 4.23 0xd2109 8192 17 0 0 0
+14:40:00.639529 3RQ Read 0xf2361f40 4.15 0x6e109 8192 16 0 0 0
+14:40:00.652978 4DN Read 0xf2361f40 4.39 0x104109 8192 19 0 0 0
+14:40:00.667040 4DN Read 0xf2361f40 4.15 0x6e109 8192 16 0 0 0
+14:40:00.668556 4DN Read 0xf2361f40 4.23 0xd2109 8192 17 0 0 0
+14:40:00.669777 6RP Write 0xf2361f40 4.39 0x104109 8192 19 0 0 0
+14:40:00.685547 4DN Write 0xf2361f40 4.39 0x104109 8192 19 0 0 0
.Ed
.Pp
The
@@ -1284,7 +1283,7 @@ option, these commands produce no output.
Use a volume with a single concatenated plex for the largest possible storage
without resilience to drive failures:
.Bd -literal
-# vinum -> concat -v /dev/da1h /dev/da2h /dev/da3h /dev/da4h
+vinum -> concat -v /dev/da1h /dev/da2h /dev/da3h /dev/da4h
volume vinum0
plex name vinum0.p0 org concat
drive vinumdrive0 device /dev/da1h
@@ -1415,29 +1414,34 @@ dependent on the context.
The configuration file can contain the following entries:
.Pp
.Bl -hang -width 4n
-.It Nm drive Ar name option
+.It Nm drive Ar name devicename
+.Op options
.Pp
-Define a drive. The option must be:
+Define a drive. The options are:
.Pp
.Bl -hang -width 18n
.It Nm device Ar devicename
Specify the device on which the drive resides.
.Ar devicename
-must be the name of a disk compatibility partition, for example
+must be the name of a disk partition, for example
.Pa /dev/da1e
or
-.Pa /dev/wd3h ,
-and it should be of type
+.Pa /dev/wd3s2h ,
+and it must be of type
.Nm vinum .
Do not use the
.Nm c
-partition, which is reserved for the complete disk, and should be of type
-.Nm unused .
-It is currently possible to create drives on other disk devices, for example
-.Pa /dev/da0s1
-or
-.Pa /dev/da0s1e ,
-but it will not be possible to start these drives after a reboot.
+partition, which is reserved for the complete disk.
+.It Nm hotspare
+Define the drive to be a
+.Do
+hot spare
+.Dc
+drive, which is maintained to automatically replace a failed drive.
+.Nm
+does not allow this drive to be used for any other purpose. In particular, it
+is not possible to create subdisks on it. This functionality has not been
+completely implemented.
.El
.It Nm volume
.Ar name
@@ -1654,15 +1658,7 @@ volume vol5
.Nm
drives are currently BSD disk partitions. They must be of type
.Ar vinum
-in order to avoid overwriting file systems. For compatibility reasons,
-.Nm
-currently accepts partitions of type
-.Ar unused ,
-but the next release will not allow this kind of partition.
-.Nm
-prints a warning message when reading a configuration from a partition of type
-.Ar unused .
-Use
+in order to avoid overwriting data used for other purposes. Use
.Nm disklabel
.Ar -e
to edit a partition type definition. The following display shows a typical
@@ -1727,12 +1723,12 @@ system.
The first choice you need to make is where to put the data. You need dedicated
disk partitions for
.Nm vinum .
-They should be compatibility partitions, not devices or partition
-.Nm c
-of a slice. For example, good names are
+They should be partitions, not devices, and they should not be partition
+.Nm c .
+For example, good names are
.Pa /dev/da0e
or
-.Pa /dev/wd3a .
+.Pa /dev/wd3s4a .
Bad names are
.Pa /dev/da0
and
@@ -1740,15 +1736,8 @@ and
both of which represent a device, not a partition,
.Pa /dev/wd1c ,
which represents a complete disk and should be of type
-.Nm unused ,
-and
-.Pa /dev/da3s0e ,
-which is not a compatibility partition.
-.Nm
-currently allows you to create drives with these names, but the
-.Nm start
-command will not find them. See the example under DRIVE LAYOUT CONSIDERATIONS
-above.
+.Nm unused .
+See the example under DRIVE LAYOUT CONSIDERATIONS above.
.Ss Designing volumes
The way you set up
.Nm
@@ -2263,11 +2252,8 @@ will not create a device on UFS partitions. Instead, it will return an error
message
.if t ``wrong partition type''.
.if n "wrong partition type".
-The partition type should be
-.Ar vinum ,
-though currently partitions of type
-.Ar unused
-are also accepted.
+The partition type must be
+.Ar vinum .
.It
When you create a volume with multiple plexes,
.Nm
@@ -2432,3 +2418,8 @@ Greg Lehey
The
.Nm
command first appeared in FreeBSD 3.0.
+The RAID-5 component of
+.Nm
+was developed by Cybernet Inc.
+.Pa www.cybernet.com
+for its NetMAX product.
diff --git a/share/man/man4/vinum.4 b/share/man/man4/vinum.4
index 5f66c54..5d333ff 100644
--- a/share/man/man4/vinum.4
+++ b/share/man/man4/vinum.4
@@ -34,7 +34,7 @@
.\" otherwise) arising in any way out of the use of this software, even if
.\" advised of the possibility of such damage.
.\"
-.\" $Id: vinum.4,v 1.9 1999/03/23 04:57:24 grog Exp grog $
+.\" $Id: vinum.4,v 1.10 1999/04/13 01:16:28 grog Exp grog $
.\"
.Dd 28 March 1999
.Dt vinum 4
@@ -189,89 +189,39 @@ as described above.
If the VINUMDEBUG variables do not match, vinum(8) will fail with a message
explaining the problem and what to do to correct it.
.Pp
-.Nm
-is currently available in two versions: a freely available version which does
-not contain RAID-5 functionality, and a full version including RAID-5
-functionality, which is available from Cybernet Systems
-Inc. See their web page at
-.Pa http://www.cybernet.com .
.Sh RUNNING VINUM
-Normally, you start a configured version of
-.Nm
-at boot time. Set the variable
-.Ar vinum_drives
-in
-.Ar /etc/rc.conf
-to indicate the slices on which
.Nm
-drives are located. For example, if you have
-.Nm
-drives on
-.Ar /dev/da1h ,
-.Ar /dev/da2h ,
-.Ar /dev/da3h ,
-.Ar /dev/da4h
-and
-.Ar /dev/da5h ,
-you would set the variable to:
-.Bd -literal
-vinum_drives="/dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5"
-.Ed
-.Pp
-.Sh VINUM INSTALLATION
-The freely available version of the
-.Nm
-kld is called
-.Pa /modules/vinum.ko ,
-and the RAID-5 version is
-.Pa /modules/Vinum.o .
-To load the module:
-.Pp
-.Bd -literal -offset indent
-# kldload vinum
-.Ed
-.Pp
-.Nm vinum(8)
-also automatically loads the kld module if it is not yet loaded.
-.Pp
-After loading
+is part of the base FreeBSD system. It does not require installation.
+To start it, start the
+.Nm vinum
+program, which will load the kld if it is not already present.
+Before using
.Nm vinum ,
-it must be configured. In an existing installation, the following command reads
-the configuration an existing set of disks:
-.Bd -literal -offset indent
-# vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6
-.Ed
-.sp
-This command must specify all of the devices used by
-.Nm vinum .
-.Nm vinum(8)
-reads the configuration from the device with the newest configuration file, then
-updates it if necessary with additional information from successively older
-configurations. These commands are normally embedded in the startup file
-.Pa /etc/rc .
-.Pp
-See
+it must be configured. See
.Xr vinum 8
for information on how to create a
.Nm
configuration.
.Pp
-To unload the kld, first find the
-.Ar Id
-field in
-.Pa kldstat:
-.Bd -literal -offset indent
-# kldstat
-Id Refs Address Size Name
- 1 2 0xf0100000 1c7de8 kernel
- 2 1 0xf0f5b000 b0000 Vinum.ko
-.Ed
+Normally, you start a configured version of
+.Nm
+at boot time. Set the variable
+.Ar start_vinum
+in
+.Pa /etc/rc.conf
+to
+.Ar YES
+to start
+.Nm
+at boot time.
.Pp
-To unload the module, use
-.Pa kldunload:
-.Bd -literal -offset indent
-# kldunload -n Vinum
-.Ed
+If
+.Nm
+is loaded as a kld (the recommended way), the
+.Nm vinum Ar stop
+command will unload it. You can also do this with the
+.Nm kldunload
+command.
.Pp
The kld can only be unloaded when idle, in other words when no volumes are
mounted and no other instances of the
@@ -1013,7 +963,11 @@ Greg Lehey
.Pa <grog@lemis.com> .
.Sh HISTORY
.Nm vinum
-first appeared in FreeBSD 3.0.
+first appeared in FreeBSD 3.0. The RAID-5 component of
+.Nm
+was developed by Cybernet Inc.
+.Pa www.cybernet.com
+for its NetMAX product.
.Sh SEE ALSO
.Xr vinum 8 ,
.Xr disklabel 5 ,
OpenPOWER on IntegriCloud