Date: Thu, 21 Aug 2008 09:27:05 -0700 From: "Kevin Oberman" <oberman@es.net> To: "Alexey Shuvaev" <shuvaev@physik.uni-wuerzburg.de> Cc: freebsd-current@freebsd.org Subject: Re: usb/46176: Let's save the horse! [was: HEADSUP new usb code coming in.] Message-ID: <20080821162705.1F8F74500F@ptavv.es.net> In-Reply-To: Your message of "Thu, 21 Aug 2008 12:02:15 %2B0200." <20080821100215.GA24076@wep4017.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1219336025_92123P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: "Alexey Shuvaev" <shuvaev@physik.uni-wuerzburg.de> > Date: Thu, 21 Aug 2008 12:02:15 +0200 > Sender: owner-freebsd-current@freebsd.org > > On Wed, Aug 20, 2008 at 11:43:35PM +0200, Fabian Keil wrote: > > Warner Losh <imp@bsdimp.com> wrote: > > > > > From: Bakul Shah <bakul@bitblocks.com> > > > Subject: Re: HEADSUP new usb code coming in. > > > Date: Tue, 19 Aug 2008 14:18:13 -0700 > > > > > > > > > > > Accidentally unplugging a mounted USB disk (without > > > > unmounting it) resulted in a hang or a crash. Is this fixed? > > > > > > That's fixed in -current right now with the old stack. It isn't a usb > > > issue at all, but a buffer cache issue. > > > > I can't confirm this for either msdosfs or geli (with ZFS). > > > > In case of msdosfs the situation has been vastly improved > > and the panic seems to be no longer guaranteed, but there's > > still a fair chance it'll happen eventually. > > > It was discussed now and then on freebsd-usb mailing list. > Have a look at http://www.gulbra.net/freebsd-usb/ > > As for the non-msdosfs formatted media, I am quite sure it is a really bad > idea to unplug media before unmounting it (there is actually no difference > between "removable" and "stationary" drives). Today most pluggable media tends to be FAT32, but I suspect that we will see growing use of NTFS and that may be a bigger issue. The last portable drive I bought (SimpleTech 120 GB 2.5 inch) came NTFS formatted.I imagine that ntfs-3g/fuse will be used much more widely and the problem will get worse, again. Any idea if there is a hope of making ntfs-3g tolerant of this in a reasonable manner? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1219336025_92123P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIrZdZkn3rs5h7N1ERArV1AJ0QDvRXqX3vO9YlxoeGQgC75Fz5zgCeNd/z 5F+UWoEBqEyyLrihgnAIXFo= =aobY -----END PGP SIGNATURE----- --==_Exmh_1219336025_92123P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080821162705.1F8F74500F>