From owner-freebsd-arm@FreeBSD.ORG Mon Mar 2 02:21:28 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5568259 for ; Mon, 2 Mar 2015 02:21:28 +0000 (UTC) Received: from pmta2.delivery3.ore.mailhop.org (pmta2.delivery3.ore.mailhop.org [54.213.22.21]) by mx1.freebsd.org (Postfix) with ESMTP id A19C6971 for ; Mon, 2 Mar 2015 02:21:28 +0000 (UTC) Received: from smtp5.ore.mailhop.org (172.31.36.112) by pmta2.delivery1.ore.mailhop.org id huf4ji20u50s for ; Mon, 2 Mar 2015 02:21:39 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YSFyz-000771-2J; Mon, 02 Mar 2015 02:21:21 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t222LIGh090265; Sun, 1 Mar 2015 19:21:18 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/U2mDr3gBKKm59I6wvgKE5 Message-ID: <1425262878.1287.4.camel@freebsd.org> Subject: Re: crash on writing usbstick From: Ian Lepore To: Brett Wynkoop Date: Sun, 01 Mar 2015 19:21:18 -0700 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> Content-Type: text/plain; charset="windows-1251" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 02:21:28 -0000 On Sun, 2015-03-01 at 20:32 -0500, Brett Wynkoop wrote: > On Sun, 1 Mar 2015 16:55:59 -0700 > Warner Losh 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