From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753257AbdFMBnG (ORCPT <rfc822;w@1wt.eu>);
        Mon, 12 Jun 2017 21:43:06 -0400
Received: from zeniv.linux.org.uk ([195.92.253.2]:45684 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752558AbdFMBnE (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 12 Jun 2017 21:43:04 -0400
Date: Tue, 13 Jun 2017 02:43:02 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Richard Narron <comet.berkeley@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        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>
 <alpine.LNX.2.21.1706100525410.1939@joy.test>
 <20170610160738.GE6365@ZenIV.linux.org.uk>
 <20170610180831.GF6365@ZenIV.linux.org.uk>
 <alpine.LNX.2.21.1706111242000.2371@joy.test>
 <20170612061417.GB31671@ZenIV.linux.org.uk>
 <alpine.LNX.2.21.1706121743270.1697@joy.test>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LNX.2.21.1706121743270.1697@joy.test>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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...