diff options
| author | Jonathan Brassow <jbrassow@redhat.com> | 2012-10-11 13:42:19 +1100 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-10-11 13:42:19 +1100 |
| commit | 761becff016b82a6a7a1b2ef224248da5f46bae9 (patch) | |
| tree | bf9e1b479b85c659c9f54cb479bed9804484c011 /lib/raid6 | |
| parent | 7386199c471f70526bbcc629f072a5a8effe218f (diff) | |
| download | op-kernel-dev-761becff016b82a6a7a1b2ef224248da5f46bae9.zip op-kernel-dev-761becff016b82a6a7a1b2ef224248da5f46bae9.tar.gz | |
DM RAID: Fix for "sync" directive ineffectiveness
There are two table arguments that can be given to a DM RAID target
that control whether the array is forced to (re)synchronize or skip
initialization: "sync" and "nosync". When "sync" is given, we set
mddev->recovery_cp to 0 in order to cause the device to resynchronize.
This is insufficient if there is a bitmap in use, because the array
will simply look at the bitmap and see that there is no recovery
necessary.
The fix is to skip over the loading of the superblocks when "sync" is
given, causing new superblocks to be written that will force the array
to go through initialization (i.e. synchronization).
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'lib/raid6')
0 files changed, 0 insertions, 0 deletions
