aboutsummaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-10-16 16:35:30 +1100
committerNeilBrown <neilb@suse.de>2009-10-16 16:35:30 +1100
commit5e5e3e78ed9038b8f7112835d07084eefb9daa47 (patch)
treeafcefac7c0dbafb71f09d90812eecb2c6e4bc766 /crypto
parente4424fee1815f996dccd36be44d68ca160ec3e1b (diff)
downloadkernel_samsung_espresso10-5e5e3e78ed9038b8f7112835d07084eefb9daa47.zip
kernel_samsung_espresso10-5e5e3e78ed9038b8f7112835d07084eefb9daa47.tar.gz
kernel_samsung_espresso10-5e5e3e78ed9038b8f7112835d07084eefb9daa47.tar.bz2
md: Fix handling of raid5 array which is being reshaped to fewer devices.
When a raid5 (or raid6) array is being reshaped to have fewer devices, conf->raid_disks is the latter and hence smaller number of devices. However sometimes we want to use a number which is the total number of currently required devices - the larger of the 'old' and 'new' sizes. Before we implemented reducing the number of devices, this was always 'new' i.e. ->raid_disks. Now we need max(raid_disks, previous_raid_disks) in those places. This particularly affects assembling an array that was shutdown while in the middle of a reshape to fewer devices. md.c needs a similar fix when interpreting the md metadata. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions