diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2008-06-06 07:45:54 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-06-06 20:29:08 +0200 |
| commit | c337869d95011495fa181536786e74aa2d7ff031 (patch) | |
| tree | 786cdf119ce33641438cd841deb0c480dd92f900 /Documentation | |
| parent | md: fix uninitialized use of mddev->recovery_wait (diff) | |
| download | linux-c337869d95011495fa181536786e74aa2d7ff031.tar.xz 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