Christopher Haster 77e3078b9f Added/fixed tests for noop writes (where bd error can't be trusted) ...

It's interesting how many ways block devices can show failed writes:
1. prog can error
2. erase can error
3. read can error after writing (ECC failure)
4. prog doesn't error but doesn't write the data correctly
5. erase doesn't error but doesn't erase correctly

Can read fail without an error? Yes, though this appears the same as
prog and erase failing.

These weren't all simulated by testbd since I unintentionally assumed
the block device could always error. Fixed by added additional bad-black
behaviors to testbd.

Note: This also includes a small fix where we can miss bad writes if the
underlying block device contains a valid commit with the exact same
size in the exact same offset.

2020-02-09 12:00:22 -06:00

..

explode_asserts.py

Rewrote explode_asserts.py to be more efficient

2020-01-26 23:53:53 -06:00

prefix.py

Mark all Python 2 scripts as Python 2

2019-06-07 04:09:44 +02:00

readblock.py

Added/improved disk-reading debug scripts

2020-01-20 19:27:27 -06:00

readmdir.py

Fixed issues with neighbor updates during moves

2020-01-20 19:27:27 -06:00

readtree.py

Fixed more bugs, mostly related to ENOSPC on different geometries

2020-02-09 11:54:22 -06:00

test.py

Added/fixed tests for noop writes (where bd error can't be trusted)

2020-02-09 12:00:22 -06:00