Date: Wed, 01 Mar 2023 14:27:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262157] su+j: Crashes during mmc(4) fsck after timeout: Error reading journal block 41408 -> INTERNAL ERROR: GOT TO reply() Message-ID: <bug-262157-227-YUMLhwrFfs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262157-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262157-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262157 --- Comment #2 from Andreas Schuh <x55839@icloud.com> --- Guess it's still an issue; though, since I disabled journaling, machine is running fine. Kernel panic was reproducible all the time, steps were: 1) Make sure, SU+J is enabled 2) Generate "high" I/O on the SD card, e.g. by installing Python with "pkg install python38" 3) At some point, machine would hang 4) Reboot; as the file system was broken after the system hung, fsck in sin= gle user mode was necessary 5) fsck always resulted in the reported kernel panic --=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-262157-227-YUMLhwrFfs>