From: NeilBrown Date: Tue, 26 May 2009 02:57:21 +0000 (+1000) Subject: md: don't update curr_resync_completed without also updating reshape_position. X-Git-Tag: v2.6.30-rc8~58^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b;p=pandora-kernel.git md: don't update curr_resync_completed without also updating reshape_position. In order for the metadata to always be consistent, we mustn't updated curr_resync_completed without also updating reshape_position. The reshape code updates both at the same time. However since commit 97e4f42d62badb0f9fbc27c013e89bc1336a03bc the common md_do_sync will sometimes update curr_resync_completed but is not in a position to update reshape_position. So if MD_RECOVERY_RESHAPE is set (indicating that a reshape is happening, so reshape_position might change), don't update curr_resync_completed in md_do_sync, leave it to the per-personality reshape code. Signed-off-by: NeilBrown --- Reading git-diff-tree failed