aboutsummaryrefslogtreecommitdiff
path: root/Documentation/device-mapper/dm-log.txt
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2011-08-02 12:32:07 +0100
committerAlasdair G Kergon <agk@redhat.com>2011-08-02 12:32:07 +0100
commitb12d437b73d32203a41fde0d407e91812c866844 (patch)
tree3c7a33f4a45779da4a5edb71678ce7f8ae4169e7 /Documentation/device-mapper/dm-log.txt
parent46bed2b5c16bb7c82e1088d7ae75fb958c8a8c4e (diff)
dm raid: support metadata devices
Add the ability to parse and use metadata devices to dm-raid. Although not strictly required, without the metadata devices, many features of RAID are unavailable. They are used to store a superblock and bitmap. The role, or position in the array, of each device must be recorded in its superblock. This is to help with fault handling, array reshaping, and sanity checks. RAID 4/5/6 devices must be loaded in a specific order: in this way, the 'array_position' field helps validate the correctness of the mapping when it is loaded. It can be used during reshaping to identify which devices are added/removed. Fault handling is impossible without this field. For example, when a device fails it is recorded in the superblock. If this is a RAID1 device and the offending device is removed from the array, there must be a way during subsequent array assembly to determine that the failed device was the one removed. This is done by correlating the 'array_position' field and the bit-field variable 'failed_devices'. Signed-off-by: Jonathan Brassow <jbrassow@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Diffstat (limited to 'Documentation/device-mapper/dm-log.txt')
0 files changed, 0 insertions, 0 deletions