From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 13 Jun 2017 02:43:02 +0100 From: Al Viro To: Richard Narron Cc: Linus Torvalds , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [git pull] first batch of ufs fixes Message-ID: <20170613014302.GC31671@ZenIV.linux.org.uk> References: <20170609213830.GB6365@ZenIV.linux.org.uk> <20170610160738.GE6365@ZenIV.linux.org.uk> <20170610180831.GF6365@ZenIV.linux.org.uk> <20170612061417.GB31671@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, Jun 12, 2017 at 05:54:06PM -0700, Richard Narron wrote: > Earlier today I could not reproduce the OpenBSD 6.1 ufs1 fsck error after > Linux 4.12-rc5 copy of my >2GB file using "cp". > > But later today I get the error when I copy using your "dd" method... > > In any case I always get a ufs1 fsck error after the Linux rm and rmdir. Interesting... Could you put together an image (starting with zeroing the device before newfs, and ideally with dd from /dev/zero to create files) that would a) pass fsck on OpenBSD b) after rm on Linux fail the same then convert it to qcow2 and publish? Or just compress it - all free and data blocks would contain only zeroes, so any kind of compression (gzip, bzip2, whatever) would reduce the size to something more managable...