diff options
| author | Heinz Mauelshagen <heinzm@redhat.com> | 2016-12-01 00:31:05 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2017-01-25 14:49:06 +0300 |
| commit | 63c32ed4afc2afd6b5551a8fcdea5b546dcaca4f (patch) | |
| tree | 8cdb6bf0a8080912d2590a3d5513b23b8c51ddd1 /block/t10-pi.c | |
| parent | 50c4feb9a3e3df9574d952a4ed2f009f8135e4c7 (diff) | |
| download | linux-63c32ed4afc2afd6b5551a8fcdea5b546dcaca4f.tar.xz | |
dm raid: add raid4/5/6 journaling support
Add md raid4/5/6 journaling support (upstream commit bac624f3f86a started
the implementation) which closes the write hole (i.e. non-atomic updates
to stripes) using a dedicated journal device.
Background:
raid4/5/6 stripes hold N data payloads per stripe plus one parity raid4/5
or two raid6 P/Q syndrome payloads in an in-memory stripe cache.
Parity or P/Q syndromes used to recover any data payloads in case of a disk
failure are calculated from the N data payloads and need to be updated on the
different component devices of the raid device. Those are non-atomic,
persistent updates. Hence a crash can cause failure to update all stripe
payloads persistently and thus cause data loss during stripe recovery.
This problem gets addressed by writing whole stripe cache entries (together with
journal metadata) to a persistent journal entry on a dedicated journal device.
Only if that journal entry is written successfully, the stripe cache entry is
updated on the component devices of the raid device (i.e. writethrough type).
In case of a crash, the entry can be recovered from the journal and be written
again thus ensuring consistent stripe payload suitable to data recovery.
Future dependencies:
once writeback caching being worked on to compensate for the throughput
implictions involved with writethrough overhead is supported with journaling
in upstream, an additional patch based on this one will support it in dm-raid.
Journal resilience related remarks:
because stripes are recovered from the journal in case of a crash, the
journal device better be resilient. Resilience becomes mandatory with
future writeback support, because loosing the working set in the log
means data loss as oposed to writethrough, were the loss of the
journal device 'only' reintroduces the write hole.
Fix comment on data offsets in parse_dev_params() and initialize
new_data_offset as well.
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'block/t10-pi.c')
0 files changed, 0 insertions, 0 deletions