"'btrfs replace' hangs at end of replacing a device (v5.10.82)" commit,
which only turned the replace_wait wake-up into a barrier one and is
superseded); 6.18 topic 011ce9c6fc1a on read-repair-fixes (testing
-27ece222af65, zb64 f3ecfc5af7f8); 7.3 topic 0b22c35e0e7b (testing and results: added after the 7.3 gate).
+27ece222af65, zb64 f3ecfc5af7f8); 7.3 topic 0b22c35e0e7b (testing 7ab729bb2f60, zb64 ace590553e2b; the 7.3 kernels were built from these zb64 commits directly).
Tested kernels: candidates refs/cand/rf1109/<lane>/zb64 (before lr1109b
moved the lanes; topic commits identical) and the re-merged
| misc-next zb64-2 non-KASAN #329 (efaeb5436501, boot smoke) | 4/4 | | 4/4 | 4/4 |
| 6.18 KASAN #324 (02c8a58382aa) | 12/12 | | 12/12 | 12/12 |
| 6.18 non-KASAN #325 (02c8a58382aa) | 12/12 | 12/12 | 12/12 | 12/12 |
+| 7.3 KASAN+FI #327 (ace590553e2b) | 12/12 | 12/12 | 12/12 | 12/12 |
+| 7.3 non-KASAN #328 (ace590553e2b) | 12/12 | 12/12 | 12/12 | 12/12 |
Without the series (rh1108, misc-next): r5 hangs in about half the
replaces; r5tp64 hangs in patch 2's cycle (counter 2, two readers asleep
"FAULT_INJECTION: forcing a failure" stack dumps of the inject arm;
unwritten-on-end lines 0.
-| step | misc-next #11 | 6.18 #326 (f3ecfc5af7f8) |
-|---|---|---|
-| rb1028 (replace-uncorrectable, scrub-uncorrectable-rc, failing-member-scrub) | PASS (VERDICT ok) | PASS (VERDICT ok) |
-| read-repair-submit-fail: repair x2 | PASS, PASS | PASS, INVALID (no read hit the bad mirror); rerun PASS, PASS |
-| read-repair-submit-fail: abortgood | PASS | PASS |
-| read-repair-submit-fail: scrubabort | INVALID (by design since replace-fixes p10: scrub stops at the fs error) | INVALID (same) |
-| read-repair-submit-fail: shutdown | PASS | (no shutdown ioctl on 6.18) |
-| read-repair-submit-fail: inject x3 | first run INVALID (harness: the repair stack is now btrfs_repair_read_work; fixed c9345315); rerun PASS x3 (EIO in ~1 s) | first run INVALID (same, + /dev/loopN naming); rerun PASS x3 (EIO in ~5 s) |
-| corrupt-recovery | PASS | PASS |
-| replace-status | PASS (= replace-fixes TESTING.md expectations) | same |
-| replace-cancel-persist | PASS (CANCELED/CANCELED/FINISHED, remounts ok) | same |
-| scrub-repair-werr | PASS | PASS |
-| scrub-fserror-stop | replace PASS, scrub INVALID ended_at_abort (known) | same |
-| replace-resume-gap | 3/3 PASS | 3/3 PASS |
-| alloc-hints-replace | PASS | PASS |
-| replace-discard (11 cases incl. dsync-raid1) | 11/11 PASS | 11/11 PASS |
-| unwritten-readback | PASS | FAIL: known retry-artifact class (arm C, 9 stripes; parity, scrub and degraded reads ok) |
-| replace-abort | 10/10 PASS | 10/10 PASS |
-| r5two (sa1 abortflag) | done, M0..M3 as predicted | same |
+| step | misc-next #11 | 6.18 #326 (f3ecfc5af7f8) | 7.3 #327 (ace590553e2b) |
+|---|---|---|---|
+| rb1028 (replace-uncorrectable, scrub-uncorrectable-rc, failing-member-scrub) | PASS (VERDICT ok) | PASS (VERDICT ok) | PASS (VERDICT ok) |
+| read-repair-submit-fail: repair x2 | PASS, PASS | PASS, INVALID (no read hit the bad mirror); rerun PASS, PASS | PASS, PASS |
+| read-repair-submit-fail: abortgood | PASS | PASS | PASS |
+| read-repair-submit-fail: scrubabort | INVALID (by design since replace-fixes p10: scrub stops at the fs error) | INVALID (same) | INVALID (scrub too close to the bad sector / done at the abort) |
+| read-repair-submit-fail: shutdown | PASS | (no shutdown ioctl on 6.18) | PASS |
+| read-repair-submit-fail: inject x3 | first run INVALID (harness: the repair stack is now btrfs_repair_read_work; fixed c9345315); rerun PASS x3 (EIO in ~1 s) | first run INVALID (same, + /dev/loopN naming); rerun PASS x3 (EIO in ~5 s) | PASS x3 (EIO in ~3 s) |
+| corrupt-recovery | PASS | PASS | PASS |
+| replace-status | PASS (= replace-fixes TESTING.md expectations) | same | same |
+| replace-cancel-persist | PASS (CANCELED/CANCELED/FINISHED, remounts ok) | same | same |
+| scrub-repair-werr | PASS | PASS | PASS |
+| scrub-fserror-stop | replace PASS, scrub INVALID ended_at_abort (known) | same | both arms INVALID ended_at_abort in the gate; rerun (gate-73k2-sfs): replace PASS, scrub INVALID ended_at_abort (known) |
+| replace-resume-gap | 3/3 PASS | 3/3 PASS | 3/3 PASS |
+| alloc-hints-replace | PASS | PASS | PASS |
+| replace-discard (11 cases incl. dsync-raid1) | 11/11 PASS | 11/11 PASS | 11/11 PASS |
+| unwritten-readback | PASS | FAIL: known retry-artifact class (arm C, 9 stripes; parity, scrub and degraded reads ok) | FAIL: same retry-artifact class (arm C, 3 "never" stripes written by raid56; scrub corrected the expected 176; degraded reads ok) |
+| replace-abort | 10/10 PASS | 10/10 PASS | 10/10 PASS |
+| r5two (sa1 abortflag) | done, M0..M3 as predicted | same | done, M1..M3 OK=101631 |
No FAIL is ENOSPC or loss of acked data except the r6p 2 GiB setup
-ENOSPC above; the 6.18 unwritten-readback FAIL is the known harness
+ENOSPC above; the 6.18 and 7.3 unwritten-readback FAILs are the known harness
retry artifact (no data lost: every reported block reads back through
parity, scrub clean).