diff options
| author | Heinz Mauelshagen <heinzm@redhat.com> | 2014-09-24 19:47:19 +0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2014-10-06 04:03:36 +0400 |
| commit | 48cf06bc5f508d5f71bc0fd7530daebb12a48428 (patch) | |
| tree | 17a0a3c51bde7dcee9ce0e45a4799d83b254dbbd /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 75b8e04bbf01bdd5c42a1d8ac54abf757196ce49 (diff) | |
| download | linux-48cf06bc5f508d5f71bc0fd7530daebb12a48428.tar.xz | |
dm raid: add discard support for RAID levels 4, 5 and 6
In case of RAID levels 4, 5 and 6 we have to verify each RAID members'
ability to zero data on discards to avoid stripe data corruption -- if
discard_zeroes_data is not set for each RAID member discard support must
be disabled. But given the uncertainty of whether or not a RAID member
properly supports zeroing data on discard we require the user to
explicitly allow discard support on RAID levels 4, 5, and 6 by setting
a dm-raid module paramter, e.g.: dm-raid.devices_handle_discard_safely=Y
Otherwise, discards could cause data corruption on RAID4/5/6.
Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions