Date: Mon, 02 Mar 2015 20:41:18 -0500 From: George Rosamond <george@ceetonetechnology.com> To: freebsd-arm@freebsd.org Subject: Re: disabling journaling? Message-ID: <54F5113E.9020405@ceetonetechnology.com> In-Reply-To: <54F5102A.10906@ceetonetechnology.com> References: <54F5102A.10906@ceetonetechnology.com>
next in thread | previous in thread | raw e-mail | index | archive | help
George Rosamond: > 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. Let me qualify that. Should journaling be disabled by default on flash media? This wouldn't necessarily apply to all Crochet builds. g
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F5113E.9020405>