Date: Tue, 19 Feb 2008 04:16:34 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: gavin@freebsd.org Cc: freebsd-bugs@freebsd.org, schmidt@ze.tum.de Subject: Re: kern/120786: Kernelpanik when forced umount of a dettached USB Harddisk Message-ID: <20080219040611.U10725@besplex.bde.org> In-Reply-To: <200802181431.m1IEVIvO063079@freefall.freebsd.org> References: <200802181431.m1IEVIvO063079@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Feb 2008 gavin@freebsd.org wrote: > Synopsis: Kernelpanik when forced umount of a dettached USB Harddisk > > State-Changed-From-To: open->closed > State-Changed-By: gavin > State-Changed-When: Mon Feb 18 14:30:37 UTC 2008 > State-Changed-Why: > Close, duplicate of usb/46176 Not quite the same. 46176 mentions the file system, which is the immediate cause of the panic. I fixed the file system (msdosfs) in -current a while ago, and I think the fix is in RELENG_7 but not RELENG_6. Forcing the unmount is not supported, but msdosfs sort of did it anyway, in a bad way that guaranteed a panic near the end of the forced unmount. Now the forced unmount fails instead of panicing. The file system still keeps retrying writes forever, so it may clobber new media, or it may be confused mixing data from new and old media. Corruption from the former, and the latter, may cause a panic eventually. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080219040611.U10725>