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
Date: Tue, 13 Jun 2017 02:43:02 +0100 [thread overview]
Message-ID: <20170613014302.GC31671@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.21.1706121743270.1697@joy.test>
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...
next prev parent reply other threads:[~2017-06-13 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 21:38 [git pull] first batch of ufs fixes Al Viro
2017-06-10 13:03 ` Richard Narron
2017-06-10 16:07 ` Al Viro
2017-06-10 18:08 ` Al Viro
2017-06-10 18:12 ` Linus Torvalds
2017-06-11 19:47 ` Richard Narron
2017-06-11 21:30 ` Al Viro
2017-06-12 6:14 ` Al Viro
2017-06-13 0:54 ` Richard Narron
2017-06-13 1:43 ` Al Viro [this message]
2017-06-13 21:56 ` Richard Narron
2017-06-14 7:11 ` Al Viro
2017-06-14 20:33 ` Richard Narron
2017-06-15 8:00 ` Al Viro
2017-06-16 14:29 ` Richard Narron
2017-06-17 2:15 ` Al Viro
2017-06-18 1:09 ` Al Viro
2017-06-18 20:45 ` Richard Narron
2017-06-20 5:17 ` [git pull] " Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170613014302.GC31671@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=comet.berkeley@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.