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
Date: Sun, 11 Jun 2017 12:47:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1706111242000.2371@joy.test> (raw)
In-Reply-To: <20170610180831.GF6365@ZenIV.linux.org.uk>
The ufs fixes are looking good, much better than what we started with.
After applying the 8 ufs patches:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
/commit/?id=5faab9e0f03c4eef97886b45436015e107f79f5f
Copying files to FreeBSD 11.0 (ufs2) and NetBSD 7.1 (ufs2) looks
pretty good.
I can copy a large >2GB file, create a directory and then run and
fsck without errors with a FreeBSD disk and a NetBSD disk.
But...
1) Creating an OpenBSD 6.1 (44bsd) disk and then on Linux copying a
large > 2GB file and creating a directory, there are errors on OpenBSD
with the fsck:
OpenBSD (44bsd):
#fsck sd0e
** /dev/rsd0e
** File system is already clean
** Last Mounted on /diske
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [Fyn?]
3 files, 1272410 used, 6983197 free (13 frags, 872898 blocks, 0.0% fragmentation)
***** FILE SYSTEM WAS MODIFIED *****
And also after removing the files on Linux, there were errors in
the fsck on OpenBSD:
#fsck sd0e
** /dev/rsd0e
** File system is already clean
** Last Mounted on /diske
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [Fyn?]
1 files, 1 used, 8255606 free (14 frags, 1031949 blocks, 0.0% fragmentation)
***** FILE SYSTEM WAS MODIFIED *****
2) The available block counts on a newly created FreeBSD 11.0
ufs2 filesystem (13079640) differ from Linux 4.12-rc4 (13079656):
Freebsd (ufs2):
#df /diske
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ada0s3e 14217008 8 13079640 0% /diske
Linux:
#df /fbsd23
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda23 14217008 8 13079656 1% /fbsd23
3) The available block counts on a newly created NetBSD 7.1
ufs2 filesystem (9518316) differ from Linux 4.12-rc4 (9518314):
NetBSD (ufs2):
#df /nbsdf
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda22 10019278 2 9518316 1% /nbsdf
Linux:
#df /diskf
Filesystem 1K-blocks Used Avail %Cap Mounted on
/dev/wd0f 10019278 2 9518314 0% /diskf
next prev parent reply other threads:[~2017-06-11 19:47 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 [this message]
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
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=alpine.LNX.2.21.1706111242000.2371@joy.test \
--to=comet.berkeley@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).