Date: Tue, 2 Nov 2010 21:57:32 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Bruce Cran <bruce@cran.org.uk> Cc: freebsd-current@freebsd.org Subject: Re: Corruption of UFS filesystems after using md(4) Message-ID: <20101102195732.GL2392@deviant.kiev.zoral.com.ua> In-Reply-To: <201011021933.51052.bruce@cran.org.uk> References: <201011021912.14281.bruce@cran.org.uk> <201011021933.51052.bruce@cran.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Nov 02, 2010 at 07:33:50PM +0000, Bruce Cran wrote: > 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. What is .viminfo ? How is it related to the command you have shown ? What are exact mount options you are using ? [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAkzQbSwACgkQC3+MBN1Mb4ixMQCghGO9CMCcSGcHqeOgMc7ytq8+ TWEAn3af1bpbWN4crvXWxIC2JmLdpZMV =BtSp -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101102195732.GL2392>