From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-io0-f194.google.com ([209.85.223.194]:35905 "EHLO
        mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751802AbdFMV4a (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Tue, 13 Jun 2017 17:56:30 -0400
Date: Tue, 13 Jun 2017 14:56:23 -0700 (PDT)
From: Richard Narron <comet.berkeley@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
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
In-Reply-To: <20170613014302.GC31671@ZenIV.linux.org.uk>
Message-ID: <alpine.LNX.2.21.1706131447230.2242@joy.test>
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> <20170613014302.GC31671@ZenIV.linux.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Tue, 13 Jun 2017, Al Viro wrote:

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

I created a gzip and sent you an email with the link to a UFS1 OpenBSD 
filesytem image.

I finished simple testing of UFS1 with FreeBSD and NetBSD and found no 
problems except for the differences between "available" blocks in df 
commands.

And testing UFS2 was fine with all 3 systems, FreeBSD, OpenBSD and 
NetBSD.