summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2008-06-05 22:45:54 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-06-06 11:29:08 -0700
commitc337869d95011495fa181536786e74aa2d7ff031 (patch)
tree786cdf119ce33641438cd841deb0c480dd92f900 /Documentation
parenta6d8113a986c66aeb379a26b6e0062488b3e59e1 (diff)
downloadtalos-op-linux-c337869d95011495fa181536786e74aa2d7ff031.tar.gz
talos-op-linux-c337869d95011495fa181536786e74aa2d7ff031.zip
md: do not compute parity unless it is on a failed drive
If a block is computed (rather than read) then a check/repair operation may be lead to believe that the data on disk is correct, when infact it isn't. So only compute blocks for failed devices. This issue has been around since at least 2.6.12, but has become harder to hit in recent kernels since most reads bypass the cache. echo repair > /sys/block/mdN/md/sync_action will set the parity blocks to the correct state. Cc: <stable@kernel.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud