Date: Sun, 01 Mar 2015 19:21:18 -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: <1425262878.1287.4.camel@freebsd.org> In-Reply-To: <20150301203244.55578413@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> <20150301203244.55578413@ivory.wynn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2015-03-01 at 20:32 -0500, Brett Wynkoop wrote: > On Sun, 1 Mar 2015 16:55:59 -0700 > Warner Losh <imp@bsdimp.com> wrote: > > > Your filesystem looks messed up. Panics are likely to haunt you. > > You’ll need to newfs it and reload the data. > > > > Also, it would be great if you could type ‘tr’ to the db> prompt to > > get a call stack traceback. That would be quite helpful. > > > > Warner > > It seems counter to the design of the ffs, especially with softupdates > enabled that one should have to newfs. fsck claimed to have fixed the > filesystem, but to be complete I have just done a newfs on the > partation again and will attempt the copy yet again. > > root@beaglebone:~ # newfs -J -U /dev/gpt/bbexport IMO, there's your problem right there. People have been reporting for years that softupdates + journaling = corruption. The freebsd project's collective response to all those reports has been a rather silent yawn. The only sane response, IMO, is to not use journaling. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1425262878.1287.4.camel>