linux.git/drivers/md/raid1.c, branch v2.6.33

md: add MODULE_DESCRIPTION for all md related modules.

2009-12-14T01:51:41+00:00

Suggested by  Oren Held 

Signed-off-by: NeilBrown

md: move offset, daemon_sleep and chunksize out of bitmap structure

2009-12-14T01:51:41+00:00

... and into bitmap_info.  These are all configuration parameters
that need to be set before the bitmap is created.

Signed-off-by: NeilBrown

md/raid1: add takeover support for raid5->raid1

2009-12-14T01:51:41+00:00

A 2-device raid5 array can now be converted to raid1.

Signed-off-by: NeilBrown

md: add honouring of suspend_{lo,hi} to raid1.

2009-12-14T01:51:40+00:00

This will allow us to stop writeout to portions of the array
while  they are resynced by someone else - e.g. another node in
a cluster.

Signed-off-by: NeilBrown

md: revert incorrect fix for read error handling in raid1.

2009-12-01T06:30:59+00:00

commit 4706b349f was a forward port of a fix that was needed
for SLES10.  But in fact it is not needed in mainline because
the earlier commit dd00a99e7a fixes the same problem in a
better way.
Further, this commit introduces a bug in the way it interacts with
the automatic read-error-correction.  If, after a read error is
successfully corrected, the same disk is chosen to re-read - the
re-read won't be attempted but an error will be returned instead.

After reverting that commit, there is the possibility that a
read error on a read-only array (where read errors cannot
be corrected as that requires a write) will repeatedly read the same
device and continue to get an error.
So in the "Array is readonly" case, fail the drive immediately on
a read error.

Signed-off-by: NeilBrown 
Cc: stable@kernel.org

md: raid1/raid10: handle allocation errors during array setup.

2009-10-16T04:55:44+00:00

Both raid1 and raid10 create a mempool during startup.
If the 'alloc' function for this mempool fails, unplug_slaves
is called.
If that happens when the pool is being initialised, unplug_slaves
will try to use the 'conf' structure that isn't filled in yet, and
badness will happen.

So ensure that unplug_slaves doesn't get called unless we know
that the conf structure if fully initialised.

Signed-off-by: NeilBrown

md/raid1/raid10: add a cond_resched

2009-10-16T04:55:32+00:00

During 'check' of a raid1 or raid10 it is possible for the management
thread to spend a lot of time running 'memcmp' on blocks from
different devices, so make sure the thread has a chance to schedule.
raid5d already has a cond_resched (in process_stripe).

Reported-By: Lee Howard 
Signed-off-by: NeilBrown

md: raid-1/10: fix RW bits manipulation

2009-09-23T08:20:15+00:00

Recently Jens has changed bio_rw_flagged() logic by following
commit 1f98a13f623e0ef666690a18c1250335fc6d7ef1. Now it returns
bool instead of int. This broke raid1/raid10 RW bits manipulation logic.
One of visible result is BUG_ON triggering due to empty barrier
here scsi_lib.c:1108 scsi_setup_fs_cmnd()

Signed-off-by: Dmitry Monakhov 
Signed-off-by: NeilBrown

md: report device as congested when suspended

2009-09-23T08:10:29+00:00

This should writeback from coming when the device is temporarily
suspended.

Signed-off-by: NeilBrown

md: Improve name of threads created by md_register_thread

2009-09-23T08:09:45+00:00

The management thread for raid4,5,6 arrays are all called
mdX_raid5, independent of the actual raid level, which is wrong and
can be confusion.

So change md_register_thread to use the name from the personality
unless no alternate name (like 'resync' or 'reshape') is given.

This is simpler and more correct.

Cc: Jinzc 
Signed-off-by: NeilBrown