Date: Sun, 26 Jan 2025 00:46:36 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 198789] Panic while mounting an NANDFS filesystem Message-ID: <bug-198789-3630-xuj0u0OBUM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198789-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-198789-3630@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=3D198789 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #4 from Warner Losh <imp@FreeBSD.org> --- NANDFS had heap big time issues, not least was that the groomer was moved i= nto the kernel. This normally wouldn't be terrible, but here there were two problems: locking was all screwed up by it (or was just implemented badly) = and it always groomed, even when there was no new traffic, so the groomer slowly would rewrite the NAND over and over and over again. I wore out a MLC part while playing with it and tracked the issue down to this... That was in the FreeBSD 8 or 9 time frame and by FreeBSD 10 it wasn't working at all (even = with this patch) and had all kinds of lock order issues because the locking protocols evolved substantially over time, but no changes were made here. It's kind of a bummer, but doing a good nandfs takes a lot of time and effo= rt and you have to keep up all the time on the latest nand parts / soc offload engines / etc. And we had none of that. --=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-198789-3630-xuj0u0OBUM>