| 6.18 #11 | ahive | scrub-stale-extent 64K replace | 0/10 |
| 6.18 #11 | ahive | scrub-stale-extent 64K scrub | 0/10 |
| misc-next zb64 a6ceb4e01937 #76 | dhive | scrub-stale-extent 64K replace / scrub | 0/5 / 0/5 |
-| 7.3 zb64 #10 | ehive | scrub-stale-extent 64K replace / scrub | 0/5 / 0/5 |
+| 7.3 zb64 4190b99b2ae8 #10 | ehive | scrub-stale-extent 64K replace / scrub | 0/5 / 0/5 |
Every run: btrfs check clean (6.18: only the baselined pre-existing
"Space key" line), ro scrub clean, every acked file verified, other klog
lines 0, taint 0, debug_locks 1, no unwritten-on-end or NORESERVE lines.
Per-commit buildcheck (fs/btrfs at the topic commit + full vmlinux link,
the lane zb64 .config, btrfs DEBUG/ASSERT on; the topic adds no Kconfig
-symbol): 6.18 and misc-next 0 failures, 0 new warnings, link rc 0.
+symbol): 6.18, misc-next and 7.3 0 failures, 0 new warnings, link rc 0.
6.18 #11 is the rd1110 6.18 zb64+fix build: its tree equals the
promoted zb64's, so kbuild had nothing to rebuild.
+Promoted 2026-11-11 (pc1111), with the replace-finish-deadlock patch 2
+changelog reword (trees unchanged) in the same lane move:
+6.18 testing 90ef266ec558, zb64 491cbce70bd4; misc-next testing
+6f8be7703b41, zb64 a6ceb4e01937; 7.3 testing 5eedf7f9826c, zb64
+4190b99b2ae8. The rf1109 replace + read-repair gate (gate-rf.sh) runs
+on 6.18 #11 as a trailer; results in forensics/pc1111.
+
Found by rd1110 (2026-11-10; forensics `raid56-wh-harness/forensics/rd1110/`)
chasing a one-off replace-discard-test.sh dsync-raid1 cancel from rh1108;
promoted by pc1111 (forensics `raid56-wh-harness/forensics/pc1111/`).