From owner-freebsd-arm@FreeBSD.ORG Tue Mar 3 09:36:45 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A857A48D for ; Tue, 3 Mar 2015 09:36:45 +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 5ED04CAF for ; Tue, 3 Mar 2015 09:36:44 +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 t239aKbd033185; Tue, 3 Mar 2015 04:36:20 -0500 (EST) (envelope-from freebsd-arm@wynn.com) Date: Tue, 3 Mar 2015 04:36:19 -0500 From: Brett Wynkoop To: Kurt Jaeger Subject: Re: disabling journaling? Message-ID: <20150303043619.37ab2bad@ivory.wynn.com> In-Reply-To: <20150303081334.GI62590@home.opsec.eu> References: <54F5102A.10906@ceetonetechnology.com> <20150303081334.GI62590@home.opsec.eu> 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=US-ASCII Content-Transfer-Encoding: 7bit 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: Tue, 03 Mar 2015 09:36:45 -0000 On Tue, 3 Mar 2015 09:13:35 +0100 Kurt Jaeger wrote: > Hi! > > > Should crochet be adjusted for it in lib/disk.sh? > > Yes, journaling should be disabled. > > We disable journaling on all our UFS devices and in addition use this: > > background_fsck="NO" > fsck_y_enable="YES" > That last bit could lead to lots of data loss if you have a badly hosed UFS. I do have it set on one REMOTE system that needs to come back up after power failure in my cabin in the woods, but if everything on that system goes away it is no loss as the data there is pretty static and in other places as well. Better to run fsck by hand and see how many problems there are, then decide if it makes sense to mount read only and copy the data off before doing the fsck -y. On the subject of journaling I do not think we should turn it off in crochet at this time. I have had exactly no problems with ufs on the root of my BBone, which is why I suspect my issues are centered more around USB than anything UFS related. I also have a couple of older x86 systems that can not run zfs which have softupdates and journaling on with no issues. There were issues at one point, but last time I saw Kirk in NYC he assured me the bugs were smashed. If it turns out one of the kernel types on here discovers from my backtraces that the problem is related to UFS and not USB then I suggest we put the data together and ask Kirk to take a look at it. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 April 19, 1775 An English attempt to confiscate guns from Americans triggered a successful revolution...... Dear Congress, that's a hint.