summaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
* md/raid1: fix buglet in md_raid1_contested.NeilBrown2012-02-131-1/+1
* md: two small fixes to handling interrupt resync.NeilBrown2012-02-071-2/+3
* Prevent DM RAID from loading bitmap twice.Jonathan Brassow2012-01-301-3/+9
* md/raid1: perform bad-block tests for WriteMostly devices too.NeilBrown2012-01-101-1/+10
* md: notify the 'degraded' sysfs attribute on failure.NeilBrown2012-01-101-0/+6
* md/raid1: Mark device want_replacement when we see a write error.NeilBrown2011-12-231-1/+15
* md/raid1: If there is a spare and a want_replacement device, start replacement.NeilBrown2011-12-231-2/+15
* md/raid1: recognise replacements when assembling arrays.NeilBrown2011-12-231-2/+23
* md/raid1: handle activation of replacement device when recovery completes.NeilBrown2011-12-231-3/+33
* md/raid1: Allow a failed replacement device to be removed.NeilBrown2011-12-231-0/+6
* md/raid1: Allocate spare to store replacement devices and their bios.NeilBrown2011-12-232-31/+40
* md/raid1: Replace use of mddev->raid_disks with conf->raid_disks.NeilBrown2011-12-231-3/+4
* md/raid10: If there is a spare and a want_replacement device, start replacement.NeilBrown2011-12-231-4/+36
* md/raid10: recognise replacements when assembling array.NeilBrown2011-12-231-0/+17
* md/raid10: Allow replacement device to be replace old drive.NeilBrown2011-12-231-11/+61
* md/raid10: handle recovery of replacement devices.NeilBrown2011-12-231-30/+80
* md/raid10: Handle replacement devices during resync.NeilBrown2011-12-231-7/+98
* md/raid10: writes should get directed to replacement as well as original.NeilBrown2011-12-231-9/+74
* md/raid10: allow removal of failed replacement devices.NeilBrown2011-12-231-25/+32
* md/raid10: preferentially read from replacement device if possible.NeilBrown2011-12-231-13/+23
* md/raid10: change read_balance to return an rdevNeilBrown2011-12-231-14/+13Star
* md/raid10: prepare data structures for handling replacement.NeilBrown2011-12-232-31/+78
* md/raid5: Mark device want_replacement when we see a write error.NeilBrown2011-12-231-0/+3
* md/raid5: If there is a spare and a want_replacement device, start replacement.NeilBrown2011-12-232-18/+28
* md/raid5: recognise replacements when assembling array.NeilBrown2011-12-231-6/+31
* md/raid5: handle activation of replacement device when recovery completes.NeilBrown2011-12-231-7/+62
* md/raid5: detect and handle replacements during recovery.NeilBrown2011-12-232-30/+106
* md/raid5: writes should get directed to replacement as well as original.NeilBrown2011-12-232-23/+97
* md/raid5: allow removal for failed replacement devices.NeilBrown2011-12-231-26/+32
* md/raid5: preferentially read from replacement device if possible.NeilBrown2011-12-231-15/+54
* md/raid5: remove redundant bio initialisations.NeilBrown2011-12-231-8/+1Star
* md/raid5: raid5.h cleanupNeilBrown2011-12-231-18/+9Star
* md/raid5: allow each slot to have an extra replacement deviceNeilBrown2011-12-232-26/+46
* md: create externally visible flags for supporting hot-replace.NeilBrown2011-12-234-39/+125
* md: change hot_remove_disk to take an rdev rather than a number.NeilBrown2011-12-236-21/+18Star
* md: remove test for duplicate device when setting slot number.NeilBrown2011-12-231-5/+0Star
* md/bitmap: be more consistent when setting new bits in memory bitmap.NeilBrown2011-12-231-1/+1
* md: Fix userspace free_pages() macroSteven Rostedt2011-12-231-1/+1
* md/raid5: be more thorough in calculating 'degraded' value.NeilBrown2011-12-231-30/+33
* md/bitmap: daemon_work cleanup.NeilBrown2011-12-231-5/+5
* md: allow non-privileged uses to GET_*_INFO about raid arrays.NeilBrown2011-12-231-2/+9
* md/bitmap: It is OK to clear bits during recovery.NeilBrown2011-12-221-4/+1Star
* md: don't give up looking for spares on first failure-to-addNeilBrown2011-12-221-2/+1Star
* md/raid5: ensure correct assessment of drives during degraded reshape.NeilBrown2011-12-221-4/+10
* md/linear: fix hot-add of devices to linear arrays.NeilBrown2011-12-221-0/+1
* md: raid5 crash during degradationAdam Kwolek2011-12-091-2/+2
* md/raid5: never wait for bad-block acks on failed device.NeilBrown2011-12-081-1/+3
* md: ensure new badblocks are handled promptly.NeilBrown2011-12-081-0/+1
* md: bad blocks shouldn't cause a Blocked status on a Faulty device.NeilBrown2011-12-081-1/+2
* md: take a reference to mddev during sysfs access.NeilBrown2011-12-081-1/+18