From owner-freebsd-arm@freebsd.org Sat Mar 26 21:35:18 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CFA3ADDA9E for ; Sat, 26 Mar 2016 21:35:18 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E07791CDB; Sat, 26 Mar 2016 21:35:17 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id u2QLYjGH045688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 26 Mar 2016 22:34:52 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id u2QLYdi9079935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Mar 2016 22:34:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id u2QLYcii063923; Sat, 26 Mar 2016 22:34:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id u2QLYbsK063922; Sat, 26 Mar 2016 22:34:37 +0100 (CET) (envelope-from ticso) Date: Sat, 26 Mar 2016 22:34:37 +0100 From: Bernd Walter To: Ian Lepore Cc: Nikolai Lifanov , freebsd-arm@freebsd.org Subject: Re: Official images without noatime Message-ID: <20160326213437.GA63809@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <4b23b28ffae59216b5dde8f28f665330@mail.lifanov.com> <1459008905.1091.100.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459008905.1091.100.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 10.2-RELEASE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2016 21:35:18 -0000 On Sat, Mar 26, 2016 at 10:15:05AM -0600, Ian Lepore wrote: > On Sat, 2016-03-26 at 08:32 -0400, Nikolai Lifanov wrote: > > > > > > Hi, > > > agree, in fact I have noatime on / as well. Shall be the default. > > > > > > > > > > > > Cheers, > > > > > > > > > --- > > > Jos? P?rez > > > > > > El 2016-03-26 00:38, Bernd Walter escribi?: > > > > /boot/msdos has noatime, but / hasn't. > > > > Considering SD media I think using noatime per default is a good > > > > idea to avoid increased riscs of data loss on power failures. > > > > > > > Since we also default to SU-no-J, power failure can be quite bad > > during, > > say, installworld. > > With / noatime, I had my RPI2 lose files like /usr/bin/cmp, /bin/ls, > > and > > /bin/cat during a power loss. > > Since it's not even possible to cleanly shut down this platform, I'm > > for > > enabling noatime for / on You can cleanly shuttdown a Pi as well as any other system via shutdown(8) or even halt(8). > > at least for RPI and RPI2 platforms. This is related to flash media internal structure, not to RPIs. With SD cards on the higher risc end. Every flash write can lead to serveral unreadable blocks. Since there is no fixed relation between logical and phycial block numbers corruption can happen everywhere on the media. The more you write the higher the risc. But flash media also write flash cells when purely reading, since it need some kind of refresh from time to time. The risc for a power failure during refresh writes are less likely however. > I'm not sure why you think SU-no-J has anything to do with power > failure, but before it turns into some kind of mythology let me just > remind people that journaling does not enhance the ability to recover a > filesystem, it only makes it faster to do so (when it doesn't fail > completely, which it does all too often as seen with the numerous > reports, some recent, of "it was finally fixed when I reran fsck > without using the journal"). I would say the risc for data loss on power failure is even higher with J, since it also writes the journal. > To get that boot-time speedup in recovery it has to do more writing as > it goes (writing metadata to the journal and then again to the live > filesystem all the time). Given the slow speed of sdcard writes, > that's a steep price to pay to save 2 or 3 seconds of boot time after a > power fail. > > Again: journaling doesn't add reliability, it only speeds recovery. On > tiny sdcard filesystems the speedup is hardly noticible. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.