Date: Fri, 06 Mar 2015 08:42:51 -0700 From: Ian Lepore <ian@freebsd.org> To: Brett Wynkoop <freebsd-arm@wynn.com> Cc: freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <1425656571.51722.1.camel@freebsd.org> In-Reply-To: <20150306022648.6f7b969d@ivory.wynn.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150306022648.6f7b969d@ivory.wynn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2015-03-06 at 02:26 -0500, Brett Wynkoop wrote: > Greeting- > > I just had a thought, while trying to crash my BBone again. Back when > I started with BSD on PDP-11/70 we had to order special disk packs for > BSD that were certified error free because Unix in those days had no > way to map out bad blocks and could crash on hitting bad blocks. > > When we moved to using BSD on Pyramid and Sun boxes there were > utilities to map out bad blocks. I do not remember what it was under > OS/X, but on Sun OS 3.x and on it is of course part of the format > command. As I recall we used to have utilities for bad block mapping > in FreeBSD back in the 2.x and 3.x days. Sometime around the 4.x or > 5.x days drive makers started to do bad block mapping with the firmware > on the drives. > > Could it be that the whole issue here is that I am running into disk > faults on the flash disks and the flash drives have no way to map the > blocks out such as modern rotating drives do with SMART and such? > > I have done a bit of man -k searching but I have not found anything for > mapping out bad blocks in 11-current. > > At the moment I am just over 1/2 way in copying /usr/ports > to /export/ports with no crash yet but a bunch of > > aintc0: Spurious interrupt detected (0xffffffff) > aintc0: Spurious interrupt detected (0xffffffff) > aintc0: Spurious interrupt detected (0xffffffff) > > messages on the console. > > -Brett > Bad block remapping is handled by the microcontroller in the usb device. These panics are not caused by IO errors, if they were you'd see stuff like this on the console before the panic... g_vfs_done():da0p1[WRITE(offset=1674510336, length=131072)]error = 6 -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1425656571.51722.1.camel>