From owner-freebsd-arm@FreeBSD.ORG Tue Mar 3 01:37:00 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 55D07318 for ; Tue, 3 Mar 2015 01:37:00 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DEBB908 for ; Tue, 3 Mar 2015 01:36:59 +0000 (UTC) Received: from 127.0.0.1 (sipb-tor.mit.edu [18.187.1.68]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id t231hrhP054700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 2 Mar 2015 20:43:56 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <54F5102A.10906@ceetonetechnology.com> Date: Mon, 02 Mar 2015 20:36:42 -0500 From: George Rosamond MIME-Version: 1.0 To: "freebsd-arm@freebsd.org" Subject: disabling journaling? Content-Type: text/plain; charset=utf-8 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, 03 Mar 2015 01:37:00 -0000 Ian mentioned softupdates + journaling is a problem. https://marc.info/?l=freebsd-arm&m=142526289401012&w=2 > 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. Should crochet be adjusted for it in lib/disk.sh? # Turn on Softupdates tunefs -n enable ${NEW_UFS_DEVICE} # Turn on SUJ with a minimally-sized journal. # This makes reboots tolerable if you just pull power # Note: A slow SDHC reads about 1MB/s, so a 30MB # journal can delay boot by 30s. tunefs -j enable -S 4194304 ${NEW_UFS_DEVICE} # Turn on NFSv4 ACLs tunefs -N enable ${NEW_UFS_DEVICE} I assume journaling should go first. Besides in build scripts, don't know how this would be done a system for the root partition when you can't go into single-user mode. g