From owner-freebsd-current@FreeBSD.ORG Tue Nov 2 19:33:52 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECBC910656A4 for ; Tue, 2 Nov 2010 19:33:52 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id AF3498FC12 for ; Tue, 2 Nov 2010 19:33:52 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 13A37E7209 for ; Tue, 2 Nov 2010 19:33:52 +0000 (GMT) Received: from core.nessbank (client-81-107-141-216.midd.adsl.virginmedia.com [81.107.141.216]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA for ; Tue, 2 Nov 2010 19:33:51 +0000 (GMT) From: Bruce Cran To: freebsd-current@freebsd.org Date: Tue, 2 Nov 2010 19:33:50 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) References: <201011021912.14281.bruce@cran.org.uk> In-Reply-To: <201011021912.14281.bruce@cran.org.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011021933.51052.bruce@cran.org.uk> Subject: Re: Corruption of UFS filesystems after using md(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2010 19:33:53 -0000 On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote: > I've noticed in recent months that I appear to be getting silent corruption > of my UFS filesystems - and I think it may be linked to using md(4) or > creating sparse files. I've confirmed this is a UFS bug related to sparse files: "truncate -s20G f1 && rm f1" is enough to trigger the error and start generating .viminfo files that appear to be 20GB. When running fsck I get an "Invalid block count" error if I just reboot without removing the .viminfo file; if I do remove it, I get a "Partially allocated inode" error. -- Bruce Cran