From: NeilBrown Date: Fri, 13 Nov 2009 06:40:51 +0000 (+1100) Subject: Don't unconditionally set in_sync on newly added device in raid5_reshape X-Git-Tag: v2.6.32-rc8~38^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7ef90146a14c2bb1de2e22399f147ebec5b74f0b;p=pandora-kernel.git Don't unconditionally set in_sync on newly added device in raid5_reshape When a reshape finds that it can add spare devices into the array, those devices might already be 'in_sync' if they are beyond the old size of the array, or they might not if they are within the array. The first case happens when we change an N-drive RAID5 to an N+1-drive RAID5. The second happens when we convert an N-drive RAID5 to an N+1-drive RAID6. So set the flag more carefully. Also, ->recovery_offset is only meaningful when the flag is clear, so only set it in that case. This change needs the preceding two to ensure that the non-in_sync device doesn't get evicted from the array when it is stopped, in the case where v0.90 metadata is used. Signed-off-by: NeilBrown --- Reading git-diff-tree failed