GVINUM(8) | MidnightBSD System Manager's Manual | GVINUM(8) |
gvinum
— Logical
Volume Manager control program
gvinum
and associated
geom(4) kernel support is
deprecated, and may not be available in FreeBSD 14.0
and later. Users are advised to migrate to
gconcat(8),
gmirror(8),
gstripe(8),
graid(8), or
ZFS(8). More information is
available at
https://wiki.freebsd.org/DeprecationPlan/gvinum.
gvinum |
[command] [-options ] |
attach
plex volume [rename
]attach
subdisk plex [offset]
[rename
]checkparity
[-f
] plex-f
flag is
specified, or otherwise at the location of the parity check pointer, the
first location at which plex's parity is incorrect. All subdisks in the
plex must be up for a parity check.concat
[-fv
] [-n
name] drivesgvinum
.create
[-f
] [description-file]gvinum
configuration for
editing. The -f
flag will make gvinum ignore any
errors regarding creating objects that already exists. However, in
contrast to vinum, objects that are not properly named in the
description-file will not be created when the
-f
flag is given.detach
[-f
] [plex |
subdisk]grow
plex devicehelp
gvinum
commands and
arguments.l
|
list
[-rvV
] [volume |
plex | subdisk]ld
[-rvV
] [drive ...]ls
[-rvV
] [subdisk ...]lp
[-rvV
] [plex ...]lv
[-rvV
] [volume ...]-r
flag provides recursive display, showing each
object's subordinate objects in proper relation. The
-v
and -V
flags provide
progressively more detailed output.mirror
[-fsv
] [-n
name] drives-s
flag is specified, a striped
mirror will be created, and thus requires a multiple of 4 drives.move
| mv
-f
drive subdisk
[...]-f
flag is required, as all data on the indicated subdisk(s) will be
destroyed as part of the move. This can currently only be done when the
subdisk is not being accessed.
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.
printconfig
quit
gvinum
when running in interactive mode.
Normally this would be done by entering the EOF character.raid5
[-fv
] [-s
stripesize] [-n
name] drivesgvinum
. This
organization requires at least three drives.rename
[-r
] drive |
subdisk | plex |
volume newname-r
flag will recursively rename subordinate objects.
Note that device nodes will not be renamed until
gvinum
is restarted.
rebuildparity
[-f
] plex-f
flag is
specified, or otherwise at the location of the parity check pointer. All
subdisks in the plex must be up for a parity check.resetconfig
[-f
]gvinum
configuration.rm
[-r
] volume |
plex | subdisk-r
is specified, its
subordinate objects.saveconfig
gvinum
configuration to disk after
configuration failures.setstate
[-f
] state volume |
plex | subdisk |
drive-f
flag forces state changes regardless of
whether they are legal.start
start
[-S
size]
volume | plex |
subdisk-S
flag is currently ignored.stop
[-f
] [volume |
plex | subdisk]gvinum
if
no parameters are specified.stripe
[-fv
] [-n
name] drivesgvinum
.
This organization requires at least two drives.The gvinum
utility communicates with the
kernel component of the GVinum logical volume manager. It 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, gvinum
maintains a command line
history.
The gvinum
commands may be followed by an
option.
-f
-f
(“force”) option overrides
safety checks. It should be used with extreme caution. This option is
required in order to use the move
command.-r
-r
(“recursive”) option applies
the command recursively to subordinate objects. For example, in
conjunction with the lv
command, the
-r
option will also show information about the
plexes and subdisks belonging to the volume. It is also used by the
rename
command to indicate that subordinate
objects such as subdisks should be renamed to match the object(s)
specified and by the rm
command to delete plexes
belonging to a volume and so on.-v
-v
(“verbose”) option provides
more detailed output.-V
-V
(“very verbose”) option
provides even more detailed output than -v
.gvinum
objectsTo create a mirror on disks /dev/ada1 and /dev/ada2, create a
filesystem, mount, unmount and then stop gvinum
:
gvinum mirror /dev/ada1
/dev/ada2
newfs
/dev/gvinum/gvinumvolume0
mount /dev/gvinum/gvinumvolume0
/mnt
...
unmount /mnt
gvinum stop
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
newfs /dev/gvinum/data
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
volume myraid5vol
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 first appeared in
FreeBSD 5.3. The vinum
utility, on which gvinum
is based, was written by
Greg Lehey.
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.
Lukas Ertl
<le@FreeBSD.org>
Chris Jones
<soc-cjones@FreeBSD.org>
Ulf Lilleengen
<lulf@FreeBSD.org>
Currently, gvinum
does not rename devices
in /dev/gvinum until reloaded.
The -S
initsize flag to
start
is ignored.
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:
debug
debug
flagsdumpconfig
[drive ...]info
[-vV
]label
volumeresetstats
[-r
] [volume |
plex | subdisk]setdaemon
[value]March 28, 2021 | midnightbsd-3.1 |