From owner-freebsd-fs@FreeBSD.ORG Fri Mar 28 22:41:32 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8076A203 for ; Fri, 28 Mar 2014 22:41:32 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (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 48454E91 for ; Fri, 28 Mar 2014 22:41:32 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s2SMcNs2075640 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 28 Mar 2014 18:38:24 -0400 (EDT) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: File system corruption with 9.2-R on PC Engines Alix boards From: John Nielsen In-Reply-To: Date: Fri, 28 Mar 2014 16:39:49 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0D92C2CC-3640-42AA-B589-33929641E984@jnielsen.net> References: To: Karl Pielorz X-Mailer: Apple Mail (2.1874) X-DCC--Metrics: ns1.jnielsen.net 1282; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 22:41:32 -0000 On Mar 28, 2014, at 11:02 AM, Karl Pielorz = wrote: > We have a number of PC Engines Alix boards, running FreeBSD 8.2. They = boot off of an onboard CF cards. >=20 > I recently installed a new one of these with 9.2-Release (i386) - only = to discover that it silently (i.e. with no errors) destroys the file = system when in use. >=20 > Typically we install these systems then flip the file system over to = 'read-only' when sending them out. The corruption happens while we're = installing various packages etc. >=20 > We don't run journal soft-updates on these boxes - just regular = soft-updates . >=20 > No console errors are logged, no syslog messages are logged. Just = after a while you might go to edit '/etc/rc.conf' - to find when you vi = it - it's now become a copy of '/etc/ntp.conf' - or other oddities. >=20 > A reboot runs fsck - which will usually fail then. Running a = foreground check reals off thousands of duplicate errors. If you = foreground check the file system, you're usually left with "not a lot" = when it's finished (i.e. if you run 'fsck -y /'). >=20 > 8.2 runs fine (we have systems that have been running embedded for = years) - 9.2 doesn't. >=20 > I found a similar thread: >=20 > = = >=20 > This eludes to CF card quality etc. - the cards we've been using have = worked fine for years - and a 9.2 'flaky' system reformatted to 8.2 then = runs fine. >=20 > Anyone else running later than 8.2 on PC Engine Alix kit? I have a pair of alix3dw systems that I use as wireless access points. = Both are running 10-STABLE on internal CF without problems. (I do world = and package builds on a faster host.) One has SU+J, the other has just = SU. I know I ran some version of 9-STABLE on the same hardware as well = (probably 9.1-ish) and don't remember any issues like those you are = describing. FWIW, both use this CF card: http://www.newegg.com/Product/Product.aspx?Item=3DN82E16820134575 You might try to see when the badness appeared in the FreeBSD 9 branch = by building kernels from various points and running them. If you use a = different build host and just build a custom kernel without (many) = modules or world it shouldn't be too onerous. I'd be curious to see if a = different CF card has the same problems too. JN