From owner-freebsd-arm@FreeBSD.ORG Tue Sep 30 14:15:47 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 4E1DB502; Tue, 30 Sep 2014 14:15:47 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9A3E0124; Tue, 30 Sep 2014 14:15:46 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id gb8so10831060lab.30 for ; Tue, 30 Sep 2014 07:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4KfAUvdRSmbaZ299sJoCuRisYBqoor8NNkzaO/IXdbg=; b=zbYeNH1Kuvdqat/KG9XCeYuyoiQEbV/M4yjVpzbsBFPfmgTrYlYKOdu5P2dTkLUPgn MME6pt160heLqS8dzbAFSGU73HMu8aRqpO03nxUXFqnfltM7aMrqnAcADcZHLBHHoGD6 +Y6eK3X/IqdCtXL/l+nci5kj1v7mgh3UZls0T7F0Yccl0bqBHeBEXlkdUi/846NONgu1 BRWlZo2/zj4Le1nApSYyf6vOyllx6qi2cXcIjiPKcEx6pxj+hoASIq6y0JoQLmAfR3Wy +eJefwBPMT8a/R1EJWMUU8bgp0QoqX0GA3xsw4hwrYaptNOFMDacaBF4VVDRGM9YyobM Ksbg== X-Received: by 10.112.180.137 with SMTP id do9mr44642730lbc.63.1412086544612; Tue, 30 Sep 2014 07:15:44 -0700 (PDT) Received: from ?IPv6:2001:1620:ff0:c51:65fd:7630:d87f:4cbe? ([2001:1620:ff0:c51:65fd:7630:d87f:4cbe]) by mx.google.com with ESMTPSA id ll12sm6067703lac.45.2014.09.30.07.15.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 07:15:44 -0700 (PDT) Message-ID: <542ABB0F.8080201@gmail.com> Date: Tue, 30 Sep 2014 16:15:43 +0200 From: Mattia Rossi User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ian Lepore , freebsd-arm Subject: Re: Random Kernel Panic on Dreamplug (FS related) References: <542559BC.7090100@gmail.com> <20140929040126.GG43300@funkthat.com> <1411998551.66615.328.camel@revolution.hippie.lan> <20140930113444.GV43300@funkthat.com> <1412085915.66615.360.camel@revolution.hippie.lan> In-Reply-To: <1412085915.66615.360.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:15:47 -0000 Am 30.09.2014 16:05, schrieb Ian Lepore: > 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. I think there are at least a few people that tried it (http://lists.freebsd.org/pipermail/freebsd-arm/2014-February/007455.html). I've tried it as well (on an external ESATA disk), but had some performance problems, which I think could be resolved if I would run a bootloader (which I don't). The other solution would be to apply the following patch, and tweak performance via sysctls on a running system: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187594 Anyhow, first things first..