Man page update for containers etc.
Signed-off-by: NeilBrown <neilb@suse.de>
This commit is contained in:
parent
a9e1c11d8b
commit
90c8d6680d
16
mdadm.8
16
mdadm.8
|
@ -38,8 +38,9 @@ md devices,
|
||||||
.BR RAID6 ,
|
.BR RAID6 ,
|
||||||
.BR RAID10 ,
|
.BR RAID10 ,
|
||||||
.BR MULTIPATH ,
|
.BR MULTIPATH ,
|
||||||
|
.BR FAULTY ,
|
||||||
and
|
and
|
||||||
.BR FAULTY .
|
.BR CONTAINER .
|
||||||
|
|
||||||
.B MULTIPATH
|
.B MULTIPATH
|
||||||
is not a Software RAID mechanism, but does involve
|
is not a Software RAID mechanism, but does involve
|
||||||
|
@ -50,6 +51,19 @@ each device is a path to one common physical storage device.
|
||||||
is also not true RAID, and it only involves one device. It
|
is also not true RAID, and it only involves one device. It
|
||||||
provides a layer over a true device that can be used to inject faults.
|
provides a layer over a true device that can be used to inject faults.
|
||||||
|
|
||||||
|
B CONTAINER
|
||||||
|
is different again. A CONTAINER is a collection of devices that are
|
||||||
|
managed as a set. This is similar to the set of devices connected to
|
||||||
|
a hardware RAID controller. The set of devices may contain a number
|
||||||
|
of different RAID arrays each utilising some (or all) blocks from a
|
||||||
|
number of the devices in the set. For example, two devices in a 5-device set
|
||||||
|
might form a RAID1 used the whole devices. The remaining three might
|
||||||
|
have a RAID5 over the first half of each device, and a RAID0 over the
|
||||||
|
second half.
|
||||||
|
|
||||||
|
With a CONTAINER, there is one set of metadata the describes
|
||||||
|
|
||||||
|
|
||||||
.\".I mdadm
|
.\".I mdadm
|
||||||
.\"is a program that can be used to create, manage, and monitor
|
.\"is a program that can be used to create, manage, and monitor
|
||||||
.\"MD devices. As
|
.\"MD devices. As
|
||||||
|
|
Loading…
Reference in New Issue