From owner-freebsd-current@FreeBSD.ORG Tue Nov 2 19:12:16 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 71BD5106566C for ; Tue, 2 Nov 2010 19:12:16 +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 108BA8FC1E for ; Tue, 2 Nov 2010 19:12:16 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 5AF49E7209 for ; Tue, 2 Nov 2010 19:12:15 +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:12:14 +0000 (GMT) From: Bruce Cran To: freebsd-current@freebsd.org Date: Tue, 2 Nov 2010 19:12:14 +0000 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.5.2; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201011021912.14281.bruce@cran.org.uk> Subject: 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:12:16 -0000 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 created a 20GB md device using "truncate -s 20G mdfile && mdconfig -a -f mdfile" and then ran some gpart commands before using "mdconfig -d -u 0" and rm'ing the file. Some time later I noticed the following had been logged to dmesg: free inode /usr/3367984 had 128 blocks free inode /usr/3367984 had 32 blocks Now, whenever I run vim it creates a sparse 20GB .viminfo file - on another server those files were reported as being 8TB. I've disabled background fsck so the filesystems should have been clean when the system booted, and I'm not using SU+J. -- Bruce Cran