diff options
author | Neil Brown <neilb@suse.de> | 2002-03-15 05:21:36 +0000 |
---|---|---|
committer | Neil Brown <neilb@suse.de> | 2002-03-15 05:21:36 +0000 |
commit | 56eb10c0b6e8f21540af444c8a28aa9e8f138ce6 (patch) | |
tree | 3b791ce573cca8c746f318411cb63d8c677678a1 /md.4 | |
parent | 9a9dab3670110c2db7fe6f716977b72adedbf855 (diff) | |
download | mdadm-56eb10c0b6e8f21540af444c8a28aa9e8f138ce6.tar.gz mdadm-56eb10c0b6e8f21540af444c8a28aa9e8f138ce6.tar.xz mdadm-56eb10c0b6e8f21540af444c8a28aa9e8f138ce6.zip |
mdadm-0.7.1mdadm-0.7.1
Diffstat (limited to 'md.4')
-rw-r--r-- | md.4 | 78 |
1 files changed, 78 insertions, 0 deletions
@@ -0,0 +1,78 @@ +.TH MD 4 +.SH NAME +md \- Multiple Device driver aka Linux Software Raid +.SH SYNOPSIS +.BI /dev/md n +.br +.BI /dev/md/ n +.SH DESCRIPTION +The +.B md +driver provides virtual devices that are created from one or more +independant underlying devices. This array of devices often contains +redundancy, and hence the acronym RAID which stands for a Redundant +Array of Independant Devices. +.PP +.B md +support RAID levels 1 (mirroring) 4 (striped array with parity device) and 5 +(striped array with distributed parity information. If a single underlying +device fails while using one of these level, they array will continue +to function. +.PP +.B md +also supports a number of pseudo RAID (non-redundant) configuations +including RAID0 (striped array), LINEAR (catenated array) and +MULTIPATH (a set of different interfaces to the same device). + +.SS RAID SUPER BLOCK +With the exception of Legacy Arrays described below, each device that +is incorportated into an MD array has a +.I super block +written towards the end of the device. This superblock records +information about the structure and state of the array so that the +array an be reliably re-assembled after a shutdown. + +The superblock is 4K long and is written into a 64K aligned block that +start at least 64K and less than 128K from the end of the device +(i.e. to get the address of the superblock round the size of the +device down to a multiple of 64K and then subtract 64K). +The available size of each device is the ammount of space before the +super block, so between 64K and 128K is lost when a device in +incorporated into an MD array. + +The superblock contains, among other things: +.TP +LEVEL +The +.TP +UUID +a 128 bit Universally Unique Identifier that identifies the array that +this device is part of. + +.SS LINEAR +.SS RAID0 +.SS RAID1 +.SS RAID4 +.SS RAID5 +.SS REBUILD/RESYNC +.SH FILES +.TP +.B /proc/mdstat +Contains information about the status of currently running array. +.TP +.B /proc/sys/dev/raid/speed_limit_min +A readable and writable file that reflects the current goal rebuild +speed for times when non-rebuild activity is current on an array. +The speed is in Kibibytes per second, and is a per-device rate, not a +per-array rate (which means that an array with more disc will shuffle +more data for a given speed). The default is 100. + +.TP +.B /proc/sys/dev/raid/speed_limit_max +A readable and writable file that reflects the current goal rebuild +speed for times when no non-rebuild activity is current on an array. +The default is 100,000. + +.SH SEE ALSO +.BR mdadm (8), +.BR mkraid (8). |