Date: Sun, 26 Oct 2014 14:19:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194606] filesystem unmount deadlock on 10.1 and head when TRIM enabled at unmount after r268815, MFC of 268205 Message-ID: <bug-194606-8-C8346OVYba@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194606-8@https.bugs.freebsd.org/bugzilla/> References: <bug-194606-8@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=194606 Guido Falsi <madpilot@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |In Discussion --- Comment #2 from Guido Falsi <madpilot@FreeBSD.org> --- (In reply to Warner Losh from comment #1) > If you disable trim, does the problem go away? Yes, it does go away. It easy to test, since simply mounting thee FS, editing a file with vi and unmounting it causes the panic, if not at first try it does in 2-3. > > I had a hard time scrounging up a CF card to test with on a SATA system. > > I'm guessing that I've dropped a biodone given the debug you've posted. Maybe, unluckily I don't know much about the kernel and the VFS system, so I can't really help with the code. Looking at it I noticed that before that commit thee value of softc->trim_running is changed before any operation is performed, while after the patch the code calls the new functions performing operation before changing that value, which is changed after the conditional (line 1506). It could be unrelated, I don't really know what that variable means, but could it be related? If you have some patch I'll be happy to test and report back. I can perform any kind of test, since this is not production hardware. -- 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-194606-8-C8346OVYba>