All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Drew DeVault" <sir@cmpwn.com>
To: <linux-ext4@vger.kernel.org>
Subject: j_recover_fast_commit: : failed on musl-riscv64
Date: Thu, 11 Feb 2021 15:48:11 -0500	[thread overview]
Message-ID: <C96ZW60NLAQF.1JF09JLHKR51M@taiga> (raw)

Hiya! I'm not really sure how to interpret this test failure with
e2fsprogs 1.46.1. Any ideas?

$ cat src/e2fsprogs-1.46.1/tests/j_recover_fast_commit.log
Journal checksum error found in test_filesys
Pass 1: Checking inodes, blocks, and sizes
Inode 14, i_blocks is 0, should be 2.  Fix? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 14
Connect to /lost+found? yes

Inode 14 ref count is 2, should be 1.  Fix? yes

Pass 5: Checking group summary information
Block bitmap differences:  +1107
Fix? yes

Free blocks count wrong for group #0 (941, counted=940).
Fix? yes

Free blocks count wrong (942, counted=940).
Fix? yes

Free inodes count wrong (245, counted=242).
Fix? yes


test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
test_filesys: 14/256 files (7.1% non-contiguous), 1108/2048 blocks
Exit status is 0
debugfs: ls
 2  (12) .    2  (12) ..    11  (20) lost+found    12  (968) a
debugfs: ls a/
 12  (12) .    2  (12) ..    13  (988) old
debugfs: ex a/new
debugfs: ex a/data
$ cat src/e2fsprogs-1.46.1/tests/j_recover_fast_commit.failed
--- j_recover_fast_commit/expect	2021-02-09 23:36:32.000000000 +0000
+++ j_recover_fast_commit.log	2021-02-11 20:39:26.306134217 +0000
@@ -1,22 +1,35 @@
+Journal checksum error found in test_filesys
 Pass 1: Checking inodes, blocks, and sizes
+Inode 14, i_blocks is 0, should be 2.  Fix? yes
+
 Pass 2: Checking directory structure
 Pass 3: Checking directory connectivity
 Pass 4: Checking reference counts
+Unattached inode 14
+Connect to /lost+found? yes
+
+Inode 14 ref count is 2, should be 1.  Fix? yes
+
 Pass 5: Checking group summary information
-test_filesys: 14/256 files (14.3% non-contiguous), 1365/2048 blocks
+Block bitmap differences:  +1107
+Fix? yes
+
+Free blocks count wrong for group #0 (941, counted=940).
+Fix? yes
+
+Free blocks count wrong (942, counted=940).
+Fix? yes
+
+Free inodes count wrong (245, counted=242).
+Fix? yes
+
+
+test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
+test_filesys: 14/256 files (7.1% non-contiguous), 1108/2048 blocks
 Exit status is 0
 debugfs: ls
  2  (12) .    2  (12) ..    11  (20) lost+found    12  (968) a
 debugfs: ls a/
- 12  (12) .    2  (12) ..    13  (12) data    14  (976) new
+ 12  (12) .    2  (12) ..    13  (988) old
 debugfs: ex a/new
-Level Entries       Logical      Physical Length Flags
- 0/ 0   1/  1     0 -     0  1107 -  1107      1
 debugfs: ex a/data
-Level Entries       Logical      Physical Length Flags
- 0/ 1   1/  1     0 -   255  1618            256
- 1/ 1   1/  5     0 -    15  1619 -  1634     16
- 1/ 1   2/  5    16 -    31  1601 -  1616     16
- 1/ 1   3/  5    32 -    63  1985 -  2016     32
- 1/ 1   4/  5    64 -   127  1537 -  1600     64
- 1/ 1   5/  5   128 -   255  1793 -  1920    128

             reply	other threads:[~2021-02-11 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 20:48 Drew DeVault [this message]
2021-02-12  4:03 ` j_recover_fast_commit: : failed on musl-riscv64 Theodore Ts'o
2021-02-12 13:27   ` Drew DeVault
2021-02-12 16:11     ` harshad shirwadkar
2021-02-12 16:26       ` Drew DeVault

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=C96ZW60NLAQF.1JF09JLHKR51M@taiga \
    --to=sir@cmpwn.com \
    --cc=linux-ext4@vger.kernel.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.