Date: Sun, 06 May 2018 11:54:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 228019] Panic and fsck -p insufficiency Message-ID: <bug-228019-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228019 Bug ID: 228019 Summary: Panic and fsck -p insufficiency Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: phk@FreeBSD.org Created attachment 193083 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D193083&action= =3Dedit 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 !=3D elm cpuid =3D 1 time =3D 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=3D32k, fsize=3D4k No kernel dump available unfortunately. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228019-227>