diff options
| author | Igor Konopko <[email protected]> | 2019-05-04 20:38:05 +0200 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2019-05-06 10:19:18 -0600 |
| commit | f2e024570ef1a3d443875f6063321ee2e503ceb1 (patch) | |
| tree | 38d0d4514b953abf1af92e4cb92acf325b0039e8 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 32ac0fa3afebb8b83e3f9189af1a481c0110fe51 (diff) | |
lightnvm: pblk: GC error handling
Currently when there is an IO error (or similar) on GC read path, pblk
still move the line, which was currently under GC process to free state.
Such a behaviour can lead to silent data mismatch issue.
With this patch, the line which was under GC process on which some IO
errors occurred, will be putted back to closed state (instead of free
state as it was without this patch) and the L2P mapping for such a
failed sectors will not be updated.
Then in case of any user IOs to such a failed sectors, pblk would be
able to return at least real IO error instead of stale data as it is
right now.
Signed-off-by: Igor Konopko <[email protected]>
Reviewed-by: Javier González <[email protected]>
Reviewed-by: Hans Holmberg <[email protected]>
Signed-off-by: Matias Bjørling <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions