Attachment 295735 Details for Bug 434670 – Patch to clean up mdadm.8

[patch] Patch to clean up mdadm.8

mdadm.8.patch (text/plain), 3.45 KB, created by Chris Pepper on 2008-02-24 06:11:51 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chris Pepper

Created: 2008-02-24 06:11:51 UTC

Size: 3.45 KB

patch

obsolete

>--- mdadm.8	2008-02-24 00:51:47.000000000 -0500
>+++ mdadm.8.pepper	2008-02-24 01:03:57.000000000 -0500
>@@ -175,7 +175,7 @@
> .BR --fail ,
> or
> .BR --remove ,
>-then the MANAGE mode is assume.
>+then the MANAGE mode is assumed.
> Anything other than these will cause the
> .B Misc
> mode to be assumed.
>@@ -817,25 +817,25 @@
> .P
> Each of these options require that the first device list is the array
> to be acted upon and the remainder are component devices to be added,
>-removed, or marked as fault.  Several different operations can be
>+removed, or marked as faulty.  Several different operations can be
> specified for different devices, e.g.
> .in +5
> mdadm /dev/md0 --add /dev/sda1 --fail /dev/sdb1 --remove /dev/sdb1
> .in -5
> Each operation applies to all devices listed until the next
>-operations.
>+operation.
> 
> If an array is using a write-intent bitmap, then devices which have
> been removed can be re-added in a way that avoids a full
>-reconstruction but instead just updated the blocks that have changed
>+reconstruction but instead just updates the blocks that have changed
> since the device was removed.  For arrays with persistent metadata
> (superblocks) this is done automatically.  For arrays created with
> .B --build
>-mdadm needs to be told that this device we removed recently with
>+mdadm needs to be told that this device was removed recently with
> .B --re-add.
> 
> Devices can only be removed from an array if they are not in active
>-use.  i.e. that must be spares or failed devices.  To remove an active
>+use.  i.e., they must be spares or failed devices.  To remove an active
> device, it must be marked as
> .B faulty
> first.
>@@ -1601,20 +1601,20 @@
> A RAID1 array can work with any number of devices from 1 upwards
> (though 1 is not very useful).  There may be times which you want to
> increase or decrease the number of active devices.  Note that this is
>-different to hot-add or hot-remove which changes the number of
>+different than hot-add or hot-remove, which change the number of
> inactive devices.
> 
> When reducing the number of devices in a RAID1 array, the slots which
> are to be removed from the array must already be vacant.  That is, the
>-devices that which were in those slots must be failed and removed.
>+devices which were in those slots must be failed and removed.
> 
> When the number of devices is increased, any hot spares that are
> present will be activated immediately.
> 
> Increasing the number of active devices in a RAID5 is much more
>-effort.  Every block in the array will need to be read and written
>-back to a new location.  From 2.6.17, the Linux Kernel is able to do
>-this safely, including restart and interrupted "reshape".
>+work.  Every block in the array will need to be read and written
>+back to a new location.  From 2.6.17, the Linux kernel is able to do
>+this safely, including restarting an interrupted "reshape" operation.
> 
> When relocating the first few stripes on a raid5, it is not possible
> to keep the data on disk completely consistent and crash-proof.  To
>@@ -1632,8 +1632,8 @@
> .SS BITMAP CHANGES
> 
> A write-intent bitmap can be added to, or removed from, an active
>-array.  Either internal bitmaps, or bitmaps stored in a separate file
>-can be added.  Note that if you add a bitmap stored in a file which is
>+array.  Either internal bitmaps, or bitmaps stored in separate files,
>+can be added.  Note that if you add a bitmap in a file which is
> in a filesystem that is on the raid array being affected, the system
> will deadlock.  The bitmap must be on a separate filesystem.
>

Actions: View | Diff

Attachments on bug 434670: 295735