From owner-freebsd-fs@FreeBSD.ORG Fri Mar 28 17:02:39 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 B676D33F for ; Fri, 28 Mar 2014 17:02:39 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5E3D5790 for ; Fri, 28 Mar 2014 17:02:39 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s2SH2VRC088833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 28 Mar 2014 17:02:32 GMT Date: Fri, 28 Mar 2014 17:02:31 +0000 From: Karl Pielorz To: freebsd-fs@freebsd.org Subject: File system corruption with 9.2-R on PC Engines Alix boards Message-ID: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 17:02:39 -0000 We have a number of PC Engines Alix boards, running FreeBSD 8.2. They boot off of an onboard CF cards. 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. 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. We don't run journal soft-updates on these boxes - just regular soft-updates . 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. 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 /'). 8.2 runs fine (we have systems that have been running embedded for years) - 9.2 doesn't. I found a similar thread: 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. Anyone else running later than 8.2 on PC Engine Alix kit? -Karl