diff options
| author | Heinz Mauelshagen <heinzm@redhat.com> | 2017-12-13 19:13:18 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2017-12-13 19:52:02 +0300 |
| commit | 11e4723206683ad59f8e9dc7771e7b44a37f7b62 (patch) | |
| tree | 0ef98a68bb0a8722a4765eac7be2fb3204fa8c92 /Documentation/device-mapper | |
| parent | 53bf5384f9b9e37c628f171366959a38c89779ca (diff) | |
| download | linux-11e4723206683ad59f8e9dc7771e7b44a37f7b62.tar.xz | |
dm raid: stop keeping raid set frozen altogether
In order to avoid redoing synchronization/recovery/reshape partially,
the raid set got frozen until after all passed in table line flags had
been cleared. The related table reload sequence had to be precisely
followed, or reshaping may lead to data corruption caused by the active
mapping carrying on with a reshape when the inactive mapping already
had retrieved a stale reshape position.
Harden by retrieving the actual resync/recovery/reshape position
during resume whilst the active table is suspended thus avoiding
to keep the raid set frozen altogether. This prevents superfluous
redoing of an already resynchronized or recovered segment and,
most importantly, potential for redoing of an already reshaped
segment causing data corruption.
Fixes: d39f0010e ("dm raid: fix raid_resume() to keep raid set frozen as needed")
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'Documentation/device-mapper')
| -rw-r--r-- | Documentation/device-mapper/dm-raid.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/device-mapper/dm-raid.txt b/Documentation/device-mapper/dm-raid.txt index 7b22375091fa..390c145f01d7 100644 --- a/Documentation/device-mapper/dm-raid.txt +++ b/Documentation/device-mapper/dm-raid.txt @@ -347,3 +347,4 @@ Version History 1.13.0 Fix dev_health status at end of "recover" (was 'a', now 'A') 1.13.1 Fix deadlock caused by early md_stop_writes(). Also fix size an state races. +1.13.2 Fix raid redundancy validation and avoid keeping raid set frozen |