From owner-freebsd-arm@FreeBSD.ORG Tue Sep 30 14:05:19 2014 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 4F086172 for ; Tue, 30 Sep 2014 14:05:19 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (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 21523F86 for ; Tue, 30 Sep 2014 14:05:18 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XYy3J-000Fii-8k; Tue, 30 Sep 2014 14:05:17 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s8UE5GSP014474; Tue, 30 Sep 2014 08:05:16 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18gzKRTSZuPt6DLhrpN+bHM X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: Random Kernel Panic on Dreamplug (FS related) From: Ian Lepore To: John-Mark Gurney In-Reply-To: <20140930113444.GV43300@funkthat.com> References: <542559BC.7090100@gmail.com> <20140929040126.GG43300@funkthat.com> <1411998551.66615.328.camel@revolution.hippie.lan> <20140930113444.GV43300@funkthat.com> Content-Type: text/plain; charset="us-ascii" Date: Tue, 30 Sep 2014 08:05:15 -0600 Message-ID: <1412085915.66615.360.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm 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: Tue, 30 Sep 2014 14:05:19 -0000 On Tue, 2014-09-30 at 04:34 -0700, John-Mark Gurney wrote: > Ian Lepore wrote this message on Mon, Sep 29, 2014 at 07:49 -0600: > > On Sun, 2014-09-28 at 21:01 -0700, John-Mark Gurney wrote: > > > Mattia Rossi wrote this message on Fri, Sep 26, 2014 at 14:19 +0200: > > > > This might be part of the weird FFS issues the Dreamplug has and no-one > > > > knows why they're happening. > > > > > > Are you running w/ FFS journaling? If so, try turning it off, but > > > keeping softupdates on.. > > > > > > > It's not an SU+J problem, or even an SU problem. fsck finds > > non-existant errors on filesystems known to be clean, and if > > write-enabled it will corrupt the good filesystem when attempting to > > correct those "errors". This is on armv4 only, not v6. I tested with > > and without softupdates on. I tested with UFS1 and UFS2 filesystems. > > You can even do a newfs followed immediately by an fsck on it and it > > will corrupt the fs. > > > > The one thing I haven't done is opened a PR for this. > > Hmm... I just tested this on my AVILA board, and I don't see this on > either UFS1 or UFS2... Are you doing this via HD or md? My testing was > via a 64MB md as I don't have a good way to attach external storage to > my board... > > If you really are seeing immediate corruption to an SD card, then I'd > make sure that the card is getting the correct data written to it... > There isn't actually any corruption on the filesystem until fsck starts trying to fix what it thinks is wrong. That is, fsck -n will report problems, you then move that drive to a non-armv4 system and fsck there reports no problems. If you let armv4 fsck "fix" problems then move the drive to another system and re-check, the filesystem IS corrupted at that point. > I'd suggest trying to run ZFS since it checksums everything it writes, > but not sure if it'd run, and if so, how well... > afaik, nobody has ever tried zfs on any arm platform. Maybe it just works. I'd love to hear from someone about it. I don't have time myself to learn to configure and administer it. -- Ian