| attach plex volume [ rename]
attach subdisk plex [offset ][ rename]
|Attach a plex to a volume, or a subdisk to a plex. If offset is specified, the subdisk will be attached to the given offset within the plex. If rename is specified, the subdisk or plex will change name according to the object it attaches to.
| checkparity [
Check the parity blocks of a RAID-5 plex.
The parity check will start at the
beginning of the plex if the
| concat [
|Create a concatenated volume from the specified drives. If no name is specified, a unique name will be set by gvinum.
| create [
Create a volume as described in
provided, opens an editor and provides the current
configuration for editing.
| detach [
|Detach a plex or subdisk from the volume or plex to which it is attached.
|grow plex device
|Grow a plex by creating a gvinum drive and subdisk on device and attach it to the plex. If required by the plex organization, it will be put into the growable state.
|Provides a synopsis of gvinum commands and arguments.
| l | list [
List information about the relevant object(s).
| mirror [
Create a mirrored volume from the specified drives.
It requires at least a multiple of 2 drives.
If no name is specified, a unique name will be set by gvinum.
| move | mv
Move the subdisk(s) to the specified drive.
If a single subdisk is moved, and it forms a part of a RAID-5 plex, the moved subdisks will need to be set to the "stale" state, and the plex will require a start command. If multiple subdisk(s) is moved, and form part of a RAID-5 plex, the moved disk(s) will need to be set to the "up" state and the plex will require a rebuildparity command. If the subdisk(s) form part of a plex that is mirrored with other plexes, the plex will require restarting and will sync once restarted. Moving more than one subdisk in a RAID-5 plex or subdisks from both sides of a mirrored plex volume will destroy data. Note that parity rebuilds and syncing must be started manually after a move.
|Write a copy of the current configuration to standard output.
|Exit gvinum when running in interactive mode. Normally this would be done by entering the EOF character.
| raid5 [
|Create a RAID-5 volume from the specified drives. If no name is specified, a unique name will be set by gvinum. This organization requires at least three drives.
| rename [
Change the name of the specified object.
Note that device nodes will not be renamed until gvinum is restarted.
| rebuildparity [
Rebuild the parity blocks of a RAID-5 plex.
The parity rebuild will start at
the beginning of the plex if the
| resetconfig [
|Reset the complete gvinum configuration.
| rm [
Remove an object and, if
|Save gvinum configuration to disk after configuration failures.
| setstate [
Set state without influencing other objects, for diagnostic purposes
|Read configuration from all vinum drives.
| start [
Allow the system to access the objects.
If necessary, plexes will be synced and rebuilt.
If a subdisk was added to a running RAID-5 or striped plex, gvinum will
expand into this subdisk and grow the whole RAID-5 array.
This can be done without unmounting your filesystem.
| stop [
|Terminate access to the objects, or stop gvinum if no parameters are specified.
| stripe [
|Create a striped volume from the specified drives. If no name is specified, a unique name will be set by gvinum. This organization requires at least two drives.
|The name of the editor to use for editing configuration files, by default vi(1) is invoked.
|directory with device nodes for gvinum objects
gvinum mirror /dev/ada1 /dev/ada2
mount /dev/gvinum/gvinumvolume0 /mnt
To create a striped mirror on disks /dev/ada1 /dev/ada2 /dev/ada3 and /dev/ada4 named "data" and create a filesystem:
gvinum mirror -s -n data /dev/ada1 /dev/ada2 /dev/ada3 /dev/ada4
To create a raid5 array on disks /dev/ada1 /dev/ada2 and /dev/ada3, with stripesize 493k you can use the raid5 command:
gvinum raid5 -s 493k /dev/ada1 /dev/ada2 /dev/ada3
Then the volume will be created automatically. Afterwards, you have to initialize the volume:
gvinum start myraid5vol
The initialization will start, and the states will be updated when it's finished. The list command will give you information about its progress.
Imagine that one of the drives fails, and the output of 'printconfig' looks something like this:
drive gvinumdrive1 device /dev/ada2
drive gvinumdrive2 device /dev/???
drive gvinumdrive0 device /dev/ada1
plex name myraid5vol.p0 org raid5 986s vol myraid5vol
sd name myraid5vol.p0.s2 drive gvinumdrive2 len 32538s driveoffset 265s
plex myraid5vol.p0 plexoffset 1972s
sd name myraid5vol.p0.s1 drive gvinumdrive1 len 32538s driveoffset 265s
plex myraid5vol.p0 plexoffset 986s
sd name myraid5vol.p0.s0 drive gvinumdrive0 len 32538s driveoffset 265s
plex myraid5vol.p0 plexoffset 0s
Create a new drive with this configuration:
drive gdrive4 device /dev/ada4
Then move the stale subdisk to the new drive:
gvinum move gdrive4 myraid5vol.p0.s2
Then, initiate the rebuild:
gvinum start myraid5vol.p0
The plex will go up form degraded mode after the rebuild is finished. The plex can still be used while the rebuild is in progress, although requests might be delayed.
Given the configuration as in the previous example, growing a RAID-5 or STRIPED array is accomplished by using the grow command:
gvinum grow myraid5vol.p0 /dev/ada4
If everything went ok, the plex state should now be set to growable. You can then start the growing with the start command:
gvinum start myraid5vol.p0
As with rebuilding, you can watch the progress using the list command.
For a more advanced usage and detailed explanation of gvinum, the handbook is recommended.
The gvinum utility was written by Lukas Ertl. The move and rename commands and documentation were added by Chris Jones through the 2005 Google Summer of Code program. A partial rewrite of gvinum was done by Lukas Ertl and Ulf Lilleengen through the 2007 Google Summer of Code program. The documentation have been updated to reflect the new functionality.
Moving subdisks that are not part of a mirrored or RAID-5 volume will destroy data. It is perhaps a bug to permit this.
Plexes in which subdisks have been moved do not automatically sync or rebuild parity. This may leave data unprotected and is perhaps unwise.
Currently, gvinum does not yet fully implement all of the functions found in vinum. Specifically, the following commands from vinum are not supported:
|Cause the volume manager to enter the kernel debugger.
|Set debugging flags.
|dumpconfig [drive ...]
|List the configuration information stored on the specified drives, or all drives in the system if no drive names are specified.
| info [
|List information about volume manager state.
|Create a volume label.
| resetstats [
|Reset statistics counters for the specified objects, or for all objects if none are specified.
|Set daemon configuration.
|March 28, 2021