[Bug 295055] zpool scrub hangs after a while

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 06 May 2026 13:31:10 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295055

            Bug ID: 295055
           Summary: zpool scrub hangs after a while
           Product: Base System
           Version: 15.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: pch-freebsd-bugs-1@u-1.phicoh.com

zpool scrub hangs after a while. I'm running 15.0-RELEASE-p8

After a while zpool status doesn't change anymore:
$ zpool status
  pool: zroot
 state: ONLINE
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A
  scan: scrub in progress since Wed May  6 11:37:49 2026
        3.25T / 3.32T scanned at 1.96K/s, 36.0G / 3.32T issued at 21B/s
        5.80M repaired, 1.06% done, no estimated completion time
config:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          raidz1-0  ONLINE       0     0     0
            ada1p4  ONLINE       0     0    36  (repairing)
            ada4p4  ONLINE       0     0    47  (repairing)
            ada3p4  ONLINE       0     0    43  (repairing)
            ada0p4  ONLINE       0     0    18  (repairing)
        logs    
          ada2p1    ONLINE       0     0     0

errors: 4 data errors, use '-v' for a list

"zpool scrub -s zroot" just hangs.

Sometimes the system panics with:
May  6 13:13:48 f250 kernel: Fatal trap 12: page fault while in kernel mode
May  6 13:13:48 f250 kernel: cpuid = 2; apic id = 02
May  6 13:13:48 f250 kernel: fault virtual address      = 0x80010
May  6 13:13:48 f250 kernel: fault code         = supervisor read data, page
not present
May  6 13:13:48 f250 kernel: instruction pointer        =
0x20:0xffffffff8103b12e
May  6 13:13:48 f250 kernel: stack pointer              =
0x28:0xfffffe0147287d20
May  6 13:13:48 f250 kernel: frame pointer              =
0x28:0xfffffe0147287d50
May  6 13:13:48 f250 kernel: code segment               = base 0x0, limit
0xfffff, type 0x1b
May  6 13:13:48 f250 kernel:                    = DPL 0, pres 1, long 1, def32
0, gran 1
May  6 13:13:48 f250 kernel: processor eflags   = interrupt enabled, resume,
IOPL = 0
May  6 13:13:48 f250 kernel: current process            = 12 (irq60: ahci0)
May  6 13:13:48 f250 kernel: rdi: fffff80001a96480 rsi: fffff80001aa3f00 rdx:
0000000000000002
May  6 13:13:48 f250 kernel: rcx: 0000000000000040  r8: fffffe014995b000  r9:
fffffe0147288000
May  6 13:13:48 f250 kernel: rax: ffffffff81949be0 rbx: fffff80001a96480 rbp:
fffffe0147287d50
May  6 13:13:48 f250 kernel: r10: 0000000000000001 r11: 0000000000002af8 r12:
0000000000080000
May  6 13:13:48 f250 kernel: r13: 0000000000000120 r14: 0000000000000000 r15:
fffffe01499595a8
May  6 13:13:48 f250 kernel: trap number                = 12
May  6 13:13:48 f250 kernel: panic: page fault
May  6 13:13:48 f250 kernel: cpuid = 2
May  6 13:13:48 f250 kernel: time = 1778065938
May  6 13:13:48 f250 kernel: KDB: stack backtrace:
May  6 13:13:48 f250 kernel: #0 0xffffffff80bbe1ad at kdb_backtrace+0x5d
May  6 13:13:48 f250 kernel: #1 0xffffffff80b71536 at vpanic+0x136
May  6 13:13:48 f250 kernel: #2 0xffffffff80b713f3 at panic+0x43
May  6 13:13:48 f250 kernel: #3 0xffffffff81079f99 at trap_pfault+0x3c9
May  6 13:13:48 f250 kernel: #4 0xffffffff81050028 at calltrap+0x8
May  6 13:13:48 f250 kernel: #5 0xffffffff804d9820 at
ahci_end_transaction+0x260
May  6 13:13:48 f250 kernel: #6 0xffffffff804d900f at ahci_ch_intr_main+0x52f
May  6 13:13:48 f250 kernel: #7 0xffffffff804d800e at ahci_ch_intr+0x4e
May  6 13:13:48 f250 kernel: #8 0xffffffff804d6653 at ahci_intr+0xf3
May  6 13:13:48 f250 kernel: #9 0xffffffff80b2b299 at ithread_loop+0x239
May  6 13:13:48 f250 kernel: #10 0xffffffff80b2782b at fork_exit+0x7b
May  6 13:13:48 f250 kernel: #11 0xffffffff8105104e at fork_trampoline+0xe
May  6 13:13:48 f250 kernel: Uptime: 6m38s

I can add the output of smartctl if desired, but as far as I can tell there is
nothing special there.

-- 
You are receiving this mail because:
You are the assignee for the bug.