diff options
author | 2020-07-02 15:23:32 +0300 | |
---|---|---|
committer | 2020-07-27 12:55:40 +0200 | |
commit | 814723e0a55a9576b1d17f4fa8811086a24dd3e8 (patch) | |
tree | d95e646ca9f47fdc186d6e35d1c63b47c594348c /tools/perf/scripts/python/export-to-postgresql.py | |
parent | btrfs: don't check for btrfs_device::bdev in btrfs_end_bio (diff) | |
download | wireguard-linux-814723e0a55a9576b1d17f4fa8811086a24dd3e8.tar.xz wireguard-linux-814723e0a55a9576b1d17f4fa8811086a24dd3e8.zip |
btrfs: increment device corruption error in case of checksum error
Now that btrfs_io_bio have access to btrfs_device we can safely
increment the device corruption counter on error. There is one notable
exception - repair bios for raid. Since those don't go through the
normal submit_stripe_bio callpath but through raid56_parity_recover thus
repair bios won't have their device set.
Scrub increments the corruption counter for checksum mismatch as well
but does not call this function.
Link: https://lore.kernel.org/linux-btrfs/4857863.FCrPRfMyHP@liv/
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions