Commit ffa23322b1596bb1a115e767d4251b62842adc23
1 parent
ece5cff0da
Exists in
master
and in
7 other branches
md/bitmap: update dirty flag when bitmap bits are explicitly set.
There is a sysfs file which allows bits in the write-intent bitmap to be explicit set - indicating that the block is thought to be 'dirty'. When this happens we should really set recovery_cp backwards to include the block to reflect this dirtiness. In particular, a 'resync' process will refuse to start if recovery_cp is beyond the end of the array, so this is needed to allow a resync to be triggered. Signed-off-by: NeilBrown <neilb@suse.de>
Showing 1 changed file with 6 additions and 0 deletions Side-by-side Diff
drivers/md/bitmap.c
| ... | ... | @@ -1566,6 +1566,12 @@ |
| 1566 | 1566 | sector_t sec = (sector_t)chunk << CHUNK_BLOCK_SHIFT(bitmap); |
| 1567 | 1567 | bitmap_set_memory_bits(bitmap, sec, 1); |
| 1568 | 1568 | bitmap_file_set_bit(bitmap, sec); |
| 1569 | + if (sec < bitmap->mddev->recovery_cp) | |
| 1570 | + /* We are asserting that the array is dirty, | |
| 1571 | + * so move the recovery_cp address back so | |
| 1572 | + * that it is obvious that it is dirty | |
| 1573 | + */ | |
| 1574 | + bitmap->mddev->recovery_cp = sec; | |
| 1569 | 1575 | } |
| 1570 | 1576 | } |
| 1571 | 1577 |