[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-arm
Subject:    Re: crash on writing usbstick
From:       Ian Lepore <ian () freebsd ! org>
Date:       2015-03-02 2:21:18
Message-ID: 1425262878.1287.4.camel () freebsd ! org
[Download RAW message or body]

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


_______________________________________________
freebsd-arm@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]