| commit | 676e42d896ab6967859fabbb06f4e11b9615cbcf | [log] [tgz] |
|---|---|---|
| author | NeilBrown <neilb@suse.de> | Tue Jun 01 19:37:26 2010 +1000 |
| committer | NeilBrown <neilb@suse.de> | Mon Jul 26 12:52:27 2010 +1000 |
| tree | efab4dffe8e930ec9ef51a5a4d4fd04ffe3749b1 | |
| parent | f4be6b43f1ac60dff00ef0923ee43b0e08872947 [diff] |
md: be more careful setting MD_CHANGE_CLEAN When MD_CHANGE_CLEAN is set we might block in md_write_start. So we should only set it when fairly sure that something will clear it. There are two places where it is set so as to encourage a metadata update to record the progress of resync/recovery. This should only be done if the internal metadata update mechanisms are in use, which can be tested by by inspecting '->persistent'. Signed-off-by: NeilBrown <neilb@suse.de>