From owner-freebsd-arm@FreeBSD.ORG Mon Mar 2 01:32:50 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 66858644 for ; Mon, 2 Mar 2015 01:32:50 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 224521D4 for ; Mon, 2 Mar 2015 01:32:49 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t221Wivg034790; Sun, 1 Mar 2015 20:32:45 -0500 (EST) (envelope-from freebsd-arm@wynn.com) Date: Sun, 1 Mar 2015 20:32:44 -0500 From: Brett Wynkoop To: Warner Losh , freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150301203244.55578413@ivory.wynn.com> In-Reply-To: <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 01:32:50 -0000 On Sun, 1 Mar 2015 16:55:59 -0700 Warner Losh wrote: > Your filesystem looks messed up. Panics are likely to haunt you. > You=E2=80=99ll need to newfs it and reload the data. >=20 > Also, it would be great if you could type =E2=80=98tr=E2=80=99 to the db>= prompt to > get a call stack traceback. That would be quite helpful. >=20 > 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 /dev/gpt/bbexport: 14755.0MB (30218160 sectors) block size 32768, fragment size 4096 using 24 cylinder groups of 626.09MB, 20035 blks, 80256 inodes. with soft updates super-block backups (for fsck_ffs -b #) at: 192, 1282432, 2564672, 3846912, 5129152, 6411392, 7693632, 8975872, 10258112, 11540352, 12822592, 14104832, 15387072, 16669312, 17951552, 19233792, 20516032, 21798272, 23080512, 24362752, 25644992, 26927232, 28209472, 29491712 root@beaglebone:~ #=20 When it next crashes I will get a backtrace for the team. -Brett --=20 wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 The Second Amendment extends, prima facie, to all instruments that=20 constitute bearable arms, even those that were not in existence=20 at the time of the founding. ~ Justice Scalia