Bug 228019

Summary: Panic and fsck -p insufficiency
Product: Base System Reporter: Poul-Henning Kamp <phk>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: ---    
Version: CURRENT   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
photo of LORs + panic messages none

Description Poul-Henning Kamp freebsd_committer freebsd_triage 2018-05-06 11:54:33 UTC
Created attachment 193083 [details]
photo of LORs + panic messages

AMD64 FreeBSD 12.0-CURRENT #1 r333269: Sat May  5 11:47:44 UTC 2018

While compiling lang/rust

    panic: Bad link elm 0xfffff8042e7cf40 prev->next != elm
    cpuid = 1
    time = 1525606495
    KDB: stack backtrace:
    db_trace_self_wrapper ...
    vpanic() ...
    panic() ...
    vm_pqbatch_process_page() + 0x276
    vm_pqbatch_submit_page() + 0x143
    vm_fault_hold() + 0x1d12
    ...

(See attached photo for more)

On reboot into single-user, fsck -p reports a lot of "Incorrect size N -> 0" and "Link count 2->1" and says the FS is fine, but a fsck without -p finds numerous files to reattach to lost+found, most of which look like temp files from the lang/rust compilation.

Filesystem in question is UFS+SU+Trim, bsize=32k, fsize=4k

No kernel dump available unfortunately.
Comment 1 Poul-Henning Kamp freebsd_committer freebsd_triage 2020-09-21 16:00:28 UTC
Time out my own old ticket, the issue has not resurfaced or gotten any attention.