diff options
| author | NeilBrown <neilb@suse.com> | 2016-11-04 08:46:03 +0300 |
|---|---|---|
| committer | Shaohua Li <shli@fb.com> | 2016-11-08 02:08:23 +0300 |
| commit | a9ae93c8cc0b63d8283f335604362f903d2244e2 (patch) | |
| tree | 5db1b0b94eca87a7251d774b0a75c0bb690e4312 /fs/exec.c | |
| parent | 5e2c7a3611977b69ae0531e8fbdeab5dad17925a (diff) | |
| download | linux-a9ae93c8cc0b63d8283f335604362f903d2244e2.tar.xz | |
md/raid10: abort delayed writes when device fails.
When writing to an array with a bitmap enabled, the writes are grouped
in batches which are preceded by an update to the bitmap.
It is quite likely if that a drive develops a problem which is not
media related, that the bitmap write will be the first to report an
error and cause the device to be marked faulty (as the bitmap write is
at the start of a batch).
In this case, there is point submiting the subsequent writes to the
failed device - that just wastes times.
So re-check the Faulty state of a device before submitting a
delayed write.
This requires that we keep the 'rdev', rather than the 'bdev' in the
bio, then swap in the bdev just before final submission.
Reported-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Diffstat (limited to 'fs/exec.c')
0 files changed, 0 insertions, 0 deletions